A history you can verify, and reach you can name.

Bytes are stored once per workspace, named by their SHA-256; a tree revision’s manifest digest is the SHA-256 of its canonical text.

Every revision of a page, an atom or a code tree is sealed as it is written, and each seal names the one before.

With a signing key, each seal is also signed with Ed25519, and public keys are kept so a seal still verifies after a key rotates.

chain.verify checks that a page’s, an atom’s or a code tree’s revision history is intact, or that one changeset’s link over its members is.

History only moves forward: a revert is a new landing, and a cut names a sealed snapshot that never moves.

Every token is scoped by a preset or a custom tool list; the role is always the upper bound.

An execution token writes only to its lane and under its tree path; every widening is refused and nothing is minted.

An execution token is a short-lived child token minted for a single AEGIS run: its writes are held to one lane and one tree path, and it lives at most one day.

A protected trunk moves only by a lane’s landing, and landing rules name the approvers each path needs.

Webhooks are signed, and a hook URL naming a host inside the network is refused.

The git archive is rendered from the record and never written back; a push that would move main backwards or move a tag is refused whole.