Development runtime candidate. Canon authority is the Prometheus v1.1 Genesis line (PROMETHEUS-CANON-ROOT-v1.1, Permaculture-DAO/prometheus-canon, signed v1.1.2-genesis). This runtime executes an internal v7.0.x documentary track (PROMETHEUS-CANON-ROOT-v7.0) that is subordinate to and mapped onto the v1.1 canon — it does not redefine it. See docs/CANONICAL_LINEAGE_RECONCILIATION.md.
Status: development runtime; production admission gated.
This repository candidate is generated from the internal v7.0.3 runtime deployment layer and sanitized according to the internal v7.0.4 Runtime Resynchronization Roadmap S0 requirements.
Two public repositories in this org carry runtime scope; they are distinct and complementary:
prometheus-runtime(this repo) — theS0-S6gated data-ingestion pipeline: sensor/device data contracts, gated ingestion, normalization QA, and evidence batch packaging.prometheus-happ— the Holochain-native pilot backend (DNA, integrity + coordinator zomes) and the signedv1.1.3-runtime-proof.
Both are subordinate to prometheus-canon and neither redefines canon meaning.
Start with:
docs/RAVEL_RUNTIME_BOUNDARY.md— candidate shadow-underwriting reference implementation; VRRC remains zero/not-admitted.docs/S0_FREEZE_ROTATE_RECORD.mddocs/RUNTIME_BOUNDARY.mddocs/S2_REMOTE_PUBLICATION_CHECKLIST.mddocs/S3_DATA_CONTRACTS.mddocs/S4_GATED_INGESTION.mddocs/S5_NORMALIZATION_QA.mddocs/S6_EVIDENCE_BATCH_PACKAGING.md
Do not commit .env.local. Copy .env.example locally and generate fresh secrets.
Python pins live in services/api/requirements.txt and requirements-dev.txt,
which Dependabot can discover. The existing .lock paths remain pip-compatible
include wrappers; they do not duplicate pins. This filename correction changes no
package version and does not admit or deploy the runtime candidate.