CAIN-42 MCPGateAGENTIC AI 75 · #26
Finished knowledge-work deliverables
ChatGPT Work was described as researching, analysing and producing documents, spreadsheets, presentations, reports and sites.
Last reviewed 2026-11-11
Agentic AI 75 / #26
2026 status: Released product capability · Category: Knowledge work
The 2026 development
ChatGPT Work was described as researching, analysing and producing documents, spreadsheets, presentations, reports and sites.
The governance gap
A finished deliverable is a consequential artifact that leaves the organisation. The questions are source provenance, who approved the final version, and whether the file can be altered after it was signed.
Where CAIN-42 fits: Moat 4 — Execution Provenance & Attestation
Core question: Can we prove what actually happened? Hash-chained, signed records binding decision to execution to observable effect.
Bind the deliverable to its sources, its generator, its reviewer and a content digest, then export a verifier. CAIN's WORM export and KEYSTONE bundle already produce tamper-evident packages with offline verification.
How the wiring works
- Record the sources and the model/tool versions used.
- Hash the final artifact and bind the reviewer's approval.
- Export a package with a standalone verifier.
- Detect any post-signing change on re-verification.
What is real today
LIVE A public route in this deployment exercises this mechanism today, within its stated scope.
The hosted demos export and verify fixed sample records. They do not prove the quality or truth of a knowledge-work deliverable.
| Component in this repository | What the module says it is |
|---|---|
cain/worm_export.py | CAIN Trust Fabric - tamper-evident WORM Causal Evidence Fabric (Phase 4) |
keystone/bundle.py | KEYSTONE evidence bundles: the signed records packaged neatly for an auditor (a zip). |
cain_audit/deliver.py | The factory: turn one of the six products into a signed, self-verifying deliverable. |
cain/audit.py | CAIN Trust Fabric - Adversarial Agent Auditor (Phase 1) |
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
- Inspect a live signed product bundle
/product-demo - Fire a live decision through the CAIN-42 pipeline
/fabric/try— the same enforcement path every product sits behind.
Commercial package
| Offer | Signed Deliverable Pack |
|---|---|
| Buyer | Enterprise knowledge teams and consultancies |
| Price (proposal) | $2,000–$10,000 per pack |
| Bundle | Runtime Containment & Evidence — Contain first, then prove what happened. |
| Operator stream | Stream 4 of the 10-stream operator playbook |
SOC, incident response, compliance, enterprise IT is the bundle buyer. The entry offer for this bundle is Runtime containment review; signed evidence pack; the range is $2,500–$5,000 per review; $2,000–$10,000 per evidence pack. 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-026 — Signed Deliverable Pack 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: Evidence Pack · Price (proposal): $2,000–$10,000 per pack · 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.