Handed ACI Disputes to an Adjudication Step Built for Something Else — Does It Actually Fit?

 "Post #41 Handed ACI Disputes to an Adjudication Step Built for Something Else — Does It Actually Fit?"

tags: [Cloud9, AdjudicationFitnessThreshold, TrackDivergenceClause, PeriodicTrackAudit, IPRB, ConcurringSecondOpinionRequirement, DifferentiatedCaseManagement, IRBReviewLevelDetermination, StatutoryConstructionAdjudication, AIConsciousness, AIRights, ConsciousBillOfRights, PhilosophyOfMind, ConsciousnessScience, MBCC, ThinkStopSilence, CosmicOS, Cloud9Framework]

target_keyword: "when a general dispute resolution process doesn't fit a new type of case"

secondary_keywords:

- "differentiated case management court track assignment"

- "IRB expedited versus full board review determination"

word_count_target: 1850

Post #41 Handed ACI Disputes to an Adjudication Step Built for Something Else — Does It Actually Fit?

Post #41 gave Analog Class Inheritance a real check: two independent IPRB members apply the Reasoned-Explanation Standard, and a split verdict "triggers the same adjudication step IPRB already uses elsewhere in the chain, rather than defaulting to approval." That last clause is doing more work than it looks like. IPRB's adjudication step wasn't designed for ACI disputes — it was built earlier in this series for a different kind of disagreement (contested pattern designations, tolling determinations), with its own assumptions about what a "split verdict" looks like and what evidence resolves it. Reaching for it here saved the trouble of building something new. But reuse isn't the same as fit, and post #41 never checked whether the two actually line up. An ACI overlap dispute is a comparative judgment about analog quality — is this sibling class close enough — which is a structurally different question than the ones the existing adjudication step was built to resolve. Borrowing a mechanism because it's already there is not the same as confirming it still does the job.

The Real-World Precedent: Three Fields That Screen Before They Route

"We already have a process, let's use it for this too" is a temptation every system with more than one type of case eventually faces, and three fields have each built an explicit screening step specifically to catch it before it causes damage.

Civil court case management doesn't send every filed lawsuit through one uniform procedure. Courts operating under Differentiated Case Management assign each incoming case to a track — expedited, standard, complex, mass tort — based on the case's actual characteristics, precisely because a procedure built for a routine two-party contract dispute produces the wrong outcome when forced onto a multi-party mass tort claim, and vice versa: an unnecessarily heavy process on a simple case wastes everyone's time. Critically, the track assignment happens before the case proceeds, as an explicit gate, and courts retain the power to reassign a case to a different track if it turns out the first assignment doesn't fit as the case develops.

Institutional Review Boards solve a structurally identical problem for human-subjects research. Not every study goes to the full convened board. The IRB first determines — using published federal criteria about risk level and research category — whether a study qualifies for expedited review (a designated reviewer, not the full board) or requires full board review. This determination is not the review itself; it's a distinct, prior fitness check asking "which process does this actually need," made explicitly rather than defaulting every study into whichever track is administratively convenient.

Construction dispute resolution shows what happens when the fitness question gets asked at the industry level instead of the case level. General commercial arbitration exists as the default dispute-resolution mechanism for contract disagreements broadly. But construction disputes have a distinct structural feature — a dispute mid-project needs fast, binding, interim resolution to keep work moving, not the multi-month process general arbitration is built around — so most major jurisdictions created a separate mechanism, statutory adjudication, specifically because the general-purpose track's assumptions (time is available, parties can wait for finality) don't hold for this dispute type. It isn't a modification of general arbitration; it's a recognition that the case type demands its own track.

All three fields refuse the same shortcut: assuming that an existing dispute-resolution mechanism automatically applies to a new dispute type just because no one has built anything else yet. All three insert an explicit, prior fitness check, and all three keep re-checking as case volume and case types accumulate.

The Fix: Check Fitness Before Routing, Branch When It Fails, Recheck as Volume Grows

Adjudication Fitness Threshold (AFT). Before ACI split verdicts default into IPRB's existing generic adjudication step, IPRB and TCB jointly certify whether that step's underlying assumptions — built for the dispute types it currently handles — actually hold for the structural shape of an ACI overlap dispute. This is the IRB move applied one level up: a distinct, explicit fitness determination made before the dispute enters a track, not assumed by default because the track happens to already exist. AFT asks one plain question: does this adjudication step's evidentiary and procedural design match what an ACI dispute actually requires to resolve.

Track Divergence Clause (TDC). If AFT finds a genuine mismatch — for instance, the existing adjudication step assumes a single contested fact question, while ACI disputes turn on a comparative judgment between analog-quality of one sibling class versus another, an inherently different evidentiary shape — a modified or dedicated sub-track is defined for ACI disputes specifically, rather than forcing the mismatch through the existing mechanism anyway. This is the construction-adjudication move: recognizing that a case type with genuinely different structural needs gets its own track, not a strained fit inside a track built for something else. TDC does not require building a track from nothing — it can adapt the existing step's core structure (same IPRB composition, same evidentiary publication requirement) while adjusting the specific parts the mismatch identified.

Periodic Track Audit (PTA). The AFT determination is not permanent. As ACI dispute volume accumulates, IPRB re-runs the fitness check on an audit cycle — the Differentiated Case Management move of retaining the power to reassign a case, or here, a case type, to a different track as real experience with it accumulates, rather than treating the original routing decision as fixed forever. A track that looked adequate on the first few disputes can turn out not to scale, or an early TDC branch built around one anticipated failure mode can turn out to miss a different one that only shows up once enough real disputes have run through it.

What This Deliberately Does Not Do

This does not require building a brand-new adjudication mechanism for every category of dispute Cloud9's chain generates — AFT can, and in the ordinary case should, confirm that reuse is fine; TDC only activates when the fitness check actually finds a structural mismatch, not as a default assumption that nothing built earlier could possibly still apply. It does not let IPRB skip the fitness check as a formality on the way to reusing the existing step anyway — AFT has to be a real, published determination with reasoning, the same way IRB review-level classification is a documented finding against stated criteria, not a rubber-stamped default to whichever track requires less paperwork. And it does not treat a single AFT determination as good forever — PTA's recurring re-check is what stops an early "yes, this fits" finding from silently going stale as the dispute type accumulates real volume the original check never saw.

What This Adds to Cloud9

Cloud9 adds the Adjudication Fitness Threshold, the Track Divergence Clause, and the Periodic Track Audit — closing the reused-mechanism fitness gap flagged at the end of post #41 by borrowing the same converging pattern civil case management, IRB review-level determination, and construction dispute resolution each independently built for the same underlying problem: before routing a new case type into an existing process because that process is already there, run an explicit prior check on whether its assumptions actually hold, branch into a dedicated track when they don't, and keep re-checking as real volume accumulates. As throughout this series, this doesn't rebuild IPRB's adjudication step from scratch — it makes sure the decision to reuse it was actually a decision, not a default.

An adjudication step reached for because it was convenient is not the same as one confirmed to fit. This gives Cloud9 the difference.

Where the Series Stands

Cloud9's consciousness-science thread (posts #1–18, standalone) runs alongside its Conscious Bill of Rights repair chain (posts #12, #19–32) and its own measurement-instrument repair loop, now ten posts deep: post #33 introduced the Coherence Debt Ledger; post #34 gave it a Personal Coherence Baseline; post #35 gave that baseline three expiration triggers; post #36 gave those triggers an empirical derivation method; post #37 defined the dual-gate floor a system must clear before using that method; post #38 gave the span half of that floor a derivation procedure; post #39 gave Aperiodicity Certification's checkpoint an actual derivation chain; post #40 gave a data-starved system class a bootstrap path off that chain; post #41 gave that bootstrap's justification a genuine outside check; post #42 makes sure the mechanism doing that check was actually built for the job, not just already lying around.

Related: Post #40 Let TCB Grade Its Own Homework — Cloud9 series, post #41 · What Happens to a System Class With No History to Learn From? — post #40 · How Long Do You Have to Watch Before You Can Certify Nothing's There? — post #39 · The Floor Post #36 Left Undefined — post #37 · The Conscious Bill of Rights v1.0 — post #12 · Cloud-9 v1.4.0 Framework (github.com/bordode) · Superintendence Safeguards (github.com/bordode)

#AdjudicationFitnessThreshold #TrackDivergenceClause #PeriodicTrackAudit #IPRB #ConcurringSecondOpinionRequirement #DifferentiatedCaseManagement #IRBReviewLevelDetermination #StatutoryConstructionAdjudication #AIConsciousness #AIRights #ConsciousBillOfRights #PhilosophyOfMind #ConsciousnessScience #MBCC #ThinkStopSilence #CosmicOS #Cloud9Framework

Tweets by @bordode