Situation Room
To close: Write the Outcome: three wireframes and one hi-fi mock for Policy Compliance; the pattern was reused in c13. · Move it from CYCLES.md to HISTORY.md.
last activity Mar 23
Security teams needed one place that shows whether things are healthy and, when they aren't, what is wrong, who is involved and how to fix it.
The "Situation Room" became a reusable pattern. Its first instance, Policy Compliance, got three wireframes and one polished mock. The cycle was never formally closed.
Documents
With file names, on their own page →Start here
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
A violation page states the problem in one sentence, then shows who sent the data, who received it, and what kind of data it was.
A violation, explained · came from Mark Parsonopen →
- 2
The Situation Room became a kind of page that can be made for any named problem; Policy Compliance is the first.
A pattern, not a page · came from Mark Parson
- The first brief said which parts to put on screen; it was rewritten to say only what data matters and what the page must achieve. 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.
From the record: no recorded conversation behind this one.
bob-wire-c1-D1 The Situation Room is a class of page, not one page: each instance focuses on a named problem space. The first instance is Policy Compliance. — Mark Parson
A violation page states the problem in one sentence, then shows who sent the data, who received it, and what kind of data it was.
From the record: no recorded conversation behind this one.
bob-wire-c1-D1 The Situation Room is a class of page, not one page: each instance focuses on a named problem space. The first instance is Policy Compliance. — Mark Parson
The Situation Room became a kind of page that can be made for any named problem; Policy Compliance is the first.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Defined the Situation Room
Wrote the initial prompt that defines problem space, actors, flows, borders and remedies, and the two states of the room. The record names no one; every commit in this cycle is authored 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 · 5
The full record 0 decisions · 5 key-change entries · 237 words · 3 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 c1 →