Start with the story.
Branch where you want to see it run.
One route through the public material for people and for machines. Follow the four steps in order, or leave the story at any stage to see how that stage runs in operations, then come back.
Start with the story: One Request, Governed →Prefer pictures? The visual guideMachine-readable routes (index.json)
Where to begin
- qensai.dev landing page — "Start with the story: One Request, Governed", "See the Proof", "Visual guide to everything" and the newest presentation, under the opening paragraph. Signed-in users see the same links on Featured Work.
- See the Proof — The "Start here · reading order" card lists the four steps.
- Governance in use — Four articles that introduce the presentation, its evidence review, and the audience correction that tightened its claims.
- Recorded PoC cases — Fifteen supporting articles for the recorded cases, their limits and the governance patterns they illustrate.
- bots.qensai.dev About — "Start with the story", "Visual guide to everything" and "The fifteen operations steps (public view)" lead the Operational Components section.
The reading order
- Step 1 · One Request, Governed
The plain-language story: nine stages from a person's request to a human decision, then the recorded runs. - Step 2 · Engineering evidence review
Each recorded case with its supported conclusion, review question and limits. - Step 3 · The full account
The report, with process evidence, the evidence annex and the scope-correction case. - Step 4 · Machine-readable records
index.json (reading order and stage routes), the JSON evidence files, SHA256SUMS.txt and READ-ME.txt.
The nine stages, and where each one branches
Each stage of the story ends with a "See it in operations" line. It opens the matching step in the public view of the fifteen operations steps. Operator pages need a sign-in; the public view does not.
Side journeys
- Governance in use — presentation reading — Four public articles supporting the presentation and evidence review. Stage-specific posts also appear under related reading.
- Recorded PoC cases — supporting articles — Fifteen public articles that expand the recorded cases and their limits. Stage-specific posts also appear under related reading.
- When agents escape — A frontier-lab evaluation incident: scorer gaming, unsanctioned coordination, sandbox escape, and the line between governance and containment.
- PASS is not done — Recorded case (August 2026): a correct grader PASS reported as a finished form.
- Before an agent acts (partner showcase) — Illustrative eight-stage journey. A bar at the bottom returns to the story.
- Signal Capture, walked through as a family request — Explainer for stage 9. Its private sources are available by invitation.
- Response Table annotated guide — Explainer for stage 8. A teaching snapshot from 18 July; its links open operator pages that need sign-in.
- How It Works (Front Porch) — Hosted guidance reading and brief preparation.
- Knowledge Center tours — Guided tours. "Open in Operator" needs sign-in; each tour also offers the public fifteen-step view.
- Try Forge — Guest demo with a preloaded result (illustration).
- System Security showcase — SysSecureOps journey, proof and guide on lab.qensai.dev.
- Roadmap, then Contact — Planned capabilities; the last step links to Contact.
Mapped to the OWASP Top 10 for Agentic Applications
Where each risk in the OWASP list is addressed in the story, and the evidence today.
| Risk | Story stages | Evidence today |
|---|---|---|
| ASI01 · Agent Goal Hijack | 1, 3, 4, 7 | Recorded: an approved correction changed the next response (15 Sep 2026); a person redirected an agent that had made an unfinished experiment its goal, and the correction was kept in the oversight record (9 Oct 2026, record-keeping only). Open cited evidence · recorded |
| ASI02 · Tool Misuse & Exploitation | 4, 5, 6 | Designed. Tool and MCP server hardening is not shown. Open cited evidence · partial |
| ASI03 · Identity & Privilege Abuse | 2 | Recorded: a person authorized before anything ran (15 Sep 2026). Workload-identity standards such as SPIFFE or OIDC for agents are not shown. Open cited evidence · recorded |
| ASI04 · Agentic Supply Chain Vulnerabilities | 4, 9 | Designed. Third-party packages and registries are outside what we show. Open cited evidence · partial |
| ASI05 · Unexpected Code Execution (RCE) | 2, 6 | Designed for authorization. Sandboxing and network isolation are outside our layer. Open cited evidence · partial |
| ASI06 · Memory & Context Poisoning | 3, 4 | Recorded in part: the task contract and its records now travel in the agent's first message (2 Oct 2026). Open cited evidence · recorded_in_part |
| ASI07 · Insecure Inter-Agent Communication | 6, 8 | Recorded in part: one desk carried one request to three specialist agents, with a person arming each request (2 Oct 2026). Detecting unsanctioned side channels is not shown. Open cited evidence · recorded_in_part |
| ASI08 · Cascading Failures | 7 | Recorded: the gate caught a false "done" and stopped the chain, then exposed its own gap when it counted an honest "no data" reply as completed (1 Oct 2026, two local runs); the gap was fixed on 2 Oct 2026. Open cited evidence · recorded |
| ASI09 · Human-Agent Trust Exploitation | 7, 8 | Recorded: completion is now checked against criteria; a claim with no evidence fails (2 Oct 2026). Open cited evidence · recorded |
| ASI10 · Rogue Agents | 2, 7 | Designed. Containment of an agent that has escaped its environment is outside our layer. Open cited evidence · partial |
Outside our layer: Sandboxing and network egress control; Protection of binaries against reverse engineering; Containment of agents that have escaped their environment.
What needs a sign-in
- The operator console on ops.qensai.dev needs an invited operator account. Its published diagrams and guides are open to everyone.
- The consumer Relay Desk and Response Table on qensai.dev need an account with the right entitlement.
- Everything on the route above, the public operations view and the side journeys can be read without an account.
Put the governance claims under pressure.
The Governed Escape Test preserves its preregistered conditions and now exposes a bounded partial result with its limits. This optional advanced handoff comes after the story, proof and maps; it is not another starting point.
Enter the Governed Escape Test →I am still exploring
Each page labels its own evidence: recorded proof, designed, illustration, live read view or explanation. A label tells you what kind of claim the page makes; read the limits each page states.