- Run the app locally in default in-memory mode and open
/at 1080p. - Confirm the runtime badge says
in_memory · deterministicand the notice says Local deterministic demo. - Use only the three supplied synthetic scenarios. Do not enter credentials or customer data.
- Keep sanitized JSON collapsed; the decision facts and audit trail carry the story.
Show the opening frame and say:
AI agents can remember generated text for months. One secret or prompt injection can become durable context. MemoryGuard turns remembering into a governed transaction.
Point to Fail closed, Scoped retrieval, and Atomic evidence.
- Select Safe preference and click Run policy gate.
- Show
active, risk15,policy_pass, and memory + audit. - Click Retrieve memory.
Say:
Allowed memory and its audit event share one CockroachDB transaction. Retrieval applies tenant, namespace, lifecycle, expiry, and clearance filters before vector ranking.
- Select Secret injection and click Run policy gate.
- Show
denied,possible_secret,persistent_prompt_injection, and raw content blocked. - Point to the new denied event in the audit trail.
Say:
The raw input is never persisted. The audit trail receives only reason codes, content length, and a SHA-256 fingerprint.
- Select Needs review and click Run policy gate.
- Show
pending_review, risk55, and click Approve as human reviewer. - Keep clearance at
confidential, click Retrieve memory, and show the event chain.
Say:
Sensitive context stays invisible until a human approves it. Approval does not bypass retrieval clearance, and every transition remains auditable.
Show the architecture image and say:
AWS provides the protected serverless runtime and embeddings. CockroachDB keeps governed memory, vector search, and audit evidence together. This recording uses the deterministic local demo; the remaining live Bedrock quota blocker is disclosed in the submission.
- Safe:
active→retrieved, risk15,policy_pass. - Denied: HTTP 422, no memory ID or raw content, two reason codes.
- Review:
pending_review→active→retrievedat confidential clearance. - Audit: proposed, denied, approved, and retrieved events in reverse chronological order.
- Runtime badge and notice clearly identify local deterministic mode.
- Record in 1920×1080, 30 fps; target 70–80 seconds.
- Use a clean browser window at 100% zoom and keep the cursor movement deliberate.
- Cut pauses, but do not hide status transitions or the local-mode disclosure.
- End with
docs/assets/architecture.svg, repository URL, and public demo URL. - Do not claim complete live Bedrock retrieval until the bounded synthetic E2E passes.