Quickstart (90 seconds)
The canonical path: Create → Verify → Publish → Registry. Get a VALID public proof with hash-only exposure.
- Generates private release artifact
- Computes payload_sha256
- Publishes minimized proof to append-only registry
DOCS · HUB · DETERMINISTIC · FAIL-CLOSED
Documentation
Minimal docs for operational use. If you can’t prove it deterministically, you don’t claim it. Public surface is hash-only, evidence is append-only, validation is fail-closed.
Docs are part of the control system: they reduce ambiguity
FAIL-CLOSED NOTICE · DOCUMENTATION POSTURE
No ambiguity, no “maybe”
HBCE documentation reflects the protocol posture: deterministic rules, minimized public exposure, append-only evidence. If a step is missing, the result is INVALID.
Start here
Operator path
How to obtain an Operator License starting from a VALID IPR Base (published proof required).
- Base proof must exist publicly
- Operator issuance is gated (fail-closed)
- Publish operator proof (hash-only)
Governance references
Protocol
HBCE-CORE / VERIFY / HBCE-REGISTRY stack, in one page. End-to-end workflow links included.
/protocol/Compliance posture
EU-first audit posture: hash-only, append-only, deterministic, fail-closed. Responsibilities and limitations.
/compliance/Activation wizard
Activation sequence with explicit Publish gate and closed loop.
/activate/