A deterministic, git-native safety layer for what your coding agent touches.
Two independent adversarial gates, and the docs-backed workflow that produces them.
[](https://www.npmjs.com/package/codument)
[](LICENSE)
[](package.json)
[](tests)
[](#3--check--terminal-deterministic-core--independent-adversarial-gates)
[](#3--check--terminal-deterministic-core--independent-adversarial-gates)
[](#3--check--terminal-deterministic-core--independent-adversarial-gates)
[](#what-it-is)
[](#1--set-up--terminal-once)
[](#1--set-up--terminal-once)
[](#1--set-up--terminal-once)
codument watch · estimated from captured token usage · facts, not a bill
**[Website](https://codument.studio/)** · **[Quick start](#quick-start)** · **[30-second demo](#try-it-in-30-seconds)** · **[Autopilot](#autopilot)** · **[How it works](#what-it-is)** · **[Try it on your repo first](#try-it-on-your-own-repo--two-commands-zero-commitment)** · **[Docs](docs/)** · **[Report an issue](https://github.com/jakubsuplicki/codument/issues)**
## Quick start
**A new project**
```bash
npm install -D codument
npx codument init
```
Start a fresh agent session and chat normally. Describe what you want built; your agent grills the idea against your docs, writes a plan, and stops for your approval. **Approve it once and it builds the thing** — implementing, reviewing, documenting and committing each step on its own, and telling you where it is at every step.
**A project that already has code** — same command. `init` also maps your existing source to the docs that will own it, so there's a registry and a set of scaffolds waiting.
Start a fresh agent session, say **`/update-docs`** once so those docs describe the code you already have, then chat as above.
Two things worth knowing before you start:
- **Start a new agent session after setup.** Agents read their instructions when a session opens, so one you already had running won't see any of this.
- **Say "step by step" to slow it down.** That drops it back to stopping at every gate for your say-so, and it stays that way until you say "keep going".
## What it is
Codument has two sides that work together, plus an independent adversarial layer for when you want more than facts:
- **A delivery workflow your agent runs.** Docs-backed planning, source-to-doc ownership, review discipline, and commit hygiene. You just chat; your agent routes intent into the right phase. Core loop: `grill → plan → approve → implement → verify → document → review → commit`.
- **Deterministic CLI checks you run.** Local, no-network, no-AI commands that read the repo and report the facts: `doctor` (coverage + lint), `review` (what a change touched, what went stale, per-symbol drift), `watch` (a live view). Same repo state, same output. No model, no network, reproducible.
- **Two independent adversarial gates that verify, don't trust.** A plan adversary contests the written plan before code exists and never blocks; a review adversary contests a non-trivial diff and blocks only when a finding's named test is genuinely red on a live re-run. The AI proposes; a deterministic oracle decides, so adding AI here never undercuts "deterministic by default".
The connective tissue is **`docs/.registry.json`**, a registry mapping each source file to the feature/doc that owns it: the workflow writes it as it builds, the checks read it to reason about every change, and the gates project it into the contract an adversary attacks.