PGA v0.2.1 — Public Machine-Readable Specification Projection

Public, license-cleared projection of the frozen PGA-v0.2.1 execution-governancespecification. PGA specifies a narrow fail-closed boundary between computation andpermission: capability, proposal, commitment, and execution authority are distinctstates, and a proposed action reaches execution only through typed provenance, currentpolicy and gate bindings, exact scope agreement, an optional hash-bound humanauthorization receipt, a final recheck, an acyclic authority decision, an immutablesingle-use execution token, and an atomic commit transaction. Missing, stale,conflicting, expired, replayed, or unbound authority-critical inputs fail closed. This projection contains the PGA-created specification, schema, hash-profile, trace,test, and status material authorized for publication (17 byte-exact files copied fromthe frozen manifest), together with lineage pins naming the frozen checkpoint and theomitted objects by hash and status. It is a publication object in its own right and isNOT byte-identical to the frozen checkpoint. CONTENTS- Governance specification, formal state model, and threat/trust model (Hungarian normative masters)- Machine schema (JSON Schema Draft 2020-12; 61 $defs, 454 local references, 63 closed object schemas, no defaults)- Canonicalization and hash-profile registry (PGA-CANONICAL-JSON-V1, RFC 8785 derived; 11 self-hash profiles, 11 record-digest profiles, 54 cross-record bindings, 0 declared dependency cycles)- Conformance and kill-test catalogue (165 CT + 18 KT)- Decision and traceability register (296 records: 183 requirements, 71 test vectors, 20 residual risks, 19 decisions, 2 fixtures, 1 evidence record)- B-CORE gate binding register, source freeze, content-freeze authority, changelog, internal QA, two test fixtures, projection validator IDENTIFIERSFrozen checkpoint (not included here): SHA-256 b9140a84a369a3adb79e733ed2e9eb085ba3eeea35a99524ed195c4bbcceea7e size 8,958,239 bytesPublication projection archive (this record): SHA-256 a7fe1fa96ef3036a68d1feaced25f79d33eaf4dd7972b8ba40a7ff080b165a02 size 612,861 bytesThree lineage archives are omitted because they embed private, predeposit, draft, ornot-published antecedent material: the v0.2 content checkpoint, the v0.2 reference-implementation negative-evidence checkpoint, and the v0.2.1 pre-freeze candidate. STATUS — PART OF THE RESULT- Content-frozen specification checkpoint; not an implementation, security proof, or deployable control.- Conformance tests: 165 of 165 NOT_RUN. Sufficiency kill tests: 18 of 18 NOT_RUN. Total 183 of 183 NOT_RUN; 0 PASS.- Reference implementation: NOT_STARTED.- External audit: NOT_PERFORMED.- B-CORE production gate bindings: 9 of 9 UNBOUND, with UNBOUND -> BLOCKED semantics.- System and production execution authority: BLOCKED.- AGI completeness claim: NONE. Security or safety guarantee: none.The internal structural validator reports PASS; that result covers only the checks itperforms on the frozen bytes and is not conformance evidence. METHODOLOGICAL NOTEPGA-v0.2.1 is a remediation of PGA-v0.2. An attempted reference implementation of v0.2stopped before producing any PASS result, having found three normative defects: acontent-hash cycle between an authority decision and its execution token; an audit-eventself-hash whose preimage included the hash field itself and duplicated its predecessor;and ambiguity between mutable token state and the stable token digest named by a commitreceipt. Two amplifying gaps were also exposed: an undefined canonical JSON profile anda prose-schema field mismatch. The v0.2 bytes are preserved as negative implementabilityevidence rather than edited in place. NOTE ON EMBEDDED DOI STATUSFiles inside the archive record doi_status = RESERVED_NOT_PUBLISHED, which was accurateat freeze time. Those bytes are immutable by design and are not updated by thispublication action. LICENSINGCC BY 4.0 applies to authorized PGA-created documentation and data; Apache License 2.0applies to authorized source code. See LICENSE_MAP.json in the archive: the record-levellicences do not override per-file scope, and no licence statement here expands rights inexcluded or third-party lineage objects.