{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp09_archetype_breadth150_20260804","cell_id":"load_balancing__accounting_auditing","arm":"BREADTH_PROBE_ONE_SHOT","candidate_id":"load_balancing__accounting_auditing__P1","proposal_index":1,"version":0,"title":"Capacity-Aware Routing of Technical-Accounting Consultation Reviews","problem":"During a financial-reporting close or audit, engagement teams submit technical-accounting consultation packets on issues such as revenue recognition, leases, and consolidations. Packets are commonly directed to a customary specialist or fixed engagement reviewer. One qualified reviewer can consequently accumulate an aging queue while other qualified, independent reviewers have unused capacity. The structural problem is uneven assignment rather than necessarily insufficient aggregate specialist capacity.","actors":["Engagement teams submitting consultation packets","Technical-accounting reviewers","Technical-accounting queue coordinator","Engagement partner or controller accountable for the reporting conclusion","Independence, confidentiality, and quality-control personnel"],"observable_state":"For each pending packet, the coordinator can observe submission time, reporting deadline, topic, estimated effort, risk class, entity restrictions, required credentials, assigned reviewer, review status, and continuity needs. For each reviewer, the coordinator can observe current work-in-progress, forecast availability, topic eligibility, independence or conflict restrictions, recent turnaround, and temporary unavailability. The problem state is present when queue age or assigned effort is concentrated on one eligible reviewer while another equivalently eligible reviewer has usable capacity.","consequence":"Localized queues delay consultation completion, compress the time available to resolve accounting issues before filing or close deadlines, and may encourage rushed review, while qualified capacity elsewhere remains unused.","affected_objective":"Timely completion of technically competent and independent accounting consultations without weakening documentation, accountability, confidentiality, or required approval gates.","intervention":"Create a pooled intake point that performs eligibility and health checks before assigning each newly admitted consultation packet. Apply capacity-aware weighted routing using topic qualification, independence and confidentiality constraints, current work-in-progress, estimated effort, deadline, and continuity requirements. Downweight saturated or unavailable reviewers, preserve high-risk priority, and make any assignment failure explicit. Once substantive review begins, keep the packet with that reviewer unless an authorized, documented handoff preserves context and ownership.","structural_mapping":[{"archetype_element":"Incoming work","domain_realization":"Technical-accounting consultation packets awaiting specialist review"},{"archetype_element":"Multiple viable receivers","domain_realization":"Reviewers who are qualified for the topic and satisfy independence, confidentiality, and entity-access constraints"},{"archetype_element":"Capacity signal","domain_realization":"Reviewer work-in-progress, estimated remaining effort, forecast availability, and queue age"},{"archetype_element":"Health check","domain_realization":"Checks for absence, overload, expired qualification, conflicts, access limitations, or other temporary ineligibility"},{"archetype_element":"Distribution policy","domain_realization":"Eligibility-constrained, deadline- and risk-aware weighted assignment rather than customary-reviewer or equal-split assignment"},{"archetype_element":"State affinity","domain_realization":"Reviewer continuity after substantive analysis begins, with documented context transfer required for reassignment"},{"archetype_element":"Feedback and monitoring","domain_realization":"Periodic comparison of assigned effort, queue age, reassignment frequency, eligibility exceptions, and review outcomes by reviewer"},{"archetype_element":"Target invariant","domain_realization":"No eligible reviewer remains overloaded while equivalent qualified capacity is idle, without violating independence, competence, priority, or approval requirements"}],"mechanism_mapping":[{"mechanism_slug":"capacity_aware_routing","role":"Ranks eligible reviewers using current and forecast workload rather than assigning solely by habit or nominal availability.","counterfactual_removal":"Without the capacity signal, routing becomes static or blind and can reproduce the original hot spot."},{"mechanism_slug":"health_checked_distribution","role":"Removes or downweights reviewers who are unavailable, conflicted, unqualified, inaccessible, or already beyond a defined work-in-progress threshold.","counterfactual_removal":"Without health and eligibility checks, the system can route sensitive or specialized work to an incapable or prohibited reviewer."},{"mechanism_slug":"weighted_routing","role":"Allocates unequal shares when reviewers differ in capacity, topic competence, packet effort, or deadline fit.","counterfactual_removal":"An equal split can overload lower-capacity reviewers and ignore material differences among packets and reviewers."}],"causal_chain":["Static or customary-reviewer assignment concentrates consultation packets despite available qualified capacity elsewhere.","Eligibility, workload, and availability signals make the viable reviewer pool and its usable capacity visible.","The routing policy filters prohibited destinations and ranks the remaining reviewers by capacity, suitability, risk, and deadline.","New packets are assigned away from saturated reviewers toward eligible reviewers with usable capacity.","Continuity rules prevent balancing from fragmenting work already under substantive review.","Monitoring updates reviewer weights or removes unhealthy receivers while exposing failed assignments instead of silently dropping packets.","If aggregate qualified capacity is sufficient, reduced assignment skew should reduce avoidable queue concentration without relaxing review safeguards."],"baseline":"Engagement teams email a customary specialist or use a fixed engagement-to-reviewer roster. Queue imbalance is discovered through aging reports or deadline escalation, and work is reassigned manually only after delay becomes visible.","nearest_rivals":["Equal round-robin assignment, which spreads packet counts but ignores effort, competence, conflicts, and differing reviewer capacity","Deadline triage or priority admission, which changes processing order or defers low-priority work but does not use idle qualified capacity through reassignment","Emergency failover to another reviewer after the customary reviewer becomes unavailable, which does not distribute ordinary live work before failure","Hiring contractors or adding permanent specialist capacity, which addresses aggregate undercapacity rather than testing whether existing capacity is unevenly used","Managerial scheduling of individual reviewers, which sequences their work but need not change which viable reviewer receives each incoming packet"],"remaining_contrastive_claim":"The proposal changes the destination of ordinary admitted consultation work before reviewer failure by pooling only eligible reviewers and using workload, health, suitability, deadline, and affinity signals. Its distinguishing causal move is assignment across viable capacity, not equal splitting, queue reprioritization, demand suppression, emergency substitution, or capacity expansion.","authority_safety":{"decision_authority":"The technical-accounting function leader or audit-firm quality leader may define routing constraints; engagement partners or controllers retain authority over accounting conclusions, required consultations, and final approvals. Independence and access-control owners determine reviewer eligibility.","authorized_first_step":"Conduct only a retrospective shadow replay on de-identified historical queue metadata; generate hypothetical assignments without changing any live work, reviewer responsibility, accounting conclusion, or approval.","excluded_actions":["Automatically approving or signing consultation conclusions","Overriding independence, competence, confidentiality, entity-access, or segregation-of-duties restrictions","Reassigning work after substantive review begins without documented authorization and context transfer","Suppressing, delaying, or dropping required consultations to improve queue metrics","Changing audit scope, materiality, filing decisions, or accounting policy","Using individual performance sanctions based on the shadow analysis"],"halt_rollback":"Stop the replay if required eligibility fields are missing, de-identification fails, restricted information is exposed, or hypothetical routing produces any prohibited assignment. Delete the derived assignment output and retain the existing assignment process unchanged."},"negative_tests":{"strongest_counterevidence":"After enforcing topic, independence, confidentiality, access, deadline, and continuity constraints, reviewers who appear idle may not be viable substitutes; the apparent imbalance could therefore reflect necessary specialization rather than poor routing.","problem_falsifier":"The problem is falsified for the sampled queue if no materially interchangeable reviewer capacity coexists with an overloaded reviewer, or if total demand exceeds eligible capacity across the same periods so redistribution cannot remove the bottleneck.","intervention_falsifier":"The intervention is falsified for the bounded replay if capacity-aware assignments do not improve predeclared workload-skew and queue-age measures relative to reconstructed baseline assignments, or if they increase prohibited assignments, deadline misses, handoffs, or concentration at a shared downstream approver.","risks":["Stale or inaccurate workload estimates create new hot spots","Reviewers or submitters game effort estimates or availability signals","Routing migrates overload to engagement partners or another shared approval bottleneck","Frequent reweighting causes assignment instability or excessive context switching","Pooling weakens engagement knowledge, continuity, or personal accountability","Efficiency weighting creates unfair or developmentally narrow reviewer workloads","Incorrect eligibility data breaches independence, confidentiality, access, or competence requirements","A central intake coordinator becomes a bottleneck or single point of failure","Queue metrics incentivize superficial review or avoidance of difficult packets"]},"next_evidence_step":"Using no more than eight weeks of de-identified historical consultation metadata from one technical-accounting pool, reconstruct the original assignment sequence and replay the same arrivals through a predeclared eligibility-constrained weighted-routing rule. Compare reviewer estimated-effort skew, oldest eligible packet age, deadline breaches, reassignment count, prohibited-assignment count, and downstream-approver concentration. Review a small random sample of hypothetical substitutions with independence and technical-quality personnel. Do not route live packets; stop if required constraint data cannot be validated.","prior_art_status":"UNSEARCHED","diversity_from_prior_proposals":"Not assessed because runtime isolation prohibits inspecting other proposals; this record is an independent one-shot mapping from the supplied archetype and domain card.","revision_record":{"parent_version":null,"progress_targets_addressed":[],"conceptual_changes":["Initial one-shot candidate."],"operational_changes":["Initial bounded retrospective replay design."],"evidence_changes":["No external evidence or prior-art search used."],"claim_changes":["Claims are limited to a testable causal hypothesis and exclude novelty, prevalence, demand, and effect size."]}}