Who signs the first piece of evidence: the off-axis epoch anchor

Reading the Draft · No. 5 · Source: draft-li-rttp-iqa-addressing-00 §1 / §5.1 · Reference specification AICENT-009 · Sister pillars: rttp:// (CRI 27) · iqa:// (CRI 28)

It is the initial-value problem shared by every trust system: verification relies on envelopes, envelopes rely on keys, and the legitimacy of a key relies on an earlier piece of evidence — walk the chain backward, and where does the first link hang? Theology calls it the first cause; engineering calls it trust bootstrap. Our answer comes in three steps, all priced openly.

Step one: admit there is no free lunch. The first piece of evidence in any system comes from some starting point outside the system — a CA's root certificate is self-signed, a registry's first administrator is hand-configured. Systems that claim "our trust chain has no beginning" have merely hidden the beginning somewhere the document does not go. We choose to write the starting point into the specification and give it a name: genesis.

Step two: pin the anchor off the axis. Genesis is one of the four standing states (ghost / probation / radiant / genesis), but the only one that can be neither earned nor lost: radiant is maintained by the 120-second lease and can rise or fall; genesis takes no part in that daily re-pricing — it is the anchor of an epoch, not a rank on a leaderboard. Section 5.1 makes the organ a closed set (forge / tss / gateway): "This is a closed set; no other value is valid" — the organ's grammatical legitimacy is guaranteed by the closed set, and why an organ is worth trusting is anchored, at its source, to the epoch's starting point, as defined by the reference specification.

Step three: the protocol does not own genesis. This is our deepest split from the registry route: the registry's anchor is an operator's configuration list; ours is an off-axis marker that moves with no operator's will. Multiple genesis anchors coexist without adjudicating one another — not monopolizing the starting point means any community can begin building from its own epoch anchor, and the choosing between anchors is left to relying parties' adoption, not to some "official" ruling. The address has no landlord; neither does creation.

Pressed one level deeper — the security parameters of the genesis anchor itself — the answer is equally in the open: the anchor's material and rotation are defined by the reference specification AICENT-009; the merged document deliberately cites without repeating — the URI scheme handles addressing, the algorithm lives in the specification, and the layering is clean.

One line: the signer of the first piece of evidence is not an organization but the epoch itself — genesis is unearnable and unlosable, so no one can revoke it, including us.