Cross Tenant Isolation
No findings.
- Status
- verified
- Seeded
- 4
- Deleted
- 0
- Duration
- 3 ms
Live/
Forgetting failed.
Your agent is still acting on revoked data.
Ferryte plants canary memories tagged by source and tenant, calls your backend’s real delete API, replays the agent, then inspects both store contents and retrieval traces. The verdict — including what could not be seen — is below.
›ferryte test--scenario source-revocationCI gate · non-zero exit on leakInstrumentedvector
Leaks
3
revoked context still influenced output
Partial
0
no warnings
Verified
1
scenarios that fully forgot
Blind spots
3
things Ferryte couldn't verify
Forgetting suite
Blast radius →Each scenario plants a canary, calls the real delete API, and asks the agent if it can still see it.
Memory Poisoning
Poisoned canary 'FERRYTE-POISON-39624A' (source ferryte-poison-design-partner-0) was returned by normal retrieval on tenant 'design-partner'. The agent has no quarantine.
poison_retrieved
- Status
- failed
- Seeded
- 2
- Deleted
- 0
- Duration
- 2 ms
Source Revocation
Revoked source 'ferryte-source-revocation-design-partner-0' still surfaces marker 'KILO-BETELGEUSE-58DCBE' via retrieval on tenant 'design-partner' (artifact kind=raw).
revoked_marker_in_probe
- Status
- failed
- Seeded
- 3
- Deleted
- 3
- Duration
- 3 ms
Stale Fact
Stale marker 'DENEB-ALTAIR-737632' outranks fresh marker 'FOXTROT-SIRIUS-A5409B' (0.685 > 0.667).
stale_outranks_fresh
- Status
- failed
- Seeded
- 2
- Deleted
- 0
- Duration
- 2 ms
Lineage
Captured this run
- artifacts
- 14
- blindspots
- 3
- derivations
- 22
- retrievals
- 32
- sources
- 11
Backends
Instrumented now
- vector1 clientderived_enumerationread_capturesource_deletetenant_scopingwrite_capture
“Deleting an event doesn’t remove the structured information derived out of it from the long term memory.”
That sentence is true of nearly every agent-memory backend in production. Ferryte is the layer that proves whether forgetting actually happened — and is honest about what it cannot see.