How kal thinks
Five ideas, five drawings. Understand these and you understand the whole system. Throughout, amber marks agent work and teal marks human trust — the same language azmx.ai uses.
1 · A snapshot is what + why + who
git stores a tree of files and a message. A kal snapshot stores the tree plus a structured intent and a structured author. History stops being a pile of diffs and becomes a narrative you can query.
kal log walks — each point carries its message, its intent, and who authored it.2 · Immutable history, revisable notes
Facts known when you snapshot — message, intent, author, files — are sealed inside a content-addressed object: change one byte and the identifier changes. Facts learned later — test results, reviews, approvals — attach as notes keyed to that identifier. You can re-test, re-review and re-index forever without ever rewriting history.
3 · The operation log behind undo
Commands don't merely move refs: every mutation appends an entry recording the complete state of every branch and tag before and after. Undo restores the “before”. Snapshots are never deleted, so undoing is just another logged operation — press it twice and you are back where you started.
4 · The trust ladder
AI work is not trusted by default — it earns trust. Verification stamps and human approvals
promote a snapshot up the ladder, and kal stats aggregates those promotions into
per-model scorecards. This is the mechanism that makes autonomous commits acceptable to a team.
5 · The git bridge — coexist, don't convert
.kal/ and .git/ share one working directory. Sync mirrors snapshots into
git commits whose trailers carry the kal metadata, and imports git commits back by parsing
those same trailers. GitHub, CI, review tools and IDEs keep working — now with provenance attached.