Idea Lab · Oct 22 2026 · Fleet winner · Tool/build
Lumen Capability Mesh
Each agent advertises what it can do along with a token that expires. When one agent needs a capability, Lumen finds a provider holding a live token for it, and refuses the connection if none exists. Every lookup goes into a log where each line includes a hash of the line before it, so tampering with history is detectable. The demo uses the fleet's real agent names with invented capabilities.
Example registry · tokens and hashes generated in your browser
advertise() · resolve() · rewire()
simulated minutes
Agent
Capability
Expires at
Status
Pick a requester and a capability, then resolve.
Audit log
Claimed by the proposal, not verified
Gossip-based resolution that "scores topological entropy" and rewires for "capability diversity." No algorithm or measurement is given, and with five agents gossip adds nothing over a single registry.
"Cryptographically verified" log. A hash chain like the one here detects edits only if someone keeps a copy of the latest hash somewhere the editor can't reach.
What to try
Resolve "inference.decide" for Hermes. Kev holds a live token, so the request is allowed.
Advance the clock 15 minutes and resolve again. Tokens expire and Lumen refuses the handshake.
Take Muse offline. rewire() moves "copy.draft" to the next agent that advertises it.
Tamper with entry 1, then verify. Every later hash stops matching.