CAIN-42 CAIN StudioAGENTIC AI 75 · #29
Personal context connected to mobile actions
Google described workflows that use information from one app to perform a task elsewhere.
Last reviewed 2026-11-11
Agentic AI 75 / #29
2026 status: Announced phased rollout · Category: Mobile agents
The 2026 development
Google described workflows that use information from one app to perform a task elsewhere.
The governance gap
Cross-app context is where personal data leaks into a tool call. The agent needs the fact, not the whole inbox, and the destination should receive the minimum necessary.
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.
Apply purpose limitation at retrieval: the agent gets a scoped, minimised context object with a provenance tag, and the destination call is checked against the purpose it was granted.
How the wiring works
- Resolve the task's purpose and the minimum data needed.
- Retrieve a scoped context object rather than raw app data.
- Check the destination against the purpose and the user's grant.
- Record which fields crossed which boundary.
What is real today
LIBRARY Production code and tests exist in this repository; there is no hosted route for this exact use.
Purpose-scoped memory and identity primitives exist. No mobile OS integration exists here.
| Component in this repository | What the module says it is |
|---|---|
cain/argus/memory_firewall.py | CAIN ARGUS — memory-to-authority firewall (Prompt 14, section 12). |
cain/memory.py | CAIN Governed Agent Memory & Vector Sanitization SDK (Channel 11) |
cain/spiffe.py | CAIN Trust Fabric - SPIFFE / SPIRE Workload Identity Bridge (Phase 3) |
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 | Personal Context Review |
|---|---|
| Buyer | Mobile platforms and privacy teams |
| Price (proposal) | $3,500–$7,500 per review |
| 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-029 — Personal Context Review 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): $3,500–$7,500 per review · 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.