docs(g51): specify base-controlled AF-02 governance amendment path

Closed
TH
7d ago
+242-0

Purpose

Start the first independently reviewable P0 planning grain without waiting for V3.2 execution-authority migration. This is a standalone, planning-only Spec Kit G51, informed by—but not dependent on merging—V3.2 candidate PR #187. Canonical V2 remains the only execution authority.

Exact observed frontier

  • main before branch: f82565cca917d119e1c774b2c470e2ac20e0d6dd
  • proposed head: 5178cb51572b90f99917e7c440cff1ce66ca06fb
  • historical AF-02 blocker: specs 049 and 050; issue #100 remains open.

Changes

Adds only specs/051-af02-governance-amendment-path/:

  • spec.md: problem, scope, required non-circular invariants.
  • plan.md: proposed two-PR, base-controlled amendment flow and distinct one-time bootstrap.
  • tasks.md: planning versus implementation gates, all implementation tasks unchecked.
  • threat-model.md: 20 fail-closed adversarial cases.
  • consistency.md: authority conflicts and non-claims.

No edits to workflows, Rust code, lockfiles, donor records, AF-02 authority files, or rulesets. No GitHub issue is closed.

Review requirements

  • Qualify CI at the current exact head, not older PR evidence.
  • Real human Code Owner approval per live rulesets.
  • OCR's lack of Markdown support is NOT a review PASS, and Jev must not be claimed without actual execution.
  • No FD-1 exception is approved. A future bootstrap must first be written, independently reviewed, and explicitly authorized by the founder for its exact base/head and changed file blob OIDs. FD-2 (required check) remains separate.
  • Normal merge commit only; no bypass, squash, rebase or force-push.

Relationship to PR #187

PR #187 remains an independent V3.2 planning candidate. If both PRs are adopted, reconcile their status/sequence and deduplicate overlapping amendment-path prose at the eventual migration gate. Merging this Spec Kit alone does not promote V3.2 or activate AF-02 A0.

Summary by cubic

Adds planning-only Spec Kit G51 specifying a base-controlled, two-PR governance amendment path for AF-02 protected paths, starting independent review without waiting on V3.2 migration PR #187.

  • Requires exact Git blob OID bindings, prior merged amendment records, and separate founder FD-1/FD-2 grants before any protected edit or check-required change.
  • Defines 20 fail-closed adversarial cases for tampering, stale records, candidate-only data, and approval spoofing.
  • Adds only files under specs/051-af02-governance-amendment-path/; no workflows, code, lockfiles, donor records, or protected paths change, and no issue is closed.
  • Canonical V2 remains the only execution authority; merging this does not promote V3.2 or activate AF-02 A0.