Publication Boundary
What is public: canonical fingerprints, receipt references, version provenance and non-sensitive summaries. What remains controlled, off-chain: plaintext documents, operational logs, sensitive submissions and protected evidence, accessible only under defined review procedures and lawful basis.
Canonical definition
The publication boundary is the rule that distinguishes what the framework discloses publicly from what remains in controlled custody, so that decisions are auditable without exposing sensitive plaintext.
Why this node exists
Integrity and auditability are achieved through fingerprints, receipts and structured reasons, while plaintext stays off-chain. Without the boundary, transparency would either leak or stall.
Operational meaning
Public, minimal and sufficient: canonical fingerprints for released artefacts, deposit receipt references, version provenance with label, timestamp and deltas, and non-sensitive summaries. Controlled, off-chain: plaintext documents, operational logs, sensitive submissions and protected evidence, accessible only under defined review procedures, lawful basis and standing, with access docketed. Evidence is packaged as bundles with manifests, integrity references and custody notes even while it remains controlled.
What this does not mean
"Off-chain" is not secrecy for its own sake. Confidential materials may be disclosed in camera or under controlled review windows when required, and courts have access to unredacted records under confidentiality where the Constitution provides.
Canonical facts
- Public
- fingerprints, receipt references, version provenance, non-sensitive summaries (Statute §6.2)
- Controlled
- plaintext, operational logs, sensitive submissions, protected evidence (Statute §6.3)
- Rule
- plaintext is never written on public ledgers; only digests and receipts (Mandate Q6)
Structural relationships
Outgoing
Incoming
- Board Statute defines Publication Boundary
- Public Record applies Publication Boundary