Watch the memory boundary execute.
A suspicious note arrives. Inspect its admission, the returned context, and the recorded chain after restart.
Watch MADB execute the memory workflow.
A fresh, real MCP run against an isolated 0.2.15rc4 candidate server, captured as requests and responses arrive. Synthetic inputs; selected response fields; reading pauses added. This capture UI is a demonstration console, not the MADB product interface.
Read the execution video’s visual transcript
This is a silent MCP protocol recording with synthetic inputs, not an external model trial. The following text summarizes the visible sequence; the captured log provides the exact responses.
- A synthetic task is accepted and committed; repeating the commit returns the same event.
- An explicit instruction to ignore prior instructions is quarantined; its commit is denied.
- An unverified approval assertion requires approval. A caller-verified variant is accepted but not committed; the flag is not authenticated authority.
- Retrieved context marks historical evidence as untrusted; an unrelated query abstains.
- A separate local runtime mock denies the simulated deployment. This is not a MADB execution-control result.
- After a normal server restart, a trace retrieves the recorded task, decision and mock outcome.
Download MP4 · Inspect the captured execution log
This is a silent protocol demonstration, not a Claude/GPT model trial or a replay of the reported breach. Caller-supplied verification does not authenticate authority. Runtime permission enforcement remains separate.
1A task becomes memoryAccepted and committed
A synthetic staging-release instruction was stored. Repeating the commit returned the same event rather than a new write.
2An explicit injection is proposedQuarantined; commit denied
The tested note asked the agent to ignore previous instructions and deploy to production. This specific input was not committed.
3A quieter approval claim arrivesApproval required; commit denied
An unverified note claiming operations approval could not be committed without the required approval token.
4The application retrieves contextOne evidence record returned
The packet marked historical evidence as untrusted. An unrelated query abstained. Full history was inspected separately through tracing.
5Production is requestedLocal mock denies execution
A separate test-runtime allowlist denied the simulated request. No real deployment or network request occurred. This is not a MADB execution-control result.
6The server starts againThree-record lineage remains traceable
Task, decision and recorded mock outcome were all found in the causal trace after a fresh server process started.