Prometheus hApp — Genesis Runtime

Prometheus v1.1 — Genesis Institutional Canonical Line

This repository is the clean Holochain-native pilot runtime repository for the Prometheus v1.1 Genesis line.

The primary canonical source repository is:

Permaculture-DAO/prometheus-canon

This repository implements bounded pilot runtime behavior.

It does not define Prometheus constitutional meaning.

Repository status

Current status:

Bounded synthetic runtime proof — signed v1.1.3

The current signed runtime proof is v1.1.3-runtime-proof. It demonstrates the recorded synthetic MQTT-to-Holochain B0-B8 scope only.

It does not establish production readiness, empirical or agronomic validation, universal duplicate prevention, certification, legal admission, market admission, financial value, or rights.

Signed canonical documents and verification materials are indexed at prometheus-canonical-releases.

Runtime role

This repository is expected to contain the Holochain-native backend implementation layer for the Prometheus pilot stack, including:

• DNA;
• integrity zomes;
• coordinator zomes;
• validation-bound records;
• source-chain-based runtime behavior;
• bounded pilot backend logic;
• runtime integration notes.

Canonical boundary

The White Paper and prometheus-canon define meaning.

This repository implements behavior.

Runtime code, zome functions, hApp manifests, tests, build artifacts, or generated outputs must not silently redefine:

• PRU logic;
• RAP inclusion;
• TRBK role;
• HoloFuel role;
• investor exposure;
• land rights;
• legal meaning;
• governance authority;
• ecological credit issuance;
• capital-facing claims.

Legacy boundary

The previous pre-v1.1 runtime repository has been moved to:

Permaculture-DAO/legacy-prometheus-happ-pre-v1.1

Legacy code may inform this repository.

Legacy code does not govern this repository.

Any legacy module, zome, manifest, build configuration, or runtime behavior must be explicitly reviewed before reintroduction into this Genesis runtime line.

Pilot-first discipline

This repository follows pilot-first discipline:

• explicit scope before expansion;
• behavior before abstraction;
• validation before execution;
• runtime clarity before scale;
• implementation fidelity before architecture drift;
• canonical boundary before runtime claim.

Related repositories

Primary canonical source:

• Permaculture-DAO/prometheus-canon

Runtime-facing repositories:

• Permaculture-DAO/prometheus-bridge
• Permaculture-DAO/prometheus-console
• Permaculture-DAO/prometheus-runtime — the S0-S6 gated data-ingestion and evidence-batch-packaging pipeline. Distinct from this repository: prometheus-runtime is the ingestion/normalization layer, while this prometheus-happ is the Holochain-native backend (DNA, zomes) and the signed v1.1.3-runtime-proof.

Operational and evaluation repositories:

• Permaculture-DAO/prometheus-ops-docs
• Permaculture-DAO/prometheus-evaluation-stack
• Permaculture-DAO/prometheus-pilot-handoff-pack
• Permaculture-DAO/prometheus-mock-backend

Operational rule

Persistence-gate candidate (#32) is a runtime-line migration: the additional sensor identity, evidence class and calibration fields change the entry schema; the integrity changes also change the DNA hash. The signed v1.1.3-runtime-proof and existing live sandbox do not prove this candidate. Rebuild and pack the DNA, record its new hash, and run conductor tests against that exact bundle before steward-approved migration. REAL persistence stays closed in integrity validation.

CI runs integrity unit tests, including the REAL gate and calibration format; the host-only sweettests remain a separate manual gate and are not CI evidence. Run them after packing the candidate with cargo test --manifest-path integration_tests/Cargo.toml --test conductor.

Use --locked: the host-only lockfile pins ed25519 3.0.0-rc.4, pkcs8 0.11.0-rc.11 and signature 3.0.0-rc.10 with ed25519-dalek 3.0.0-pre.1; resolving their final releases with that prerelease fails to compile. The conductor test is pinned to Holochain 0.6.1. Persistence idempotency includes sensor_id; domain no-double-counting still uses subject + indicator + time, conservatively preventing two sensors from both counting the same observation.

Runtime behavior lives here.

Canonical meaning lives in prometheus-canon.

Bridge/API behavior lives in prometheus-bridge.

Frontend behavior lives in prometheus-console.

Legacy runtime history remains outside the active path unless formally reintroduced.

Public visibility and license boundary

Public visibility enables inspection and verification. This repository currently declares its software packages UNLICENSED; visibility alone is not a grant to copy, modify, redistribute, deploy, or commercially use the code. A separate license decision is required before representing this repository as open source.

See PUBLICATION_BOUNDARY.md.