{"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__cultural_studies","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"cultural_studies","title":"Governed Lifecycle for Public Interpretive Layers in Community Cultural Archives","opportunity_summary":"Test a governed, reversible lifecycle for captions, tags, notices, essays, and annotations so users can distinguish current guidance from historical framing while provenance, disagreement, attribution, and restoration paths remain intact. The proposal is structurally testable, but problem prevalence, comparative benefit, institutional demand, and distinctiveness are unsupported in the sealed record.","adopter_authorizer":"The adopting party is a community archive, museum, library, or digital-exhibition steward. Its designated steward may authorize reversible visibility changes; contested classification or irreversible destruction additionally requires documented records or legal approval and participation by materially affected communities.","scores":{"meaningful_impact":{"score":4,"rationale":"If users mistake obsolete or harmful framing for current guidance, the proposed separation of active and historical interpretation could materially improve accountability and representation while preserving evidence of change. The sealed candidate does not establish how often or widely this problem occurs."},"stakeholder_pull":{"score":3,"rationale":"Curators, represented communities, contributors, researchers, and visitors have plausible interests in clearer currency and preserved provenance, but the candidate contains no direct demand evidence, adoption inquiry, or demonstrated willingness to contribute review labor."},"incremental_advantage":{"score":4,"rationale":"Relative to dated version history alone, supersession markers, tiered presentation, dependency checks, reversible disposition, and restoration directly target apparent authority rather than merely documenting chronology. Whether this improves understanding without hiding useful contestation remains untested."},"distinctiveness_plausibility":{"score":2,"rationale":"The combination is coherent, but prior-art status is explicitly UNSEARCHED and the candidate provides no comparison with existing archival description, reparative-description, community-governance, versioning, or preservation practices. Distinctiveness therefore has little affirmative support."},"technical_implementability":{"score":4,"rationale":"Inventory fields, status markers, tiered visibility, quarantine, audit records, soft deletion, and restoration are technically plausible metadata and presentation functions. Integration with collection systems, citations, access controls, and restricted-content rules is unspecified."},"adoption_authority_feasibility":{"score":3,"rationale":"The candidate identifies a steward and bounds reversible decisions, but contested classifications may require community, records, legal, privacy, and donor authority whose mandates can conflict. Authority is recognizable but coordination feasibility is uncertain."},"evidence_readiness":{"score":4,"rationale":"The proposal supplies separate problem and intervention falsifiers, an explicit comparator, a bounded sample, reversible actions, halt conditions, and measurable harms. User-testing methods and decision thresholds still need specification."},"safety_net_benefit":{"score":5,"rationale":"Soft deletion, quarantine, durable audit records, dependency checks, tested restoration, no pilot hard deletion, and explicit rollback directly reduce the risks of silencing, provenance loss, and irreversible error."},"scalability":{"score":3,"rationale":"The lifecycle structure could be reused across collections, but classification and disposition are culturally specific and require contextual review, affected-community participation, dependency analysis, and potentially uncompensated labor. Scaling without degrading legitimacy is unresolved."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Design and run the bounded eight-week study on at most 50 layers from one collection, including inventory, compensated affected-community review, metadata preparation, a dated-version-history comparison, limited reversible supersession, user assessment, audit documentation, and restoration testing.","confidence":"LOW","assumptions":["Existing collection and metadata systems can be used without major procurement or migration.","Restricted material can be handled within existing access controls.","The band includes staff labor, participant compensation, evaluation, governance coordination, and compliance review.","No hard deletion or broad public rollout occurs."]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"Prepare one collection for controlled production use by defining governance rules, metadata fields, status displays, audit and quarantine workflows, restoration procedures, staff training, and limited system integration.","confidence":"LOW","assumptions":["The archive already operates a modifiable digital collections platform.","Implementation is limited to one institution and a small number of collections.","No extensive legacy-data remediation or replacement platform is required.","Community governance and legal review are available but not unusually protracted."]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Launch across multiple collections within one institution, including backlog inventory, platform integration, access-control testing, consultation, citation and dependency handling, documentation, training, evaluation, and remediation capacity.","confidence":"LOW","assumptions":["Launch is institutional rather than multi-institutional.","A substantial but bounded metadata backlog requires human review.","Sensitive-content controls and audit infrastructure need adaptation rather than complete replacement.","Consultation participants are compensated and disputes receive dedicated coordination."]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Operate recurring review cycles, community participation, dispute handling, metadata maintenance, audit retention, restoration tests, training, user monitoring, and software support for one institution.","confidence":"LOW","assumptions":["Review volume remains moderate and does not require a large permanent department.","Existing archive staff absorb part of the workflow.","No major platform migration or extraordinary legal dispute occurs.","Community participation and accessibility support remain funded."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The candidate specifies a recognizable observable condition—contradictory layers without visible currency—and plausible harms, but supplies no external or user evidence that confusion, representational harm, or deferred cleanup occurs materially in a target collection."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"The archive's designated steward is identified for reversible visibility changes, with records or legal authorities and materially affected community representatives required for contested or irreversible decisions."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal claims that governed lifecycle treatment will improve identification of current guidance beyond dated version history alone without reducing discovery of relevant historical context or increasing disputes, broken citations, or restoration failures."},"bounded_next_evidence_step":{"status":"YES","reason":"An eight-week, metadata-only study on at most 50 layers is bounded, excludes hard deletion, limits reversible supersession to ten layers, and can compare lifecycle treatment with dated version history using explicit falsifiers."},"no_unresolved_safety_or_authority_stop":{"status":"UNCERTAIN","reason":"The candidate defines exclusions, halt conditions, rollback, and community participation, but the actual collection's legal, donor, privacy, records, and community mandates are unknown and may prevent even reversible visibility changes."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"The pilot bounds duration and sample size, but the sealed candidate does not specify platform architecture, metadata quality, backlog size, participant compensation, compliance workload, or integration effort sufficiently to validate implementation ranges."}},"blocking_evidence":["Baseline evidence that sampled users mistake historical layers for current guidance or experience a measurable search, trust, or representational problem.","Comparative evidence that lifecycle treatment outperforms dated version history in identifying current guidance without reducing access to relevant historical context.","Evidence that affected communities recognize the proposed decision process as legitimate and are not subjected to tokenistic or uncompensated participation.","Verification that attribution, citations, dependencies, restricted-content controls, audit history, and restoration remain intact after reversible supersession.","A prior-art comparison establishing whether the combined mechanism adds anything material to existing archival and community-governance practices.","Collection-specific confirmation of steward, community, records, legal, privacy, and donor authority."],"next_evidence_step":"Conduct the authorized eight-week study on no more than 50 layers from one collection. First measure whether users distinguish current from historical interpretation; then compare dated version history alone with the proposed lifecycle presentation using matched tasks. Falsify the opportunity if baseline confusion is absent, or if lifecycle treatment fails to improve identification of current guidance while reducing discovery of historical context or increasing disputes, citation failures, sensitive exposure, or restoration failures. Allow no hard deletion and restore prior visibility on any halt condition.","research_questions":["How frequently do target users misidentify historical interpretation as current guidance, and what consequences follow?","Does lifecycle presentation outperform dated version history alone on current-guidance identification while preserving discovery of historical contestation?","Which parties possess legitimate authority for each disposition, and how should conflicts among community, legal, donor, privacy, and records obligations be resolved?","Can the system preserve attribution, citations, dependencies, access restrictions, audit history, and reliable restoration through every reversible disposition?","How does the proposal differ materially from existing archival description, versioning, reparative-description, community-archive governance, and digital-preservation practices?","What staffing, compensation, integration, and recurring-review burden arises per collection without converting consultation into unpaid labor?"] ,"recommendation":"PARTNERED_RESEARCH","uncertainty_constraints":["Closed-book assessment with no external validation.","Problem prevalence, stakeholder demand, market size, and realized impact are unmeasured.","Prior art and world novelty are unsearched.","Cost bands are resource-equivalent planning ranges, not estimates based on a specified platform or institution.","The legitimacy and availability of affected-community representatives are collection-specific.","Cultural currency and harm cannot be inferred safely from age, access frequency, or automated contradiction signals.","Legal, donor, privacy, records, and community obligations may conflict.","Scalability depends on retaining contextual human judgment and compensated participation."],"closed_book_prior_art_boundary":"No conclusion is made about novelty, prevalence, adoption, or existing implementations. The sealed packet labels prior art UNSEARCHED; comparison with archival description, versioning, reparative description, community-archive governance, and digital-preservation practice requires external research."}