← Cycles
bob-wire · c18activestarted Jul 24Auto draft — not yet reviewed

Post-Mortem Map

Park it for nowThe research and brief are sound and nothing has replaced them, but no one has picked up the wireframe in three months.

Next: Park it with a pickup note: build the incident page from the brief when incident pages return to the roadmap. · Or close it with the research as its outcome.

last activity Jul 24

Why we did this

Incident pages tell what happened in stacked cards and tables. We wondered whether a map of who touched what would help, or was a solution looking for a problem.

What happened

Research says yes: Microsoft, AWS, Wiz and others put such maps on incident pages. A design brief is ready. The wireframe was never built.

In wordsOther security products put an actor map on the incident page; ours should be a guide beside the timeline, limited to the incident, and honest about guesses.
At a glance
3
changes
0
conversations
0
decisions
0
outside helpers

What changed

The change that matters most, in plain words. Open any one to see it.

  1. 1

    Other security products put an actor map on the incident page; ours should be a guide beside the timeline, limited to the incident, and honest about guesses.

    A map is worth drawing, with conditions · came from Mark Parson

Also in this cycle
  • No one draws the AI-agent version: tool servers, repos and models as actors with their policy state. In words
  • A design brief for one incident page is written; the wireframe pass never ran. In words

How we got here

Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.

Someone said

From the record: no recorded conversation behind this one.

We decided

No ruling needed: the work itself is the change.

So now

Other security products put an actor map on the incident page; ours should be a guide beside the timeline, limited to the incident, and honest about guesses.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Asked whether the map was worth it

The initial prompt asks whether a visual map is valuable or "a solution looking for a problem"; the record names no one, and the cycle folder was committed by Mark Parson (git), so the credit is matched from authorship.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

Everything captured · 0

The full record 0 decisions · 0 key-change entries · 336 words · 0 captures

The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.

Open the record for c18 →

Qpoint Brand Style Guide