h•eart•h Prometheus — Genesis Canon

Prometheus v1.1 — Genesis Institutional Canonical Line

This repository is the primary canonical staging repository for the Prometheus v1.1 Genesis Institutional Canonical Line.

It is maintained under:

Permaculture-DAO/prometheus-canon

This repository is not a legacy continuation, patch, or automatic upgrade of any previous Prometheus repository, release, hash set, signature set, runtime artifact, or development archive.

Pre-v1.1 materials are treated as historical development artifacts unless explicitly reintroduced through the v1.1 signed canonical release process.

Repository status

Current status:

Genesis canonical release line — signed v1.1.2

The controlling signed release is v1.1.2-genesis. Its signature attests authenticity and integrity; it does not imply empirical, legal, market, financial, or multi-steward constitutional validation.

Later files or local documents are candidates only until they pass the canonical amendment, review, hash, signing, and release procedure.

The minimal public verification copy is maintained in prometheus-canonical-releases. The complete historical freeze archive remains private.

Source of truth

The source-of-truth document for this Genesis line is:

• canonical/h-earth-prometheus-white-paper.docx

The canonical Markdown derivatives staged for review are:

• canonical/h-earth-prometheus-white-paper.md
• canonical/h-earth-prometheus-white-paper.source.md

The DOCX remains the controlling source document until final textual freeze.

Canonical ontology

Prometheus v1.1 defines Prometheus as verified regenerative infrastructure, not a public offering and not a token-first system.

The operative ontology is:

• OHE generates regenerative performance;
• MRV and provenance make evidence reviewable;
• PRU provides the value-analysis and maturity-classification interface;
• RAP aggregates verified units into portfolio-grade regenerative infrastructure;
• TRBK supports governance, coordination, access, or participation within legal boundaries;
• HoloFuel supports operational transaction and infrastructure capacity;
• any future financial or digital instrument requires a compliant legal wrapper, jurisdiction-specific review, disclosure, and investor-protection discipline.

Verification-first rule

Prometheus follows this progression:

claim → observation → evidence → provenance → integrity → verified indicator → admissibility → value

No ecological claim, PRU maturity class, RAP inclusion, investor-facing interpretation, tokenized representation, or capital-facing statement should bypass evidence, provenance, confidence scoring, admissibility, governance review, and legal review.

Runtime boundary

The White Paper defines meaning.

Runtime repositories implement bounded pilot behavior.

The Holochain hApp, bridge, console, evaluation stack, mock backend, operations documentation, and pilot handoff repositories must not redefine Prometheus ontology.

Runtime artifacts do not create PRU value, investor rights, token rights, land rights, ecological credits, governance authority, or capital-facing claims by themselves.

Hash and signature boundary

This repository contains both signed-release material and later staging controls.

Only files bound to a signed tag or release manifest are part of a signed release. Staging manifests, audits, checksums, amendments, and working documents do not silently modify v1.1.2-genesis.

Legacy boundary

Pre-v1.1 repositories, releases, drafts, hashes, signatures, generated packs, runtime artifacts, and development materials are historical development artifacts.

They are not part of the active canonical release path unless explicitly reintroduced through the v1.1 signed canonical release process.

No legacy artifact may silently become canonical by being copied into this repository.

Founder mirror

The founder publication mirror is expected to be:

Uwohali/hearth-prometheus-whitepaper

That mirror may publish or mirror canonical content, but it does not supersede this repository unless explicitly synchronized through the signed canonical release process.

Operational rule

Canonical meaning lives here.

Runtime behavior lives in runtime repositories.

Operational discipline lives in operations and evaluation repositories.

Public visibility boundary

Public visibility supports inspection, verification, and defensive publication. It does not turn architectural specifications into proof, create rights, or expand any license beyond the notices included with the relevant material. See PUBLICATION_BOUNDARY.md.

Founder publication lives in the Uwohali mirror.

Legacy material remains outside the active canonical path unless formally reintroduced.