krineia.com
Open standard · Participation
The standard
is open.
KRINEIA is a draft open standard for append-only, cryptographically chained governance receipts. This is where you propose changes, adopt the format, or join the community of practitioners building tamper-evident governance into their systems.
v1.0-rc2 invariants · v2.1 signed receipt schema proposed
maintainer
your repo
Three paths · all open
01 / Propose
Change the standard
through the standard.
Start with the public reference snapshot, then send a concrete proposal to the maintainer. The original repository remains private; you do not need access to its issue tracker to participate. Submission does not itself amend or ratify the draft standard.
Read the current spec
The v1.0-rc2 invariants, v2.1 receipt schema, and operator semantics are available in a public source snapshot with a per-file provenance manifest.
Read the public referenceSend a change request
Email reuben@hummbl.io with subject KRINEIA proposal. Include the snapshot commit, affected file or clause, proposed change, and rationale or reproduction. Request repository access there when needed. Do not include credentials or private operational data.
Submission and setup guideCheck proposal status
The signed v2.1 profile is proposed, not ratified in this snapshot. Its public manifest identifies the exact source and exported files. Private operational receipt chains are not included or required for reading this reference.
Snapshot provenance02 / Adopt
Three operators. Your system.
Adoption means implementing the three operators — append, project, and cut — against your own governance record. No fourth operator. No hidden extension. The boundary is the standard.
append()
Extend the chain
Add one new, hash-linked receipt to your governance record.
project()
Read a view
Derive an inspectable projection without mutating the record.
cut()
Bound a slice
Select a reviewable segment while preserving its provenance.
Reference verifier
tools/verify_chain.py — stdlib-only structural
verification. Strict v2.1 Ed25519 verification requires the
cryptography package.
Reference watcher
daemon/krineia_watcher.py — a daemon that observes
and records receipts. Use it as a reference for your own observer
implementation.
Receipt schema
spec/RECEIPT_SCHEMA.md — the v2.1 signed receipt
schema proposal and the explicitly supported legacy formats.
Strict signed verification and legacy structural inspection have
different assurance boundaries.
03 / Join
The community is the standard.
A standard without practitioners is a document. KRINEIA is maintained by HUMMBL, LLC, but its value depends on the people who implement, test, and depend on it. If you are building tamper-evident governance into a system, you are already part of this.
Can do read the public source, propose changes, implement the operators, publish your adoption, and report what breaks.
Not yet formal membership, working group registration, or governance voting rights. The standard is draft; the organization is emerging.
04 / Changelog
What changed, and when.
Invariants
v1.0-rc2 — current draft
Signed schema
v2.1 — proposed, not ratified
Legacy format
v0.1 — unsigned, unauthenticated
License
Dual MIT / Apache-2.0
The September 26, 2026 public snapshot pins the source commit and file hashes. It publishes a bounded reference package, not the private repository's operational history. Read the schema change history or download the snapshot.
05 / Constellation
A peer satellite in the HUMMBL mesh.
KRINEIA stays runtime-agnostic so systems beyond HUMMBL can adopt the standard. HUMMBL depends on KRINEIA; KRINEIA does not import HUMMBL.