Operators Demo
Capsules.Run Local*
This demo establishes a file format for shipping context across teams, tools, organizations, and offline machines. Gather evidence, interact with Gemma 4, establish chronology and provenance, then prepare a `.capsule` another unit can hydrate.
* Capsule v0.6 prototype: software, AI, and an operator writing the Capsule file format. It proves sealed bytes, hashes, event order, and signer key, not real-world truth.
Gemma 4 and Ollama power local inference at frontier levels while Capsule keeps the work portable.
`program.md`, `manifest.json`, and `chain/events.jsonl` give teams a known substrate instead of a loose chat transcript.
Evidence can be gathered and analyzed with Gemma 4 locally before anything leaves the device.
Different people can operate in different rounds of the same situation while preserving events, decisions, and provenance.
Like skills, capsules are malleable. SaaS products, local tools, and runtimes can write the same baseline structure.
Prepare to ship your cognition layer.
Capsule structure
Device briefing lines
SITREP: waiting for evidence. PRIORITY: LOW. VERIFY: inspect source bytes before action. NEXT: add evidence, interact, then seal.
Bind the capsule to a local key.
Capsules-protocol envelope
The command center first renders the capsule as a signed inner ZIP. When encrypted seal is on, the SDK wraps that signed capsule as `content.enc` and writes the decryption metadata into the outer capsule.
- Sign: Ed25519 over the canonical capsule envelope.
- Encrypt: ChaCha20-Poly1305 for the inner capsule bytes.
- Wrap: X25519 derives a recipient key bundle so the other party can decrypt with their private export key.
- Verify: the receiver unwraps, parses the inner capsule, then verifies the Ed25519 signer and event chain.
This is an SDK-aligned example layer, not a competing email encryption standard. Other organizations can swap the envelope implementation while preserving the Capsule manifest, chain, and trust boundary.