CAIN-42 MCPGateAGENTIC AI 75 · #63
Agent permission review inside collaboration tools
Salesforce and NVIDIA described Slack-based inspection and approval of agent permission requests.
Last reviewed 2026-11-11
Agentic AI 75 / #63
2026 status: Integration announcement · Category: Workplace governance
The 2026 development
Salesforce and NVIDIA described Slack-based inspection and approval of agent permission requests.
The governance gap
Approval in chat is convenient and easy to spoof. The approver needs to see the exact action, the target and the consequence, and the approval must be bound to that action rather than to a message thread.
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.
Bind approval to an action digest and a named approver. A chat message can carry the request, but the approval record is separate, signed and single-use.
How the wiring works
- Render the exact action and consequence in the request.
- Bind the approval to the action digest and expiry.
- Verify the approver's identity and authority.
- Consume the approval once and record it.
What is real today
LIVE A public route in this deployment exercises this mechanism today, within its stated scope.
The approval demo is real on fixed actions. No Slack or Salesforce integration exists.
| Component in this repository | What the module says it is |
|---|---|
keystone/approval.py | APPROVAL KEYSTONE: a person approves the exact action, in Slack or by a one-time link, and the approval is proof. |
cain/argus/reauthorization.py | CAIN ARGUS — continuous re-authorization engine (Prompt 14, sections 8-9). |
cain/worm_export.py | CAIN Trust Fabric - tamper-evident WORM Causal Evidence Fabric (Phase 4) |
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 action-bound approval demo
/approval-keystone - Fire a live decision through the CAIN-42 pipeline
/fabric/try— the same enforcement path every product sits behind.
Commercial package
| Offer | Chat Approval Review |
|---|---|
| Buyer | Collaboration platforms and enterprise IT |
| Price (proposal) | $2,500–$5,000 per review |
| Bundle | Identity & Authority — Every agent, every delegation, every boundary. |
| Operator stream | Stream 2 of the 10-stream operator playbook |
CISO, IAM, platform security, agent-tool vendors is the bundle buyer. The entry offer for this bundle is Agent authority review; MCP/A2A boundary review; the range is $2,500–$7,500 per review; integration from $10,000. 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-063 — Chat Approval Review PILOT
A bounded pilot report: up to five scenarios, the relevant library engine or analysis, a written result and the stated limits. Engineering time is quoted per pilot.
Kind: Assessment · Price (proposal): $2,500–$5,000 per review · Lead time: 10 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.