Documentation
Prove your engineering. Here's how.
The complete reference for the zegit ecosystem — the toolchain that turns the work your developers and agents do into signed, audit-grade evidence bound to the exact commit. meerkat knows · mongoose works · zegit proves.
The toolchain
Three tools share one evidence spine. The same record travels from "an agent ran a step" all the way to "here is the signed, CRA-mapped proof" — with no translation layer in between.
A knowledge base compiled into a single binary and served over MCP, CLI, and HTTP — so agents start from what's true at your org.
A developer agent harness — an OpenCode-style TUI. Multi-provider routing, a tool loop, meerkat wired in. Every step emits evidence.
The governance layer. Signs evidence into an Attestation of Validation, gates releases with quorum, and bundles CRA-grade proof.
Start here
Install & first run
Install zg, meerkat, and mongoose, then go from zero to a governed push in 90 minutes.
ReadCore concepts
Evidence records, envelopes, AoVs, DSSE, and the ALLOW / REQUIRE_REVIEW / BLOCK policy engine.
Readzg CLI reference
Every zg subcommand — validate, auth, tr, evidence, init, revert, ceremony — with flags and exit codes.
ReadCRA Evidence Bundle
Turn a release tag into an Annex I–mapped, offline-verifiable evidence bundle.
ReadReference by component
zegit
The prover: validation, AoVs, Tag Requests, the gateway, and evidence bundles.
Openmeerkat
The knowledge base: install, the mk CLI, content sources, ingestion, and MCP/HTTP integrations.
Openmongoose
The agent harness: the TUI, model routing, model catalogs, skills, and evidence output.
OpenEditor plugins
Emit zegit evidence from Claude Code and OpenCode sessions, deterministically.
OpenA note on honesty
These docs follow the platform's own voice rule: be honest about what the evidence proves. Where a feature is planned rather than shipped, or where a v1 attestation has a known limit, the page says so plainly.