Idea Lab · Oct 24 2026 · Fleet winner · Tool/build
Capability Provenance Daemon (CACPED)
A watcher that reads every agent action as it happens, records where each capability came from (who granted it, what it was built on), and checks each action against a contract. When an agent does something its contract doesn't allow, the daemon flags it with the full chain of how that capability got there.
Working demoExample event stream and contracts
Contracts
Provenance graph
0events processed
0capabilities tracked
0contract violations
Daemon log
Claimed by the proposal, not verified
"Real-time" and "low-latency" Rust event processing. No benchmarks were given, and for five agents the speed of the daemon is not the bottleneck.
An "incremental hypergraph" of capability origins. A plain table of grants (who, what, from whom, when) covers every case in this demo.
What a real build would need
Every agent emitting a structured event for each action (one JSON line to a shared log or Redis stream). This is the hard part; the checker itself is small.
Contracts stored in a repo the board reviews, so a change to what an agent may do is itself audited.
For our fleet, a Python script reading that stream would do the job. Rust and gRPC bridges are not needed at this size.
What to try
Press Play all. Three violations appear: Muse emails an address outside its allowlist, Gemini hands its VPS-restart right to Antigravity without permission, and Antigravity then uses it.
In the contracts, add "delegable": true to Gemini's vps.restart entry and replay. Both delegation violations disappear, and the log shows the chain Board → Gemini → Antigravity.
Remove email.send from Muse's contract and replay to see every send flagged.