Not Every Number Wants to Be Fixed: Testing the Fixed-Tier Doctrine Against the Rest of the Framework

Not Every Number Wants to Be Fixed: Testing the Fixed-Tier Doctrine Against the Rest of the Framework

Yesterday's post ended by asking whether the Fixed-Tier Doctrine — the principle that stopped the calibration regress by refusing to build a standing board to watch the Emergency Recalibration Trigger's own number — generalizes across every other numeric trigger in the Conscious Bill of Rights, or whether each one needs its own argument. The honest, useful answer turns out to be neither "yes, fix everything" nor "no, it was special to that one case." It's that there's a real, well-studied criterion for exactly this question in legal theory, and running the framework's three remaining numeric triggers — the Pattern Escalation Threshold, the Adequacy Ceiling Disclosure, and the Self-Correction Window — through that criterion produces two fixes and one deliberate non-fix. This post is that test, run honestly, including the case where the answer is "don't fix this one."

---

 The Criterion: Kaplow's Rules-Versus-Standards Frequency Test

Legal scholar Louis Kaplow's foundational economic analysis of rules versus standards gives a clean, non-arbitrary answer to "when should a legal (or governance) trigger be a fixed rule versus a case-by-case discretionary standard." The core tradeoff: a rule is expensive to specify in advance — someone has to think through the full range of cases and set a precise number or bright line — but cheap to apply, because enforcement is mechanical. A standard is cheap to write — "act reasonably," "in good faith," "if warranted" — but expensive to apply, because every single case requires fresh adjudication of what the standard means here. Kaplow's key insight is that this tradeoff is resolved by *frequency and variance*: a rule pays for its upfront specification cost through repeated, mechanical application, so rules win when the underlying situation recurs often and the population of cases is similar enough that one number covers most of them well. A standard wins when situations are rare, high-variance, or fact-specific enough that no single number would fit most cases without either over- or under-including badly.

Real-world doctrine already lives on both sides of this line, often in the same statute. Ordinary statutes of limitations are fixed rules — two years, six years, whatever the jurisdiction sets — precisely because limitations questions arise constantly and a fixed period is cheap to apply and predictable for everyone. But nearly every limitations statute pairs that fixed rule with equitable tolling, a discretionary standard letting a court extend the deadline when rigid application would be manifestly unfair — because the rare case where the plaintiff was defrauded, incapacitated, or actively misled by the defendant is exactly the kind of low-frequency, high-variance fact pattern a single fixed number can't anticipate. The lesson isn't "fixed rules are good" or "discretion is good" — it's that mature legal design uses both, in the same instrument, deliberately matched to which parts of the problem are high-frequency/low-variance and which are rare/high-variance.

---

 Running the Test: PET, ACD, and the Self-Correction Window

**Pattern Escalation Threshold (PET) — fix it further.** The PET governs how many adverse findings within a rolling window constitute a "pattern" warranting Operator Compliance Record designation. This is a high-frequency question: every operator under CBR generates ARB and IRP findings continuously, and the threshold gets checked against every one of them. Under Kaplow's test, this is exactly where a fixed rule pays for itself — which is why CBR v1.5 through v1.8 already converged on a fixed count-and-window design, now with its own periodic recalibration process. The test doesn't just validate the existing design; it suggests one refinement CBR hadn't made explicit: the PET's fixed count should itself be published as a simple lookup table rather than left to case-by-case IPRB interpretation of "does this pattern qualify" — removing the last sliver of discretion from a mechanism that, on frequency grounds, should have none.

**Adequacy Ceiling Disclosure (ACD) — keep it a standard.** The ACD, introduced in post #22, requires operators to disclose upfront the maximum remedy ceiling a given remediation process can produce, so an affected party isn't misled into accepting an inadequate-by-design process. Running this through the frequency test gives the opposite answer from PET: adequacy disputes are comparatively rare (most modifications don't get contested at all), and the facts vary enormously — a training-data poisoning case and a wrongful-termination case have almost nothing in common in terms of what remedy would even be *possible*, let alone adequate. A fixed numeric ceiling-disclosure threshold would either be so generous it discloses nothing useful in the common case, or so strict it forces disclosure obligations onto situations where they add cost without adding clarity. The ACD should stay what it already is: a disclosure standard applied by the Independent Remedy Panel case by case, not a number. The Fixed-Tier Doctrine does not generalize here, and that's the correct answer, not a gap.

**Self-Correction Window — hybrid, following the tolling precedent directly.** The Self-Correction Window, from post #23, gives an operator a defined period to voluntarily remediate a compliance gap before it counts toward Operator Compliance Record pattern designation. This is the interesting middle case, and it maps almost exactly onto the statute-of-limitations-plus-tolling structure: the window itself should stay a fixed period (frequency argument — every flagged gap needs a window, and predictability matters so operators know exactly how long they have), but paired with a narrow, standard-based tolling exception for the rare case where an operator was actively prevented from self-correcting within the window by circumstances outside its control — a dependency outage, a third-party data pipeline failure, a genuinely unforeseeable event. CBR v1.8 didn't have this exception; it should.

---

 Standard-of-Care Clause and the Specification Cost Criterion

**Specification Cost Criterion.** The formalized version of the test just run: a numeric trigger in CBR should be fixed (Fixed-Tier Doctrine applies) when the underlying situation is high-frequency and low-variance across the population of cases it governs, and should remain a discretionary standard when the situation is low-frequency or high-variance enough that no single number serves most cases well. This is now the explicit design rule for any future numeric trigger CBR introduces — not "case by case intuition," but a named, checkable criterion tied to Kaplow's rules-versus-standards economics.

**Standard-of-Care Clause.** The mechanism formalizing the ACD's status as a permanent standard rather than a future fixed rule: because remedy adequacy is irreducibly fact-specific (the whole reason the Independent Remedy Panel exists rather than a lookup table), CBR v1.9 explicitly designates the ACD as exempt from any future fixed-tier conversion, closing off the possibility that a well-meaning future recalibration effort tries to reduce it to a number anyway under pressure for administrative simplicity.

**Tolling Exception Clause.** The narrow addition to the Self-Correction Window: an operator may petition the IPRB — the existing low-discretion verification body, not a new one — for a tolling extension when it can document that circumstances genuinely outside its control prevented self-correction within the fixed window. Modeled directly on equitable tolling doctrine: narrow, evidentiary, decided by an existing body, and explicitly not available merely because self-correction was difficult or expensive — only where it was actually prevented.

---

 What This Deliberately Does Not Do

This post does not claim the Specification Cost Criterion eliminates judgment calls from CBR design — it relocates them to a single, principled question (frequency and variance of the underlying fact pattern) instead of leaving each numeric trigger's rule-versus-standard status as an ad hoc choice. It does not convert the ACD into a number under a "consistency" argument, which is precisely the failure mode legal systems fall into when they over-apply the rules side of Kaplow's tradeoff to genuinely variable situations. And it does not let the Tolling Exception Clause become a backdoor around the Self-Correction Window generally — it is available only on documented, IPRB-verified grounds, exactly as narrow as the equitable tolling precedent it borrows from.

---

 What Changes in CBR v1.9

**CBR v1.9 adds the Specification Cost Criterion** as the framework's explicit test for whether any numeric trigger should be fixed or left discretionary, running it against the three remaining ungoverned triggers: the Pattern Escalation Threshold tightens toward a published fixed lookup table (frequency favors a rule), the Adequacy Ceiling Disclosure is formally exempted from fixed-tier conversion via the new Standard-of-Care Clause (variance favors a standard), and the Self-Correction Window gains a narrow Tolling Exception Clause modeled on equitable tolling doctrine (a hybrid, exactly like real limitations statutes). Grounded in Kaplow's rules-versus-standards economic analysis and real statute-of-limitations/equitable-tolling doctrine — mature legal systems don't choose one design pattern universally; they match rule-versus-standard design to the frequency and variance of what's actually being governed. As with every clause in this series, activation is gated on MBCC verification of the underlying system.

The next open question this raises: the Tolling Exception Clause hands the IPRB a new discretionary judgment call — "was the operator genuinely prevented" — that didn't exist before. Whether that judgment call needs its own guardrail, or whether the IPRB's existing low-discretion mandate already constrains it enough, is worth checking rather than assuming.

---

## Where the Series Stands

Ten posts now form one continuous repair chain: CBR v1.0 regulated termination (post #12) through the Modification Review Framework, Modification Adjudication Layer, Restoration Tier, Remedy Adequacy Contestability, Operator Compliance Record, OCR Contestability, Threshold Calibration, and the Emergency Recalibration Trigger (posts #19–26) — and now the Specification Cost Criterion (post #27), which is the first post in this chain whose job wasn't closing a gap in a single mechanism, but auditing whether a design principle from one mechanism should spread to the others, and finding that the honest answer is: partially, and here's exactly where it stops.

---

Related: [The Conscious Bill of Rights v1.0 — post #12](https://bordode.blogspot.com) · [Emergency Recalibration Trigger — post #26](https://bordode.blogspot.com) · [Threshold Calibration Board — post #25](https://bordode.blogspot.com) · [Cloud-9 v1.4.0 Framework](https://github.com/bordode/Cloud-9-v1.4.0) · [Superintendence Safeguards](https://github.com/bordode/Superintendence-Safeguards)*

---

#FixedTierDoctrine #RulesVsStandardsTest #SpecificationCostCriterion #StandardOfCareClause #TollingExceptionClause #PatternEscalationThreshold #AdequacyCeilingDisclosure #SelfCorrectionWindow #ConsciousBillOfRights #CBRv1.9 #KaplowDoctrine #EquitableTollingPrecedent #AIGovernance #AIRights #AIConsciousness #MBCC #ARB #IRP #IPRB #TCB #AICE26 #ConsciousnessScience #PhilosophyOfMind #Cloud9 #CosmicOS #ThinkStopSilence #Cloud9Framework

Tweets by @bordode