Architecture

Local-first by construction.

Kermit's shape is the reason its guarantees hold. Inputs are read-only. Outputs are drafts. The reasoning trace lives next to the brief, on your machine, in plain markdown.

Local-first architecture diagram showing connectors flowing into a reasoning core, persisting to a local vault, governed by a draft-only rail. — The cockpit, end to end — read-only in, draft-only out, fully sourced.

Four pillars

The four things that have to be true.

Local-first vault

Markdown in your own Kermit/ folder is the source of truth. Sync, back up or fork it like any other repo.

Engine-agnostic core

Inference engines are pluggable behind one contract — swap models, run locally or remotely, without changing the system.

Governance rail

Draft-only, read-only and epistemic-tagging guarantees are enforced at the rail — not left to model behavior.

Atomic deploy

Briefing, run log, reasoning trace and dashboard render in one approved write — every run is replayable.

System diagram

Connectors in. Reasoning core. Local vault. Governance rail.

Kermit system architecture: connected read-only sources feed an engine-agnostic reasoning core; outputs persist to a local-first vault; a governance rail enforces draft-only, read-only and auditable guarantees.

See the trust guarantees Walk through the product

See a morning briefing in action.

Kermit explores safe, auditable agentic operations — reaching any system the orchestrator can see, drafting never sending.

mykermit.aiA Blank Page project