{"schema_version":1,"assessment_id":"eoa_inverse_innovation_exp03_opportunity320_20260801","source_experiment_id":"eoa_inverse_innovation_exp03_full320_20260801","cell_id":"layer_decay_and_expiration_management__gender_studies","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"gender_studies","title":"Lifecycle labeling and supersession routing for gender-research artifacts","opportunity_summary":"A repository workflow would assign explicit lifecycle and successor labels to versioned survey instruments, identity-category codebooks, consent language, crosswalks, and analytic guidance; route ordinary searches toward approved current artifacts; preserve labeled historical access; and gate disposition on dependencies, authority, exceptions, and restoration checks. The intended result is less accidental wrong-version reuse without loss of evidence needed for longitudinal interpretation, reproducibility, or accountability.","adopter_authorizer":"The repository data steward is the operational adopter and may label and route artifacts. Irreversible disposition requires the artifact owner and locally designated ethics or records authority, with affected-community consultation when representational stakes are material.","scores":{"meaningful_impact":{"score":4,"rationale":"If accidental wrong-version reuse occurs materially, reducing it while preserving historical evidence could improve study validity, representation, reproducibility, and accountability. The score is limited because prevalence and effect magnitude are unverified."},"stakeholder_pull":{"score":2,"rationale":"The candidate identifies researchers, curators, participants, communities, and governance authorities with plausible interests, but supplies no evidence of expressed demand, current burden, budget ownership, or willingness to adopt."},"incremental_advantage":{"score":3,"rationale":"Relative to the stated immutable versioned-repository rival, decay triggers, an exception register, dependency-gated disposition, successor-biased routing, quarantine, and restoration testing form a testable increment. Whether that bundle improves outcomes enough to justify added work remains unknown."},"distinctiveness_plausibility":{"score":3,"rationale":"The lifecycle-state bundle is coherently differentiated from the stated nearest rival, but repository preservation and records-governance prior art is unsearched, so real-world distinctiveness cannot be established closed-book."},"technical_implementability":{"score":4,"rationale":"A read-only pilot using metadata labels, recorded successors, search comparisons, index snapshots, and restore drills appears technically tractable on at most 100 artifacts. Contextual-staleness judgments and dependency discovery remain difficult human-governance tasks."},"adoption_authority_feasibility":{"score":3,"rationale":"The proposal names a data steward for labeling and routing and reserves irreversible actions for owners plus ethics or records authorities. Feasibility is mixed because authority is distributed and material cases may require consultation and resolution of contested classifications."},"evidence_readiness":{"score":4,"rationale":"The candidate supplies a bounded 90-day read-only design, a matched-baseline comparison, observable selection and retrieval outcomes, restore drills, separate problem and intervention falsifiers, and rollback conditions. Sampling representativeness and tolerances still require specification."},"safety_net_benefit":{"score":4,"rationale":"Historical labeling, dependency checks, reversible quarantine, snapshots, restoration testing, excluded hard deletion, and explicit halt conditions provide substantial protection against evidence loss and misclassification. They do not eliminate risks of practical inaccessibility or institutionalized bias."},"scalability":{"score":2,"rationale":"Scaling requires continuing contextual review, authority maintenance, dependency tracing, dispute handling, community consultation, and label upkeep across heterogeneous artifacts. The candidate itself identifies curator workload and disagreement as potential failure conditions, and supplies no scale evidence."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Design and conduct the 90-day read-only study on at most 100 artifacts from two consenting collections, including inventory, proposed labels, matched search tasks, owner review, restore drills, analysis, and governance coordination.","confidence":"LOW","assumptions":["Artifacts and repository access are available from consenting collections.","No production access restrictions or deletions occur.","Existing staff can supply repository, research-methods, ethics, and evaluation input.","The band includes labor and coordination but not a new enterprise repository platform."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Prepare a limited institutional implementation after favorable evidence, including lifecycle rules, metadata schema, successor and exception records, review workflows, search-routing changes, audit logging, training, and governance approvals.","confidence":"LOW","assumptions":["Implementation extends an existing repository rather than replacing it.","Integration is limited to a small number of repository and search systems.","Sensitive-data controls already exist and require configuration rather than wholesale construction.","The number and complexity of legacy dependencies are unknown."]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Apply the approved workflow to an initial multi-collection repository population, resolve dependencies and contested labels, conduct affected-party review where needed, test restoration, and evaluate launch outcomes.","confidence":"LOW","assumptions":["Launch is institution-scale rather than sector-wide.","Artifact volume is materially larger than the pilot but does not require mass manual reconstruction of all historical citations.","No irreversible bulk disposition is included.","Governance and repository staff are available for sustained review."]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Maintain lifecycle labels and successor links, review triggers and exceptions, handle disputes and new versions, monitor wrong-version selection and historical retrieval, and perform periodic restore tests.","confidence":"LOW","assumptions":["The institution operates an existing repository and search service.","Review volume remains manageable by a small cross-functional allocation rather than a dedicated large team.","Community consultation is targeted to materially representational cases.","External citation tracing remains bounded."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"YES","reason":"The candidate specifies an observable and falsifiable problem: contradictory versions lacking reliable lifecycle labels, accidental selection of superseded artifacts, and preservation risks. External evidence is still needed to determine its prevalence and materiality."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"Repository data stewards are identified as operational adopters, while artifact owners and local ethics or records authorities are identified for irreversible decisions; affected-community consultation is assigned for material representational stakes."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal claims that explicit lifecycle states, decay review, exception and dependency controls, successor-biased routing, and restore testing will outperform an immutable versioned repository with a current-version index on wrong-version selection and decision time without worsening historical retrieval."},"bounded_next_evidence_step":{"status":"YES","reason":"A 90-day, read-only study covering at most 100 artifacts from two consenting collections is bounded by duration, sample, permissions, outcomes, comparison, halt conditions, and rollback."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The first step prohibits deletion and access restriction, preserves the prior index, names decision authorities, excludes age-only invalidation and universal-vocabulary claims, and halts for material misclassification, unresolved dependencies, restore failure, or worsened historical retrieval."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"The pilot scope supports a broad first-evidence estimate, but the sealed candidate does not specify repository scale, integration complexity, artifact volume, dependency density, consultation load, or staffing needed for deployment and recurring operation."}},"blocking_evidence":["A representative audit establishing whether accidental superseded-artifact selection and associated search or interpretation burdens are material rather than negligible.","Evidence distinguishing mistaken current-use selection from intentional historical or longitudinal use.","Comparative results against the maintained current-version-index rival on wrong-version selection, decision time, historical retrieval, unresolved citations, complaints, and restore fidelity.","Inter-rater and affected-owner evidence that lifecycle classifications can remain reliable despite contested or non-monotonic gender and sexuality concepts.","A deployment inventory covering repository scale, integrations, sensitive-data controls, dependency density, governance workload, and consultation requirements.","External prior-art review determining whether the proposed bundle is already present in mature repository, preservation, metadata, or records-lifecycle practice."],"next_evidence_step":"Run the authorized 90-day read-only study on at most 100 artifacts from two consenting collections. Compare proposed lifecycle-and-successor labels with matched searches using the existing maintained version index, measuring accidental wrong-version selection, decision time, historical retrieval, unresolved citations, representational complaints, and restore fidelity. Treat negligible baseline misuse, no improvement over the rival, or worsened historical retrieval or restoration as falsifying evidence; make no deletion or access change and roll back pilot labels from the recorded snapshot if halt conditions occur.","research_questions":["How often do representative users accidentally select a superseded artifact, and how often is older-artifact use intentional historical or longitudinal work?","Does the lifecycle workflow outperform a prominently maintained current-version index on selection accuracy and decision time?","Does routing toward current artifacts impair historical retrieval, citation resolution, or interpretation of prior datasets?","Can reviewers and affected owners classify contextual staleness consistently without suppressing contested or minority frameworks?","What artifact dependencies, authorized holds, privacy constraints, and external citations must be preserved?","What curator, owner, ethics, records, and community-consultation workload is required to keep labels reliable?","Which existing repository and governance capabilities could implement the workflow, and what integration gaps remain?","What prior art already combines versioning, lifecycle metadata, preservation, exception handling, dependency-gated disposition, and restoration testing?"] ,"recommendation":"VALIDATE_PROBLEM_FIRST","uncertainty_constraints":["Problem prevalence, accidental-use frequency, effect size, and institutional demand are unverified.","Prior art and real-world distinctiveness are unverified.","Older terminology is not inherently invalid, and conceptual change is neither monotonic nor universally agreed.","The proposal could institutionalize majority judgments or make retained historical evidence practically inaccessible.","Repository scale, integration needs, dependency density, consultation burden, and exact resource requirements are unspecified.","Cost bands are resource-equivalent planning ranges based only on the bounded candidate description, not observed procurement or implementation data.","Pilot findings from two consenting collections may not generalize to other institutions, disciplines, or governance regimes."],"closed_book_prior_art_boundary":"Prior art is unsearched and unverified. This closed-book assessment establishes only the candidate's internal coherence, testability, and stated differentiation from its sealed nearest rival; it does not establish novelty, prevalence, market size, realized impact, or superiority to existing repository, preservation, metadata, or records-governance practices."}