CAIN-42 CAIN StudioAGENTIC AI 75 · #14
Persistent, correction-aware agent memory
OpenAI's internal data agent saved corrections and organisational knowledge for reuse.
Last reviewed 2026-11-11
Agentic AI 75 / #14
2026 status: Reported internal deployment · Category: Memory
The 2026 development
OpenAI's internal data agent saved corrections and organisational knowledge for reuse.
The governance gap
A saved correction is a high-value memory with a provenance problem: who corrected it, against which source, and does it still apply after the source changes? Unchecked, a correction becomes an unappealable rule.
Where CAIN-42 fits: Moat 2 — Security-Context Continuity
Core question: Does authority survive every boundary? Identity, scope and delegation are carried across tools, agents, memories and systems.
Store memory with its author, source, scope and supersession chain, and never let a retrieved memory carry authority. CAIN's governed-memory client and MEMGUARD enforce write-time screening, tenant scope and revocation.
How the wiring works
- Write the correction with its source, author and scope.
- Screen the write for injection and policy conflict before it is stored.
- Retrieve with tenant and purpose filters, not only similarity.
- Supersede or revoke rather than overwrite, and keep the chain.
What is real today
LIVE A public route in this deployment exercises this mechanism today, within its stated scope.
The hosted memory demo sanitises fixed adversarial memories. It is not an OpenAI deployment and does not prove long-term memory quality.
| Component in this repository | What the module says it is |
|---|---|
cain/memory.py | CAIN Governed Agent Memory & Vector Sanitization SDK (Channel 11) |
cain/argus/memory_firewall.py | CAIN ARGUS — memory-to-authority firewall (Prompt 14, section 12). |
keystone/memguard.py | MEMGUARD KEYSTONE: Agent long-term memory audited, Claude cleanses, vector sanitization proved, signed. |
cain/continuum/memory_continuity.py | CAIN CONTINUUM — Authority-Preserving Memory + continuity proof + consolidation attack lab |
Descriptions are the first line of each module's own docstring, read without importing it. A module path is a pointer into this repository, not a hosted endpoint. Its existence is checked by the test suite; its status for this use is the label above.
Check it yourself
- Run the live memory-sanitisation demo
/memguard-keystone - Fire a live decision through the CAIN-42 pipeline
/fabric/try— the same enforcement path every product sits behind.
Commercial package
| Offer | Memory Authority Audit |
|---|---|
| Buyer | Agent-platform teams and enterprise knowledge owners |
| Price (proposal) | $2,500 per audit; pilot from $5,000 |
| Bundle | Memory & Context — Memory that cannot launder authority. |
| Operator stream | Stream 2 of the 10-stream operator playbook |
Agent-platform teams, enterprise AI governance, regulated data owners is the bundle buyer. The entry offer for this bundle is Memory authority audit; hosted memory-sanitisation pilot; the range is $2,500 per audit; metered from $0.0002 per inspection. A price on this page is a proposal, not a validated rate, and no customer is claimed.
Buy this as a product or service
CAIN-A75-014 — Memory Authority Audit DELIVERABLE
A bounded engine run on the buyer's sample: findings, a written report, and a SHA-256 artifact manifest. The manifest is unsigned: it is not a signature and not an attestation.
Kind: Assessment · Price (proposal): $2,500 per audit; pilot from $5,000 · Lead time: 5 business days.
Open the product page · all 75 products
What this page does not claim
What this page is not. CAIN-42 is not affiliated with, endorsed by, integrated into, or shipped with the organisation named in the 2026 item. The item is public context; the page describes how CAIN-42 would govern that class of capability. No page here claims a customer, a partnership, a certification, a patent, or a production integration. Prices are proposals. Built by a three-person team.