Repository truth, carried forward

Documentation that keeps pace with the code.

Kronika generates, audits, and reconciles documentation from an explicit source boundary. See what the model reads, gate drift in CI, and keep the result in Git.

Open sourceNode.js 22+CLI + TypeScript API
repository / documentation
$ kronika sources --repo .
Selected 24 files · 118,904 bytes
Skipped 9 files with reasons

$ kronika check --base origin/main
Documentation passes
No public behavior is missing.

$ kronika sync --dry-run
current  docs/cli.md
advanced docs/configuration.md
No hidden source selection
Inspect firstEvery selected and skipped file is visible before inference.
Fail closedEscaping paths, oversized diffs, and malformed answers are refused.
Remember in GitPer-document baselines make every reconciliation traceable.
01

One bounded loop.

Kronika separates evidence, judgment, and state so every step can be inspected and reviewed.

A

Select the evidence

Git-aware discovery, secret-prone exclusions, path confinement, and byte budgets establish the exact source manifest.

Source selection →
B

Write or audit once

One signed Brama request generates a candidate or judges an exact Git range. Preview is the default; writes are explicit.

CLI reference →
C

Advance the baseline

The sync loop checks only declared evidence. Passing audits advance state; blockers become a focused rewrite brief.

The sync loop →
02

A documentation gate with a concrete standard.

Internal refactors do not create prose churn. Kronika blocks on omitted or contradictory public behavior, interfaces, configuration, security boundaries, and operational contracts.

  • Audit one resolved base-to-head range
  • Return named blocker and warning findings
  • Exit non-zero for blockers or incomplete audits
How severity works →
Documentation verdictPASS
base9f2d67a
head4a8c10e

The changed behavior is covered by the current documentation.

0 blockers1 warning
03

From first command to unattended reconciliation.

The documentation covers the full CLI and library surface, the evidence and trust boundaries, every sync concept, recovery paths, and captured end-to-end walkthroughs.

Keep the boundary visible

Start with the files the model is allowed to see.

Read the quick start