Session View
To close: Write an Outcome: four-altitude ladder and fixtures kept as reference · Move to HISTORY.md
last activity Aug 20
The product records everything an AI session does, but there was nowhere to read it: a link promised a session's full story and went nowhere.
Two mocks: one session read at four levels, from receipt to raw events, and a bake-off reading it as a chat. Not finished yet: the timeline, footprint map and final page were never built.
Documents
With file names, on their own page →What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
A session can now be read: first as a layered record with a receipt on top, then as a chat people already know how to read.
From a record to a conversation · came from Mark Parsonopen →
- 2
One page shows a session four ways: a receipt, chapters, the full conversation, and the raw events.
One session, four heights · came from Mark Parsonopen →
- When a rule blocks something, it appears like an app posting an alert in a team channel. In words
- Showing full prompt text and keeping sessions short enough to read were written down as open questions, not settled. In words
- The chat idea later became shared transcript parts, used on the product's Session Details page. 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.
c77-D1 Design for the engineer reading their own session first; the CISO receipt is the first finished piece. — Mark Parson
c77-D8 Try the transcript in familiar chat styles; familiarity is the ramp, not the destination. — Mark Parson
A session can now be read: first as a layered record with a receipt on top, then as a chat people already know how to read.
From the record: no recorded conversation behind this one.
c77-D7 Everything is worked out by fixed rules for now; AI-written titles are liked but parked. — Mark Parson
One page shows a session four ways: a receipt, chapters, the full conversation, and the raw events.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Ruled the seven framing questions
Chose engineer-first with the receipt as the first finished piece, replay only, full text for now with privacy kept in view, and fixed rules over AI summaries; then asked to try familiar chat styles.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 2
The full record 7 decisions · 5 key-change entries · 873 words · 2 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 c77 →