Capstone: publish an operating map, not a deployment

Verifiedon 2026-07-302026.7.1-2

Scenario

You inherit a proposed personal-assistant deployment. It will accept messages from an operator’s chosen channel, call one read-only internal service, and return a response. It may later add a team room and browser node. You are not asked to install or expose anything. Your job is to make the design safe to review.

Deliverable

Submit one redacted page containing:

1. an original system and request/data-flow diagram;
2. the Gateway, agent, session, memory, model, channel, tool, and recipient surfaces that actually apply;
3. at least three explicit boundaries: identity/credentials, untrusted content, and external side effect;
4. an owner and stop/escalate rule for each external action;
5. source receipts with revision and review date; and
6. the current status: proposed, tested in sandbox, approved, or not approved.

Do not substitute a video, copied transcript, or generic security checklist for this work. The page must be understandable without third-party media.

Rubric

A passing capstone proves disciplined analysis—not production readiness. Any addition of public ingress, a privileged tool, new plugin, mixed-trust audience, or external recipient needs its own review.

Final check

Before sharing, remove secrets, QR codes, personal identifiers, raw transcripts, private hostnames, and unnecessary log output. Confirm that the source receipt links resolve to the exact reviewed revision and that your claims distinguish the current documented behaviour from planned design decisions.