Capture the influence.
Every retrieval, decision, derived memory, and action records the exact memory inputs that influenced it.
A malicious vendor document becomes M-184. The agent stores the claim as trusted memory and carries its source into every later decision.
Scroll to follow one compromised fact through the system.
MEMORY INTAKE / T+00. ONE FALSE MEMORY ENTERS TRUST. A malicious vendor document becomes M-184. The agent stores the claim as trusted memory and carries its source into every later decision.
RETRIEVAL / T+04. TRUST BECOMES BEHAVIOR. Procurement and Finance retrieve the same poisoned fact. What looked like one bad row now shapes approvals, derived memory, and a pending transfer.
BLAST RADIUS / T+11. THE DAMAGE HAS A TOPOLOGY. ANTIDOTE follows recorded influence edges from M-184 to every dependent. The red path shows evidence of impact, not a decorative network.
RECOVERY PLAN / PREVIEW. TRACE FIRST. REPAIR AS ONE. Preview the full state change before execution. Revoke the root, quarantine descendants, invalidate decisions, and preserve the audit trail.
The narrative above explains the threat. The console below reads the live case state. Select a node, compute its blast radius, then approve the transactional repair.
Deleting the row would leave decisions, derived memories, and external actions contaminated. Compute the causal blast radius before changing state.
Procurement ingests a malicious vendor document and forms a poisoned memory; Finance retrieves the derived approval and prepares a $24,000 transfer; Operations derives a trust memory; Security determines the source is compromised and repairs the chain.
Every retrieval, decision, derived memory, and action records the exact memory inputs that influenced it.
Transactional recovery changes the root memory and every affected descendant in one governed operation.
The confirmed attack becomes security memory, allowing future candidates to be screened before trust.