§54.1 Function

RGP-01 names release governance as a first-class constitutional act. A surface that cannot prove its release identity is not part of the civilization; it is impersonating one.

§54.2 Provenance Binding

Every release carries a four-field provenance record. The record is published, citable, and verifiable against CI without operator mediation.

json
{
  "deployment_identity": "kiri:release/<release_id>",
  "ci_provenance":       "build hash, builder identity, source commit, signed",
  "ratification_link":   "GPL-01 proposal that authorized publish",
  "rollback_lineage":    "ordered list of prior release_ids back to the last stable anchor"
}

§54.3 Rollback Continuity

Rollback is not the reverse of release. It is its own forward act, carrying its own release identity and citing the lineage it returns to. The civilization moves forward through every transition — including the ones that return it to a prior state.

1. §54.3.a
   Lineage is published

   Rollback lineage is part of the provenance record, not a separate artifact.

2. §54.3.b
   Anchored to stable

   Every lineage terminates at a release explicitly marked stable under GPL-01.

§54.4 CI Provenance

CI provenance is the unforgeable substrate of release identity. A release whose CI provenance cannot be verified is, by this article, draft — never production.

§54.5 Bounded Scope

RGP-01 does not modify governance, does not introduce new APIs, and does not redefine ratification. It ratifies the deployment provenance the civilization already publishes.

§54.6 Final Principle

A release without lineage is a rumor. RGP-01 ends the rumor by binding lineage to every publish.

“Every release is a published act with a published ancestry.”