{"actors":["Library systems lead responsible for the successor discovery service","Catalogers and metadata librarians who maintain descriptive records and crosswalks","Digital archivists responsible for hierarchical and collection-level context","Public-services librarians who support searchers","Accessibility and privacy reviewers","Patrons who depend on the current portal","Institutional IT staff operating indexes, integrations, and migration tooling","Library governance sponsor who controls release scope"],"affected_objective":"Deliver a supportable successor discovery portal that preserves reliable search, filtering, record display, and stable access to the existing collections while correcting selected metadata and accessibility failures.","arm":"COMMON_P1","authority_safety":{"authorized_first_step":"Conduct a read-only constraint-and-backlog audit using existing documentation, issue records, and a small sample of current searches; produce findings for the designated library governance sponsor without changing production systems or release commitments.","decision_authority":"The library governance sponsor approves the core contract and release tiers; the systems lead administers the complexity budget; accessibility, privacy, preservation, and continuity owners retain veto authority within their mandates.","excluded_actions":["No production metadata transformation","No deletion or irreversible consolidation of source records","No procurement or vendor commitment","No patron-data collection beyond already authorized operational records","No retirement of the predecessor portal","No reclassification of statutory, accessibility, privacy, preservation, or continuity obligations as optional ambitions"],"halt_rollback":"Halt the trial if the proposed core omits a mandatory obligation, cannot reproduce designated predecessor searches, or lacks a reversible record-level migration path. Preserve the predecessor as the system of access, discard trial mappings where necessary, and return disputed capabilities to governance review."},"baseline":"Continue planning the successor from a single combined backlog in which search parity, metadata repair, linked-data architecture, new collections, personalization, analytics, preservation integration, and interface redesign compete without release-class boundaries, while the predecessor remains operational pending a broad cutover.","candidate_id":"second_system_complexity_restraint__library_information_science__COMMON_P1","causal_chain":["A constrained first portal establishes usable keyword search, facets, record display, and stable links for a bounded set of collections.","Its narrow schema, batch indexing, limited integrations, and manual exception handling also create recorded omissions and workarounds.","Authorization of a successor relaxes the earlier limits and creates an opportunity to combine parity, metadata cleanup, architectural generalization, and deferred capabilities.","Without separate work classes, locally defensible additions accumulate in the launch release and increase mapping, testing, training, support, and migration dependencies.","A constraint-release inventory identifies which predecessor limits merely caused failures and which also protected comprehensibility, operability, or delivery.","A successor core contract and admission rubric restrict the launch tier to preserved core functions, mandatory obligations, and selected evidenced repairs within a stated complexity budget.","A staged release ladder gives excluded capabilities explicit owners and reconsideration triggers, reducing pressure to disguise them as parity requirements.","Parallel validation against designated predecessor searches and a reversible collection-by-collection migration seam protect launchability and continuity.","Evidence from stabilization reviews then governs whether parked capabilities enter later tiers."],"cell_id":"second_system_complexity_restraint__library_information_science","consequence":"If the combined backlog remains undifferentiated, the successor may become difficult to validate, migrate, teach, and support; launch can recede while patrons remain dependent on an aging predecessor, or a broad cutover can lose familiar retrieval behavior and descriptive context.","diversity_from_prior_proposals":"Not assessed against prior proposals because runtime isolation forbids inspecting them; this candidate is specifically instantiated as governance of a library discovery-portal successor and its metadata migration.","experiment_id":"eoa_inverse_innovation_exp13_second_slot_policy60_20260806","intervention":"Create a governed discovery-successor release protocol. First, document the predecessor portal’s constraints, failures, and useful focusing functions. Classify every successor item as core parity, mandatory safety or continuity, defect repair, technical-debt retirement, validated improvement, speculative option, or parked ambition. Ratify a launch-tier core contract covering designated search journeys, facets, record context, stable identifiers, accessibility, and reversible collection migration. Give the launch tier a complexity budget spanning metadata profiles, crosswalks, index pipelines, integrations, interface modes, staff training, and support procedures. Require each non-core addition to state evidence, coupling, maintenance owner, validation method, and launch impact. Place non-admitted items on stabilization or expansion tiers with review triggers. Run collection-by-collection parallel validation and retain the predecessor route until acceptance criteria are met.","mechanism_mapping":[{"counterfactual_removal":"Without it, earlier limits are treated only as defects, so useful focusing and support functions disappear without replacements.","mechanism_slug":"constraint_release_inventory","role":"Records the narrow schema, bounded collection set, batch indexing, manual exception handling, and other predecessor constraints, separating their harmful effects from their useful functions."},{"counterfactual_removal":"Without it, parity, repair, cleanup, architecture, and new capabilities can enter through the same backlog channel and evade distinct burdens of proof.","mechanism_slug":"rewrite_scope_firewall","role":"Separates continuity obligations and core retrieval parity from metadata repair, technical debt, architectural generalization, and new discovery capabilities."},{"counterfactual_removal":"Without it, the launch boundary remains negotiable item by item and cumulative expansion can displace the predecessor’s validated functions.","mechanism_slug":"successor_charter","role":"Fixes the launch-tier core contract, protected retrieval and continuity invariants, release-tier boundaries, and decision authority."},{"counterfactual_removal":"Without it, each addition can appear affordable in isolation even when aggregate crosswalk, testing, training, integration, and support burdens make the release unlaunchable.","mechanism_slug":"complexity_budget_review","role":"Evaluates cumulative descriptive, architectural, operational, user, validation, and support load before admitting additions."},{"counterfactual_removal":"Without it, deferral can appear equivalent to rejection, encouraging stakeholders to relabel later capabilities as immediate parity needs.","mechanism_slug":"staged_release_ladder","role":"Assigns deferred capabilities to stabilization, expansion, or later-review tiers with named evidence and capacity triggers."},{"counterfactual_removal":"Without it, the successor can displace the working portal before it reproduces core retrieval behavior, leaving users without a tested escape path.","mechanism_slug":"parity_then_expansion_gate","role":"Requires designated predecessor searches, displays, links, accessibility checks, and reversible collection migration to pass before expansion or retirement decisions."}],"nearest_rivals":["Generic backlog prioritization: ranks items by value or urgency but need not recover the useful functions of predecessor constraints or distinguish successor parity from released ambition.","Minimum viable product planning: can reduce initial scope but may omit continuity with a validated predecessor, explicit treatment of postponed ambitions, and a reversible migration seam.","Metadata-profile and crosswalk governance: controls descriptive consistency but does not govern the combined flood of interface, architecture, integration, cleanup, and service ambitions.","Ordinary phased migration: sequences collections or systems but can still carry an overloaded target design into every phase.","Technical-debt triage: separates cleanup work but does not by itself define the successor core contract or protect deferred capabilities from entering as hidden parity requirements."],"negative_tests":{"intervention_falsifier":"The intervention is weakened if, after applying the charter to the real backlog, launch-tier coupling, validation work, support procedures, and unresolved dependencies remain indistinguishable from baseline planning, or if parked items routinely re-enter without satisfying their stated triggers.","problem_falsifier":"The diagnosed second-system pattern is absent if the predecessor did not establish a valued core, no stockpile of postponed capabilities exists, old constraints are not being relaxed, and the successor’s complexity consists only of independently mandatory current obligations.","risks":["A narrow core contract could preserve known metadata exclusions or poor discovery behavior.","Gatekeepers could classify inconvenient accessibility or community-description repairs as optional ambition.","A fixed complexity budget could conceal differences between superficial feature count and necessary semantic work.","Parallel operation could impose additional staff and synchronization burden.","Parked capabilities could become an indefinite holding area despite nominal review triggers.","Collection-by-collection migration could create temporarily inconsistent patron experiences.","Incumbent users’ familiar searches could dominate validation while less visible user journeys remain untested."],"strongest_counterevidence":"A requirements trace could show that the apparently ambitious capabilities are all necessary for current legal, accessibility, preservation, interoperability, or continuity constraints, and that staffing, validation, support, and reversible migration capacity have already been demonstrated for the integrated design."},"next_evidence_step":"Within ten working days, have the systems lead and two metadata or service representatives review a bounded sample of 30 successor backlog items and 12 high-use predecessor search journeys. Produce a constraint-function inventory, work-class assignments, a draft core contract, a dependency count for the proposed launch tier, and a list of disputed classifications. Make no build, procurement, migration, or retirement decision from this exercise alone.","observable_state":"A working first-generation discovery portal serves a bounded collection set through a small metadata profile, batch indexing, keyword search, facets, record pages, and stable links. Successor planning artifacts place reproduction of these functions alongside metadata remediation, linked-data modeling, additional repository integrations, full-text processing, personalization, analytics, and interface redesign. Observable indicators include items carrying multiple work classes, absent maintenance owners, additions lacking validation methods, dependencies that cross release boundaries, unresolved predecessor-search acceptance tests, and a cutover plan without a collection-level escape path.","prior_art_status":"UNSEARCHED","problem":"A library’s constrained first-generation digital-collections portal has established a usable retrieval core, but its planned successor is becoming a container for every omission exposed by that success. The original limits—few metadata profiles, a bounded collection set, batch updates, minimal configuration, and manual handling of exceptions—caused real problems while also keeping indexing, training, and support understandable. Once the replacement is authorized, parity work, metadata repair, linked-data generalization, new repositories, full-text services, personalization, analytics, preservation integration, and interface redesign enter one backlog. The library lacks a defended core contract, cumulative complexity limit, and legitimate path for deferring capabilities while preserving migration continuity.","proposal_index":1,"remaining_contrastive_claim":"Conditional on the described facts, the candidate addresses more than ordinary scope control: its defining claim is that successor risk arises from relaxing constraints after a validated first system has accumulated postponed ambitions, so governance must preserve or replace the useful functions of those constraints while protecting parity, staged deferral, and rollback.","revision_record":{"claim_changes":["Initial version; no prior claim was revised.","Claims are framed conditionally and do not assert novelty, prevalence, demand, or effect size."],"conceptual_changes":["Initial mapping of second-system constraint release to a library discovery-portal replacement.","Defined the predecessor’s narrow metadata and operating model as both a source of failures and a focusing device."],"evidence_changes":["No external evidence was searched.","Specified observable indicators, counterevidence, and bounded falsification criteria."],"operational_changes":["Initial release protocol includes work-class separation, a core contract, a multidimensional complexity budget, staged deferral, parallel validation, and a reversible migration seam."],"parent_version":null,"progress_targets_addressed":["Infer a concrete library and information science problem.","Preserve the archetype’s predecessor-success, constraint-release, ambition-flood, triage, staging, and launchability structure.","Bound authority and the first evidence step.","State problem and intervention falsifiers and material risks."]},"schema_version":1,"structural_mapping":[{"archetype_element":"Successful but constrained predecessor","domain_realization":"The first-generation digital-collections portal provides usable search and stable access for a bounded collection set through a narrow metadata profile and simple indexing pipeline."},{"archetype_element":"Predecessor constraint memory","domain_realization":"The library records how limited schemas, batch updates, few integrations, minimal configuration, and manual exceptions both caused failures and constrained testing, training, and support load."},{"archetype_element":"Deferred ambition backlog","domain_realization":"Recorded successor items include richer description, linked data, more repositories, full text, personalization, analytics, preservation integration, and interface redesign."},{"archetype_element":"Successor core contract","domain_realization":"The launch tier must preserve designated search journeys, facets, record context, stable identifiers, accessibility, and reversible migration while addressing only selected current failures."},{"archetype_element":"Preserved constraint function map","domain_realization":"Useful functions of narrowness are replaced with release gates, profile limits, explicit integration admission, support-capacity checks, and validation ownership rather than simply discarded."},{"archetype_element":"Ambition triage gate","domain_realization":"Every addition is classified and must identify evidence, semantic and technical coupling, maintenance ownership, validation needs, and launch consequences."},{"archetype_element":"Complexity and scope budget","domain_realization":"The launch tier caps the combined number and interaction of metadata profiles, crosswalks, index pipelines, integrations, interface modes, training changes, and support procedures."},{"archetype_element":"Staged successor release ladder","domain_realization":"Non-core capabilities move to stabilization, expansion, or later-review tiers with named owners and evidence or capacity triggers."},{"archetype_element":"Launchability gate","domain_realization":"The library tests buildability, retrieval parity, accessibility, staff support readiness, and collection-level migration before admitting further ambition or retiring the predecessor."},{"archetype_element":"Rollback or escape path","domain_realization":"The predecessor remains available while collections are migrated reversibly and validated in parallel, allowing failed mappings or releases to return to the prior access route."}],"title":"Constraint-Memory Gate for a Successor Digital-Collections Discovery Portal","version":0}