Public Rule Registry¶
Registry — instantiates Reflexive Rule-Binding Governance
Maintains a single authoritative, openly readable catalog of the operative rules and exactly who they govern, so the rule in force is knowable in advance rather than held privately by the enforcer.
A rule that only the enforcer can see is not a rule so much as a discretionary power dressed as one — the authority can claim afterward that the rule always said whatever suits the case. The Public Rule Registry removes that privacy. It is the standing, authoritative catalog of the operative rules, openly readable, that also names the domain each rule governs — which entities, roles, sites, and time periods are in scope. Its defining property is that the canonical text lives in the open and in one place: there is a single answer to "what is the rule, and does it apply to me?" that anyone can look up before acting, rather than a private version the enforcer consults after the fact. It is not the process for changing rules and not the record of how they were applied; it is the current, knowable statement of what the rules are and whom they bind.
Example¶
An open technical-standards body such as the W3C develops the specifications that browsers and websites must follow. Rather than distributing rules privately to favored vendors, it maintains its specifications as openly published documents, each with a clear status (draft, candidate, recommendation) and an explicit statement of scope — which features, which conformance classes, which implementers are covered. Anyone building a browser can read the exact, current normative text and see precisely what conformance requires.
The registry's value is that no implementer can be blindsided by a rule they had no way to know. Because the operative specification and its scope are public and singular, a vendor cannot be told after shipping that the "real" requirement was something never written down, and the standards body cannot quietly hold a different rule for insiders. The rule is what the published registry says it is — for everyone it names.
How it works¶
- Single source of truth. One canonical location holds the operative text; copies are derived from it, not authoritative against it, so there is no ambiguity about which version governs.
- Open readability. The rules are published in a form any governed party can access and understand in advance, not gated behind the enforcer's discretion.
- Explicit scope statements. Each rule carries a register of what it governs — the entities, roles, and periods in its domain — so applicability is a lookup, not an argument.
- Status and currency markers. The registry distinguishes what is in force now from what is draft, retired, or superseded, so "the current rule" is unambiguous.
Tuning parameters¶
- Granularity of scope tags — how finely the governed-domain register is drawn. Fine tags make applicability precise but heavy to maintain; coarse tags are cheap but leave edge cases arguable.
- Readability vs. precision — plain-language rules are accessible but ambiguous; formally precise rules are unambiguous but opaque to lay readers. Registries often must carry both layers.
- Access breadth — fully public, or open only to the governed population. Wider access maximizes accountability; narrower access may be needed where the rules themselves are sensitive.
- Canonicalization strictness — how hard the registry insists that all copies defer to it. Strict canonicalization prevents drift but requires discipline to keep every downstream copy in sync.
When it helps, and when it misleads¶
Its strength is that it makes the rules knowable in advance, which is the precondition for every other constraint in the archetype — you cannot bind an authority to a rule, test equal application, or audit a decision against a rule that was never fixed and published. Publicity is the antidote to "secret law," the condition in which the operative rule is whatever the enforcer later says it was; a public registry is what lets people order their conduct by rules they can actually read.[n1]
It misleads when publication is confused with fixity or with obedience. A registry documents what the rules are; it does not stop them from being changed at whim (that needs an amendment protocol) and it does not stop them from being applied unequally to those it names (that needs testing and audit). A common failure is the technically-public-but-practically-unfindable registry — rules posted where no one can locate them, or so voluminous and unindexed that publication defeats the purpose. Another is drift: unversioned edits that let the "current" rule quietly change under readers' feet. The guarding discipline is to keep the registry genuinely findable, singular, and currency-marked, and to route every change to it through a governed amendment path rather than a silent edit.
How it implements the components¶
public_rule_surface— it is this component: the open, authoritative surface on which the operative rules are published and made knowable in advance.governed_domain_register— each rule's explicit scope statement enumerates the entities, roles, and periods it governs, so applicability is looked up rather than argued.
It does not govern how a rule may be changed or guarantee advance notice of edits — that rule_bound_change_rule and retroactivity_guard belong to amendment_and_notice_protocol.md — and it does not record how each rule was applied to specific actions: that rule_to_action_trace is rule_application_audit_log.md.
Related¶
- Instantiates: Reflexive Rule-Binding Governance — supplies the open, singular statement of what the rules are and whom they bind.
- Sibling mechanisms: amendment_and_notice_protocol.md · rule_application_audit_log.md · supremacy_clause.md · policy_as_code_guardrail.md
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Public Rule Registry operates as a persistent ledger, log, register, or case record that preserves history and traceability because it maintains a single authoritative, openly readable catalog of the operative rules and exactly who they govern, so the rule in force is knowable in advance rather than held privately by the enforcer.
Independent corroboration: The frozen evidence defines Public Rule Registry as 'Maintains a single authoritative, openly readable catalog of the operative rules and exactly who they govern, so the rule in force is knowable in advance rather than held privately by the enforcer', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: A publicly knowable authoritative catalog of operative rules expresses the legal tradition of promulgation and rule of law.
Related originating lineages:
- Library & Information Science — Cataloging and authority control supplied discoverability and canonical-version management.
- Public Administration & Policy — Administrative registers operationalized publication and scope of operative rules.
Review resolution: Both blind reviewers agree on law_governance as the primary origin. Explicit reconciliation resolves encyclopedia_synthesis_disagreement. The merged alternate lineages retain only domains the reviewers identified as materially formative; domain_reach=multi_domain records later applicability separately from origin breadth.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Lon Fuller's account of the "inner morality of law" holds that rules people cannot know in advance — secret, unpublished, or unknowable rules — fail to function as law at all, because no one can conform to a rule they cannot read. A public registry is the operational answer to that promulgation requirement. ↩