{"actors":["State benefits appeals tribunal administrator","Administrative law judges","Docketing and scheduling clerks","Language-access coordinator","Appellants and their representatives","Tribunal privacy officer","Legislative or inspector-general oversight staff"],"affected_objective":"Timely and procedurally fair resolution of benefits appeals without sacrificing lawful prioritization, adjudicative independence, or aggregate docket stability.","arm":"COMMON_P1","authority_safety":{"authorized_first_step":"The tribunal administrator may authorize a read-only, de-identified retrospective docket audit using existing administrative records; the audit may assess workflow but may not alter scheduling, eligibility, or case outcomes.","decision_authority":"The tribunal administrator controls administrative workflow and resource allocation, subject to privacy and language-access rules; administrative law judges retain exclusive authority over merits, evidence, continuances, and remedies in individual cases.","excluded_actions":["Changing or recommending the result of any appeal","Using protected characteristics or accommodation needs to disadvantage an appellant","Removing statutory priority or due-process protections","Inferring sensitive attributes not already lawfully collected","Publicly reporting cells small enough to identify appellants","Automating sanctions, dismissal, or adverse scheduling"],"halt_rollback":"Halt if records cannot support reliable pathway comparisons, privacy review identifies unacceptable re-identification risk, or monitoring burdens interfere with hearings. Disable the new reports and alerts, return to the existing docket process, and retain only an access-controlled audit log documenting the decision."},"baseline":"The tribunal monitors aggregate monthly filings, dispositions, pending caseload, and median case age. Managers respond to aggregate backlog changes through docket-wide staffing or scheduling adjustments, while unusually delayed cases are handled through complaints or ad hoc escalation.","candidate_id":"ensemble_and_population_level_equilibrium_versus_individual_level_heterogeneity__law_governance__COMMON_P1","causal_chain":["Monthly dispositions remain approximately aligned with incoming appeals, producing a stable aggregate pending caseload.","The aggregate indicator pools cases across offices, procedural pathways, accommodation requirements, continuance histories, and case-age trajectories.","Pooling removes information about tail duration and persistent clusters of delayed cases.","Administrators interpret the stable macrostate as evidence that the docket process is functioning uniformly and therefore favor docket-wide responses or no response.","Some operationally defined case pathways can consequently experience repeated long waits without changing the headline equilibrium.","A two-level docket review makes the aggregation rule and distributional state visible while preserving the valid aggregate capacity signal.","Predeclared excursion rules route patterned delays to administrative review at the office or pathway level rather than altering adjudicative outcomes.","Joint monitoring of aggregate balance and pathway-level delay tests whether targeted workflow changes address local degradation without concealing system-wide deterioration."],"cell_id":"ensemble_and_population_level_equilibrium_versus_individual_level_heterogeneity__law_governance","consequence":"A true system-level docket equilibrium can be mistaken for timely treatment of every appellant, allowing persistent pathway-specific delay to burden access to benefits, preparation, representation, and confidence in procedural fairness.","diversity_from_prior_proposals":"Not assessed against other proposals because runtime isolation forbids inspecting them; this candidate is independently derived from the supplied archetype and domain card.","experiment_id":"eoa_inverse_innovation_exp13_second_slot_policy60_20260806","intervention":"Adopt a two-level docket governance rule for one tribunal: retain the aggregate inflow-to-disposition balance as the capacity indicator, but pair it with case-age quantiles, unresolved-case trajectories, and predeclared operational cuts such as office, hearing format, representation status, language-accommodation workflow, and continuance source. Document how cases aggregate into the headline indicator and what it omits. When a sufficiently supported pathway repeatedly crosses a predeclared delay or procedural-risk threshold, require an administrative review of translation availability, notice delivery, scheduling, staffing, or handoff design. Any response must target workflow conditions rather than merits, and the tribunal must continue monitoring both aggregate balance and distribution-level outcomes.","mechanism_mapping":[{"counterfactual_removal":"Without the dashboard, a stable aggregate pending caseload could again conceal tail duration and pathway-specific excursions.","mechanism_slug":"distributional_dashboard","role":"Display the macro capacity indicator beside case-age quantiles, tail counts, uncertainty, and predeclared pathway cuts."},{"counterfactual_removal":"Without the crosswalk, reviewers could not determine how heterogeneous case trajectories produce the stable headline measure or what information is discarded.","mechanism_slug":"micro_macro_crosswalk","role":"Specify that filings add to pending inventory, dispositions subtract from it, and monthly pooling suppresses pathway and trajectory information."},{"counterfactual_removal":"Without excursion alerts, distributional reporting could remain descriptive and fail to initiate review when a supported local pattern persists.","mechanism_slug":"subgroup_excursion_alert","role":"Trigger bounded administrative review when an adequately supported operational pathway repeatedly exceeds a predeclared delay or procedural-risk threshold while the aggregate remains stable."},{"counterfactual_removal":"Without sampled file review, apparent pathway differences could be acted on despite coding errors, lawful pauses, or materially different procedural circumstances.","mechanism_slug":"representative_microcase_panel","role":"Review a privacy-protected sample spanning the delay distribution to distinguish workflow friction from lawful prioritization, party-requested delay, and data error."}],"nearest_rivals":["A tribunal-wide backlog-reduction initiative, which acts on aggregate imbalance even though the proposed problem can coexist with aggregate balance.","An aggregation-bias correction project, which would replace a mathematically or compositionally invalid headline metric; here the aggregate inventory balance may be valid but incomplete for individual treatment.","A generic disparity dashboard, which maps variation but does not define the macro equilibrium, aggregation translation, level boundary, or intervention rule.","Individual case escalation through complaints or judicial review, which can address particular cases but does not detect patterned heterogeneity beneath a stable docket."],"negative_tests":{"intervention_falsifier":"The intervention is undermined if, after a bounded pilot with adequate records, flagged reviews mostly reflect transient noise or lawful case differences, produce no actionable workflow distinction, or worsen aggregate docket stability without improving the flagged procedural condition.","problem_falsifier":"The proposed problem is falsified if case-age distributions show no persistent tail or operational-pathway clustering after accounting for statutory priority, party-requested continuances, case complexity, and data uncertainty, or if the aggregate indicator is not actually stable over the declared window.","risks":["Small pathway cells may generate false alarms or expose appellant identities.","Repeated slicing may create spurious disparities.","Recorded accommodation or representation fields may be incomplete or inconsistently coded.","Managers may stigmatize a pathway or office instead of correcting workflow conditions.","Targeted attention may shift delay to unmonitored cases while preserving the aggregate mean.","Administrative monitoring may intrude on adjudicative independence.","Faster processing may be wrongly treated as preferable when additional time protects due process."],"strongest_counterevidence":"Observed tail delay may be primarily explained by lawful statutory priorities, appellant-requested continuances, evidentiary complexity, or necessary accommodation work; if so, heterogeneous duration is not evidence of defective administration and may protect procedural rights."},"next_evidence_step":"Conduct a single-site, read-only retrospective audit covering the tribunal's preceding twelve complete months. Pre-register the aggregate stability test, operational pathway definitions, minimum cell rules, delay and procedural-risk indicators, and exclusions for lawful pauses. Produce only de-identified aggregate tables and inspect a bounded stratified sample of 60 files across the case-age distribution. The deliverable is a go/no-go memorandum on whether one prospective, nonbinding alert can be tested for 90 days; no scheduling or adjudicative change occurs in this first step.","observable_state":"Over a declared twelve-month window, monthly incoming and disposed appeals remain close enough that total pending inventory and median case age appear stable, while the underlying record can be examined for persistent differences in case-age quantiles, unresolved trajectories, remand frequency, notice failures, or continuance patterns across operational pathways and offices.","prior_art_status":"UNSEARCHED","problem":"A state benefits appeals tribunal treats a stable aggregate pending caseload as evidence of timely administration, although that valid macro equilibrium may coexist with persistent long-tail delay concentrated in particular offices or procedural pathways, including cases requiring language-access coordination. Because the headline measure pools unlike trajectories, administrators cannot tell whether heterogeneity is ordinary lawful variation or a patterned procedural burden requiring workflow-level action.","proposal_index":1,"remaining_contrastive_claim":"Even if the tribunal's aggregate inflow-to-disposition balance is valid and stable, it is insufficient to govern procedural timeliness when persistent, adequately supported pathway-level delay can be identified; the appropriate response is conditional administrative review at the level where delay clusters, not rejection of the aggregate metric or automatic intervention in individual merits.","revision_record":{"claim_changes":[],"conceptual_changes":[],"evidence_changes":[],"operational_changes":[],"parent_version":null,"progress_targets_addressed":["Initial complete candidate preserving the archetype's macro-equilibrium and micro-heterogeneity distinction","Explicit aggregation rule and level-of-analysis boundary","Bounded authority, privacy safeguards, falsifiers, and first evidence step"]},"schema_version":1,"structural_mapping":[{"archetype_element":"Ensemble Frame","domain_realization":"All appeals entering or remaining pending in one state benefits tribunal during twelve complete months, with cases as members and monthly case states as trajectories."},{"archetype_element":"Macro Equilibrium Indicator","domain_realization":"Monthly incoming appeals relative to dispositions, interpreted with total pending inventory and median case age over the declared window."},{"archetype_element":"Microstate Variability Profile","domain_realization":"Case-age quantiles, unresolved trajectories, remands, notice failures, and continuance patterns by predeclared operational pathway and office."},{"archetype_element":"Aggregation Translation Rule","domain_realization":"Each filing adds one case to pending inventory and each final disposition removes one; monthly totals and the pooled median compress pathway, tail, and trajectory information."},{"archetype_element":"Level-of-Analysis Boundary","domain_realization":"Stable inventory supports a tribunal-level capacity claim but does not establish that any appellant or pathway receives timely process; an individual delay likewise does not disprove tribunal-level balance."},{"archetype_element":"Heterogeneity Relevance Test","domain_realization":"Variation becomes reviewable only when it is persistent, adequately supported, not explained by lawful priority or requested delay, and associated with a predeclared procedural-risk condition."},{"archetype_element":"Subgroup and Locality Map","domain_realization":"Heterogeneity is mapped by office and operational pathway, including hearing format, representation status, accommodation workflow, and continuance source, subject to minimum-cell and privacy rules."},{"archetype_element":"Multi-Level Feedback Design","domain_realization":"Tribunal-wide capacity remains monitored while pathway excursions trigger administrative workflow review and any response is checked for displacement or macro deterioration."},{"archetype_element":"Representative Case Guardrail","domain_realization":"A stratified, privacy-protected file panel checks whether quantitative excursions reflect actual workflow conditions rather than anecdotes, miscoding, or lawful case differences."}],"title":"Two-Level Docket Equilibrium Review for Benefits Appeals","version":0}