From design c101: six finding sessions, and the pawns they need

Handoff from design c101 (Qmap Surface), 2026-11-03. The source of truth stays in design: if this note and the files it points to disagree, the design files win.

Design wrote six example agent sessions, each of which set off one or more policy findings. They're meant to be staged in qmap as small scenes ("dioramas"): one session per scene, about 6–17 actors each, drawn as two stills on the same cast: the finding, then what happened to it afterwards.

The six, in one line each

1. The stranger on the phone. Dana's Claude Code calls a Vanta MCP server nobody set up, signed in with her personal account. Observed.
2. The secret in the test file. Amara's Claude Code reads a fixture of real customer SSNs and sends them to the model and a Linear ticket. Observed; blocked from the next session on.
3. No brakes. Marcus runs Codex with approvals and the sandbox off. It reads ~/.pgpass, force-pushes and deletes a folder. Observed.
4. The door that stayed shut. Raj's Claude Code tries two paste sites, and both are blocked. Separately, an internal mirror negotiates weak TLS.
5. The trick note. An injected Sentry event gets Priya's Claude Code to read ~/.aws/credentials. The send-out is blocked.
6. The invisible helper. An unwatched process on Felix's machine talks to OpenAI for three hours. Only the traffic is visible.

Pawns needed

To stage all six scenes, qmap needs 11 pawns plus the guard's marks:

• Pawns: helper (harness), person, laptop (endpoint), brain (model), brain's company (provider), badge (account), plug-in (MCP server), tool, project (repo), file, outside place (destination).
• The guard's marks: a finding flag by severity; Observed vs Enforced; open, ignored-until-a-date, resolved and pending.

Skill and Team aren't needed. Team stays a rug.

First priority:

• Helper: watched · no brakes (approval gate missing) · unknown silhouette.
• Plug-in: configured · stranger (used, in no config) · joins the rug after an exception.
• File: ordinary · sensitive, high or critical.
• Outside place: approved · weak TLS · not approved and blocked (at a wall) · not approved and crossed.
• The guard's marks.

Missing art for every scene: the laptop has no 3D form, and the person, project and badge have no forms of their own.

Beyond pawns: a session rug vs an install rug, a payload riding a line, a gate on a line, a wall at the boundary, numbered steps, and fog for what can't be seen.

The full table, with the states each session needs and the art that exists today, is in design/cycles/c101.qmap-surface/pawns-needed.md.

Where the data is

The JSON is generated from design/app/data/finding-sessions-c101.ts with npx tsx scripts/finding-sessions-export.mts (run in design/). Edit the .ts, not the JSON.