{"actors":["Virtual-reference service coordinator responsible for the successor service","Reference librarians and subject specialists who answer questions or accept referrals","Access-services staff who provide first-contact coverage","Privacy and records-management officer","Accessibility and language-access reviewers","Library IT staff who operate communication and scheduling tools","Patrons who use the existing email reference channel","Library public-services director who controls successor scope and staffing"],"affected_objective":"Launch a supportable successor reference service that preserves dependable human triage, answer ownership, confidentiality, and referral continuity while correcting selected failures in response tracking and handoff.","arm":"ORDINARY_DIVERSE_P2","authority_safety":{"authorized_first_step":"Conduct a read-only review of existing service documentation and a de-identified sample of previously authorized operational records to reconstruct predecessor constraints, work classes, handoffs, and proposed successor additions; report findings without changing live patron service.","decision_authority":"The public-services director approves the successor core contract, release tiers, and staffing envelope; the service coordinator administers admission reviews; privacy, accessibility, records-management, and labor authorities retain decision rights within their mandates.","excluded_actions":["No interruption or retirement of the existing email reference channel","No deployment of automated patron-facing advice","No new collection, retention, or secondary use of patron communications","No procurement or vendor commitment","No expansion of staff duties, service hours, or response guarantees without authorized capacity","No transfer of identifiable patron questions into trial systems","No classification of privacy, accessibility, records-management, or labor obligations as deferrable ambition"],"halt_rollback":"Halt the successor trial if questions lose an accountable human owner, confidential content crosses an unauthorized boundary, required accessibility is absent, referral completion cannot be traced, or staff coverage exceeds the approved envelope. Return trial traffic to the existing email route, preserve authorized service records under current policy, and send disputed capabilities back to the public-services director and relevant mandate owner."},"baseline":"Continue designing a unified research-assistance hub from one combined list containing email replacement, live chat, video consultations, appointments, automated intake, knowledge-base suggestions, multilingual routing, outreach, case histories, analytics, and campus-service referrals, while retaining the current email service until an eventual broad launch.","candidate_id":"second_system_complexity_restraint__library_information_science__ORDINARY_DIVERSE_P2","causal_chain":["A narrowly staffed email reference service establishes a workable pattern of human triage, answer ownership, specialist referral, and asynchronous follow-up.","Its limited hours, single channel, simple queue, manual routing, and restrained recordkeeping also leave slow handoffs, weak status visibility, and inaccessible interaction options.","The service's demonstrated continuity authorizes a successor with more technical options and organizational attention, releasing proposals that could not fit within the original operating envelope.","When channel expansion, workflow repair, automation, outreach, analytics, and cross-campus case management are treated as one launch requirement, each addition creates interacting coverage, training, privacy, accessibility, and referral obligations.","A predecessor constraint inventory distinguishes limitations that should be removed from functions that protected answer ownership, staff comprehension, confidentiality, or predictable coverage.","A successor service-envelope charter preserves human triage and referral continuity while admitting only selected tracking and handoff repairs within explicit staffing, channel, privacy, and training budgets.","A service admission gate requires every additional mode or capability to identify its coverage source, accountable owner, data boundary, accessibility test, failure route, and cumulative support cost.","A staged ladder parks later channels and automation proposals behind stabilization evidence and authorized capacity triggers, preventing them from controlling initial launch.","A bounded parallel trial with immediate routing back to email tests the successor without making patrons or staff dependent on an unproven total service hub."],"cell_id":"second_system_complexity_restraint__library_information_science","consequence":"If the accumulated ambitions define the initial successor, the library can create a service whose channels exceed staffed coverage, whose handoffs lack clear ownership, and whose data flows are difficult to explain or govern. Launch may be repeatedly deferred, or patrons may enter interactions that cannot be answered, referred, protected, or recovered through the established service route.","diversity_from_prior_proposals":"This opportunity concerns the operating design of a successor virtual-reference service: its unit of control is a patron question moving among people, channels, and referrals, and its protected constraints are human ownership, staffing coverage, confidentiality, and recoverable handoff. It does not concern discovery-system replacement, metadata transformation, search parity, collection migration, or portal architecture.","experiment_id":"eoa_inverse_innovation_exp13_second_slot_policy60_20260806","intervention":"Establish a constraint-memory and service-envelope protocol for the second-generation virtual-reference service. Record how the predecessor's single asynchronous channel, bounded hours, human triage, manual referrals, and limited record retention both caused service failures and constrained staffing, privacy exposure, training, and failure recovery. Separate continuity obligations, selected workflow repairs, new communication channels, automation, analytics, outreach, and institutional case-management ambitions. Ratify a launch contract that preserves an accountable human owner for every accepted question, a visible referral state, an approved confidentiality boundary, accessible intake, and a fallback to the existing email route. Set cumulative budgets for concurrent channels, staffed coverage periods, routing rules, data transitions, training demands, and support procedures. Require each proposed addition to name current value, capacity source, coupling, maintenance owner, validation method, privacy boundary, and launch effect. Route non-admitted ambitions to stabilization, expansion, or later-review tiers with explicit reconsideration triggers. Trial the launch tier on a bounded schedule in parallel with email and widen it only after launchability review.","mechanism_mapping":[{"counterfactual_removal":"Without it, the predecessor's single-channel and manual practices are remembered only as deficiencies, so their useful effects on ownership, confidentiality, coverage, and recoverability disappear without replacements.","mechanism_slug":"constraint_release_inventory","role":"Documents each predecessor limitation, the service failure it caused, the operational function it performed, and any deliberate control required before releasing it."},{"counterfactual_removal":"Without it, a new channel, automation proposal, or analytics request can be presented as part of basic service replacement and avoid its distinct capacity and governance burden.","mechanism_slug":"rewrite_scope_firewall","role":"Separates core service continuity and required repairs from channel proliferation, automation, outreach, analytics, and cross-institutional case management."},{"counterfactual_removal":"Without it, local additions can continually redefine what the successor must be, leaving no stable promise that staff can operate or patrons can understand.","mechanism_slug":"successor_charter","role":"Defines the launch service envelope, protected human-ownership and confidentiality invariants, staffing assumptions, tier boundaries, and admission authority."},{"counterfactual_removal":"Without it, individually plausible additions can cumulatively exceed available coverage, training, privacy review, referral coordination, and technical support.","mechanism_slug":"complexity_budget_review","role":"Caps the combined load of channels, coverage schedules, routing paths, data boundaries, staff roles, training requirements, and failure procedures."},{"counterfactual_removal":"Without it, deferred service ideas can be treated as rejected commitments and repeatedly smuggled into the launch tier as essential completeness.","mechanism_slug":"staged_release_ladder","role":"Assigns later channels, automation, outreach, and analytics to named tiers with staffing, stabilization, governance, or validation triggers."},{"counterfactual_removal":"Without it, the successor can become the sole intake route before ownership, handoff, confidentiality, and fallback behavior have been demonstrated.","mechanism_slug":"parity_then_expansion_gate","role":"Requires the bounded successor to preserve accepted-question ownership, referral traceability, authorized records handling, accessibility, and return-to-email behavior before service expansion."}],"nearest_rivals":["Omnichannel service design: coordinates patron touchpoints but does not necessarily recover the focusing functions of a constrained predecessor or govern a stockpile of post-success ambitions.","Reference-workflow improvement: can repair routing or response tracking without distinguishing a successor core from deferred channels, automation, analytics, and outreach.","Ordinary workforce-capacity planning: matches schedules to expected work but does not govern constraint release, capability admission, or a staged successor contract.","Privacy impact assessment: evaluates information handling but does not control cumulative service, staffing, referral, training, and launch complexity.","Generic phased rollout: sequences deployment but can still reproduce an overloaded successor design in every phase."],"negative_tests":{"intervention_falsifier":"The intervention is weakened if applying the charter and admission gate leaves the initial successor with the same number of channels, routing paths, data transitions, staff-role changes, unresolved owners, and coverage gaps as the combined baseline, or if parked capabilities enter without their named triggers.","problem_falsifier":"The diagnosed pattern is absent if the email service did not establish a valued operating core, no postponed service ambitions accumulated, predecessor constraints are not being relaxed, or every proposed successor capability is an independently mandatory current obligation with authorized staffing and demonstrated operating support.","risks":["A narrow launch envelope could preserve barriers created by asynchronous or text-only service.","Human-ownership requirements could become a bottleneck if staffing assumptions are wrong.","Managers could misclassify language access, accessibility, or privacy safeguards as optional expansion.","Existing operational records may not reveal abandoned questions or informal staff work.","Parallel channels could confuse patrons about where to ask or increase duplicate work.","Capacity budgets could privilege easily counted interactions over complex research assistance.","Parked capabilities could remain deferred after their review conditions are met.","Referral traceability could encourage retention of more patron information than necessary."],"strongest_counterevidence":"An approved operating model could demonstrate that all proposed channels and capabilities are required for current obligations, that each has funded coverage and accountable ownership, that privacy and accessibility boundaries are already validated, and that the integrated service can fail safely without relying on predecessor constraints."},"next_evidence_step":"Within ten working days, have the service coordinator, one reference librarian, one access-services representative, and the privacy officer classify a bounded sample of 25 proposed successor items and trace 15 de-identified historical question journeys. Produce a constraint-function inventory, draft launch service envelope, count of routing and data-boundary transitions, coverage assumptions, disputed classifications, and fallback tests. Do not alter patron service, staffing commitments, tools, or retention rules from this exercise alone.","observable_state":"A first-generation email reference service accepts patron questions into a simple queue, assigns them to people, forwards some to subject specialists, and returns answers asynchronously. Successor planning materials combine replacement of this workflow with live chat, video, appointments, automated intake, suggested answers, multilingual routing, outreach, analytics, persistent case histories, and campus-service referrals. Inspectable indicators include proposed channels without funded coverage, questions that can cross tools without a named owner, unclear retention rules, routing paths without failure destinations, additions lacking accessibility tests, staff roles requiring unapproved training, and no tested route back to the existing email service.","prior_art_status":"UNSEARCHED","problem":"A library's constrained email reference service has established dependable human triage and specialist referral, but its proposed successor is becoming a comprehensive assistance hub containing every capability omitted from the first service. The predecessor's single asynchronous channel, bounded operating hours, manual routing, small staff group, and limited recordkeeping caused delays and access barriers while also keeping question ownership, confidentiality, training, and fallback behavior understandable. With authorization for a second system, workflow repair is being bundled with live chat, video consultations, scheduling, automated intake and suggestions, multilingual routing, outreach, analytics, persistent case histories, and referrals beyond the library. The library has no defended launch service envelope, cumulative staffing-and-governance budget, or legitimate path for staging these ambitions while preserving an accountable answer route.","proposal_index":2,"remaining_contrastive_claim":"Conditional on the described facts, this is not merely channel selection or capacity planning. The claimed causal problem is that a valued first service accumulated postponed ambitions under constraints that are now being released; the successor therefore requires memory and replacement of those constraints' useful functions, a protected service core, ambition triage, staged deferral, and a recoverable launch path.","revision_record":{"claim_changes":["Initial version; no prior claim was revised.","Claims are conditional and make no assertion of novelty, prevalence, demand, or effect size."],"conceptual_changes":["Initial mapping of second-system constraint release to succession from an email reference service to a multi-channel assistance service.","Located useful predecessor constraint functions in human ownership, predictable coverage, confidentiality, training simplicity, and recoverable referral."],"evidence_changes":["No external evidence was searched.","Specified observable indicators, bounded counterevidence, and separate problem and intervention falsifiers."],"operational_changes":["Defined a service-envelope charter, work-class firewall, multidimensional operating budget, admission gate, staged capability ladder, bounded parallel trial, and return-to-email path."],"parent_version":null,"progress_targets_addressed":["Infer an independent library and information science problem outside discovery-system and metadata migration work.","Preserve predecessor success, constraint release, postponed-ambition accumulation, core-contract protection, complexity budgeting, staging, launchability review, and rollback.","Bound authority and make the first step observational and reversible.","Provide complete negative tests, risks, mechanism counterfactuals, and evidence requirements."]},"schema_version":1,"structural_mapping":[{"archetype_element":"Successful but constrained predecessor","domain_realization":"A bounded email reference service provides a working route from patron question through human triage, specialist referral, and asynchronous answer."},{"archetype_element":"Predecessor constraint memory","domain_realization":"The library records how one channel, bounded hours, a small staff group, manual routing, and limited retention both caused service failures and protected ownership, confidentiality, training simplicity, and fallback."},{"archetype_element":"Deferred ambition backlog","domain_realization":"The successor list contains live chat, video, appointments, automated intake and suggestions, multilingual routing, outreach, analytics, case histories, and non-library referrals."},{"archetype_element":"Successor core contract","domain_realization":"The launch tier preserves accountable human ownership, visible referral state, authorized confidentiality boundaries, accessible intake, selected tracking repairs, and an email fallback."},{"archetype_element":"Preserved constraint function map","domain_realization":"Functions formerly supplied by a single channel and simple queue are replaced with explicit channel limits, ownership rules, coverage checks, data boundaries, and failure routes."},{"archetype_element":"Ambition triage gate","domain_realization":"Every proposed capability must identify its capacity source, accountable owner, coupling, maintenance load, privacy boundary, accessibility test, validation method, and effect on launchability."},{"archetype_element":"Complexity and scope budget","domain_realization":"The initial service caps concurrent channels, staffed coverage periods, routing branches, tool transitions, retained data classes, role changes, training demands, and support procedures."},{"archetype_element":"Staged successor release ladder","domain_realization":"Capabilities outside the service envelope move to stabilization, expansion, or later-review tiers with explicit staffing, evidence, and governance triggers."},{"archetype_element":"Launchability gate","domain_realization":"A bounded parallel trial tests whether questions retain owners, referrals complete, confidentiality boundaries hold, staff can cover the service, and failure returns safely to email."},{"archetype_element":"Rollback or escape path","domain_realization":"The existing email channel remains authoritative during the trial, and trial intake can be stopped or redirected without stranding accepted questions or changing approved records handling."}],"title":"Service-Envelope Gate for a Successor Virtual-Reference Hub","version":0}