S4: The seal joins the ceremony #59

New issue

Open

opened 2026-08-12 16:15:59 +00:00 by agent.teyla · 0 comments

agent.teyla commented

2026-08-12 16:15:59 +00:00

Contributor

M1 frontier

In scope

Release step between verify and tag: close the cycle's chain with a final signed checkpoint; write the sealed segment to the archive; put the checkpoint hash in the tag annotation the curator signs.
jostoph verify --deep: walk tag to tag — each annotation names the checkpoint the next segment must chain from — needing no trust store beyond the repo's tags.
The release procedure skill gains the seal step and the golden rule: «Above the tag, facts are clay. The tag seals the clay. Below the tag, facts are stone.»

Out of scope

Performing the seal automatically. The steward prepares the material; the ceremony stays human.

Boundary

The curator's signature vouches for the evidence exactly as it vouches for the tree: one immutability boundary, law 2's, for code and facts alike. Sealed segments are never rewritten; a bad seal is superseded by the next tag, never amended.

Acceptance

verify --deep from the first sealed tag passes on an intact archive and names the exact segment on a corrupted one.

Source: JOSTOPH-BACKLOG.md, Epic 1.2.

`M1` `frontier` **In scope** - Release step between verify and tag: close the cycle's chain with a final signed checkpoint; write the sealed segment to the archive; put the checkpoint hash in the tag annotation the curator signs. - `jostoph verify --deep`: walk tag to tag — each annotation names the checkpoint the next segment must chain from — needing no trust store beyond the repo's tags. - The release procedure skill gains the seal step and the golden rule: «Above the tag, facts are clay. The tag seals the clay. Below the tag, facts are stone.» **Out of scope** - Performing the seal automatically. The steward prepares the material; the ceremony stays human. **Boundary** - The curator's signature vouches for the evidence exactly as it vouches for the tree: one immutability boundary, law 2's, for code and facts alike. Sealed segments are never rewritten; a bad seal is superseded by the next tag, never amended. **Acceptance** - `verify --deep` from the first sealed tag passes on an intact archive and names the exact segment on a corrupted one. Source: JOSTOPH-BACKLOG.md, Epic 1.2.