Releases: Permaculture-DAO/prometheus-canon
Release list
h•eart•h Prometheus — Genesis v1.1.2 (signed)
Release Notes — v1.1.2-genesis
Status
v1.1.2-genesis is the text- and table-complete canonical White Paper of record
for the h•eart•h Prometheus v1.1 Genesis Institutional Canonical Line. It is
prepared for signing (freeze-prep complete); detached GPG signatures are
generated by the release maintainer (see RELEASE_SIGNING_READINESS.md).
White Paper of record
canonical/h-earth-prometheus-white-paper.docx— source of truth (Full
Corpus v1.1.2). SHA25629f91e6d6a31fb8bd9754a7ef32ea8b7f168bf64fa7097cf9b6ee951ab9fca04.canonical/h-earth-prometheus-white-paper.md— readable derivation (pandoc).
SHA256f3862005bc4d6e8e4cba0f2a7646e67dff758fcd28c8411046eb5d04875f9540.provenance/v1.1.2/…strict.md— reproducible table-complete derivation.
The Full Corpus supersedes the prior v1.1.0-rc.2-strict lineage (preserved under
canonical/_superseded_rc2_strict/). The corpus passes the master-prompt v3.1
gap-audit: all A–X sections + matrices (Howey, MiCA, Legal Semantic Firewall,
Red-Team, Capital-Readiness, Scientific Falsifiability, H1–H5 mapping, Jacobi/Lancet
anchor, custody / self-falsifiability / anti-overproduction, human-state weight=0).
Canon amendments in this release
canonical/AMENDMENTS/A-001— HSI bound under human-state weight=0.canonical/AMENDMENTS/A-002— consolidated Legal Semantic Firewall table.
Disclosure: A-001/A-002 are adopted as versioned clauses and are part of
this signed release. Their incorporation into the source DOCX prose body is
deferred to v1.1.3 (a separate weave). Until then the canon governs via the
corpus + these clause files together.
Custody disclosure (required)
This canon is substantially single-source: v1.1.2-genesis is a release signed by
a single authority, not yet shaped by more than one authoring process nor
ratified by multiple active stewards. The signature attests authenticity and
integrity, not multi-steward constitutional ratification.
Signing boundary
Final SHA256 sets and detached .asc GPG signatures are generated only from the
release maintainer environment, with the authorized key 8C8CB0D48C7F60DA, after
this freeze-prep. See RELEASE_SIGNING_READINESS.md and CHANGELOG.md.