{"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__music_musicology","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"music_musicology","title":"Lifecycle Governance for Superseded Digital Music-Edition Layers","opportunity_summary":"Introduce explicit current, superseded, archived, quarantined, and deletion-eligible states for notation encodings, transcriptions, annotations, renders, and editorial records. The mechanism would demote obsolete artifacts from active discovery while preserving tombstones, successor links, restoration paths, and authority-controlled exceptions. The proposal is coherent and safely testable, but the sealed packet does not establish problem prevalence, stakeholder demand, realized benefit, or distinctiveness from existing repository and edition practices.","adopter_authorizer":"A consenting digital-edition project, authorized jointly by its designated scholarly editor and repository steward, with rights holders or community custodians retaining authority over restricted materials.","scores":{"meaningful_impact":{"score":3,"rationale":"Avoiding use of superseded readings and preserving reconstructable editorial provenance could materially benefit scholarship and performance, but the packet provides no evidence about incident frequency, affected collections, or consequence magnitude."},"stakeholder_pull":{"score":2,"rationale":"Editors, maintainers, users, and repository stewards are clearly identified, but no complaints, requests, commitments, observed workarounds, or willingness to allocate resources are supplied."},"incremental_advantage":{"score":4,"rationale":"Relative to naming conventions, folders, maintainer knowledge, or a latest-version pointer, the proposal adds explicit lifecycle states, dependency checks, preservation holds, tested restoration, governed exceptions, and successor links that directly address authority confusion and provenance risk."},"distinctiveness_plausibility":{"score":2,"rationale":"The domain adaptation is specific and coherent, but prior-art status is explicitly UNSEARCHED; the packet cannot establish whether comparable versioning, archival-status, citation-resolution, or preservation workflows already exist."},"technical_implementability":{"score":4,"rationale":"Status metadata, discovery demotion, tombstones, audit records, quarantine, and restoration testing are technically tractable for one bounded project, although incomplete identity resolution and dependency discovery could prevent safe classification."},"adoption_authority_feasibility":{"score":4,"rationale":"The proposal identifies joint scholarly-editor and repository-steward authority, preserves rights-holder and community-custodian control, and bounds the first step to one consenting project; coordination and disputed-value decisions remain nontrivial."},"evidence_readiness":{"score":4,"rationale":"The candidate supplies separate problem and intervention falsifiers, a bounded one-work test, rollback conditions, and observable outcomes, but retrieval events, authority-confusion coding, comparison windows, and preservation checks still require a predefined protocol."},"safety_net_benefit":{"score":5,"rationale":"Reversible quarantine, permanent-deletion exclusions, preservation holds, dependency checks, tombstones, successor links, restore verification, audit records, and explicit halt criteria provide unusually strong protection against provenance and access failures during evaluation."},"scalability":{"score":3,"rationale":"Lifecycle states and audit mechanisms could be reused across editions, but musical, philological, rights, cultural-custody, citation, and repository contexts require project-specific judgment and may limit automation or uniform rollout."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"Design and conduct a non-destructive audit and sandbox comparison for one work in one consenting project, including layer inventory, identity and dependency review, retrieval-task coding, restoration checks, and editor-repository interpretation.","confidence":"MODERATE","assumptions":["The work has tens to low hundreds of relevant artifacts rather than a collection-scale backlog.","Existing repository exports and version records are accessible without major data engineering.","Scholarly-editor and repository-steward participation is available for a limited review.","No permanent deletion or production discovery change occurs."]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"Prepare one project for controlled lifecycle management by defining policy, metadata mappings, authority roles, preservation holds, dependency checks, audit logging, quarantine storage, restoration procedures, and user-facing status presentation.","confidence":"LOW","assumptions":["The existing repository can be extended rather than replaced.","Persistent identifiers and successor links can be added without redesigning the edition platform.","Rights and cultural-custody review is bounded to the participating project.","Identity and dependency records are incomplete but recoverable through targeted manual review."]},"operational_launch":{"band_2026_usd":"50K_TO_250K","scope":"Launch the governed workflow across one established digital-edition project, including backlog classification, quality assurance, training, stakeholder communication, monitored discovery changes, exception review, and evaluation.","confidence":"LOW","assumptions":["Launch covers one project or repository collection, not a multi-institution consortium.","Most artifacts can be classified through metadata-assisted review with expert escalation.","Cited, unique, contested, restricted, and dependency-uncertain objects remain active or held.","Existing preservation infrastructure supports quarantine and verified restoration."]},"annual_recurring":{"band_2026_usd":"10K_TO_50K","scope":"Maintain lifecycle labels and successor links, review exceptions and preservation holds, revalidate classifications, test restoration, monitor retrieval incidents, and administer scholarly, repository, rights, and custody disputes for one project.","confidence":"LOW","assumptions":["Artifact growth and exception volume remain modest.","The workflow is integrated into ordinary editorial and repository operations.","No major archive migration, format remediation program, or litigation is included.","Recurring review requires periodic expert labor rather than a dedicated full-time team."]}},"research_burden":"MODERATE","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The packet specifies an observable authority-confusion and preservation problem with a clear falsifier, but supplies no observed incidents, retrieval data, maintenance burden, or stakeholder testimony showing that it is material in an actual project."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"A consenting edition project is the adopter, with its designated scholarly editor and repository steward jointly authorizing rules and rights holders or community custodians controlling restricted materials."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal claims that explicit lifecycle states and discovery demotion will reduce retrieval of superseded layers as current relative to ordinary naming, folder, or latest-pointer practices, without causing citation, provenance, access, or reconstruction failure."},"bounded_next_evidence_step":{"status":"YES","reason":"One work can be inventoried and evaluated non-destructively in a sandbox with fixed retrieval tasks, baseline comparison, predefined confusion coding, dependency review, and restoration checks."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The candidate excludes permanent deletion in the first step, preserves authority for editors, stewards, rights holders, and custodians, and requires halt and restoration upon citation, dependency, rights, restoration, or scholarly-value concerns."},"implementation_cost_scope_and_range":{"status":"YES","reason":"The one-work evidence scope and one-project implementation scope are sufficiently bounded to assign broad resource bands, although repository condition, backlog size, and expert-review needs keep confidence moderate to low."}},"blocking_evidence":["Observed frequency and consequence of users retrieving or treating superseded layers as endorsed in a consenting project.","Evidence of editor, performer, scholar, and repository-steward demand or willingness to adopt the added governance process.","Prior-art comparison covering edition versioning, archival-status metadata, persistent citation resolution, repository discovery controls, and preservation workflows.","Evidence that layer identities, citations, derivatives, restrictions, and dependencies can be discovered completely enough for safe demotion or quarantine.","A predefined measurement protocol for retrieval events, authority-confusion coding, comparison conditions, restoration success, and unacceptable provenance or access harm."],"next_evidence_step":"For one work in one consenting project, run a preregistered, non-destructive audit and sandbox retrieval study: inventory identity-resolved layers, citations, restrictions, and dependencies; compare fixed user tasks under the ordinary discovery baseline versus simulated lifecycle labels and successor links; and stop before production changes. Falsify the opportunity if the audit finds no material stale-authority incidents or burden, if lifecycle presentation does not reduce mistaken-current selections, or if any layer cannot be reliably reconstructed, restored, or protected.","research_questions":["How often do users encounter or rely on superseded layers as current, and what scholarly, performance, or maintenance consequences follow?","Which stakeholders experience enough burden to request or authorize lifecycle governance, and what additional process would they tolerate?","Which comparable lifecycle, versioning, citation-resolution, and preservation mechanisms already exist in digital-edition or repository practice?","Can identities, citations, derivatives, access restrictions, and dependencies be discovered with sufficient recall to make demotion and quarantine safe?","How should contested, minority, culturally important, or historically significant states be protected from visibility bias introduced by demotion?","Do lifecycle labels and successor links outperform an immutable history with a latest pointer on mistaken-current retrieval without impairing provenance or reconstruction?","What repository features, staffing levels, backlog sizes, and review volumes drive startup and recurring resource requirements?","How can tombstones and lifecycle metadata avoid accumulating indefinitely or disclosing restricted information?"],"recommendation":"PRIOR_ART_RESEARCH","uncertainty_constraints":["Closed-book evaluation provides no external evidence of prevalence, stakeholder pull, existing practice, novelty, market size, realized impact, or exact cost.","The proposal is at HYPOTHESIS maturity and its generator confidence is not empirical validation.","Cost bands are resource-equivalent planning ranges based on assumed one-work and one-project scopes, not observed quotations or implementation histories.","Technical feasibility depends on repository-specific identity, dependency, citation, rights, credential, and restoration conditions.","An old editorial state may acquire historical or cultural value, so age and low access cannot establish disposability.","The incremental effect remains uncertain until baseline and lifecycle-assisted retrieval are compared using predefined outcome coding."],"closed_book_prior_art_boundary":"The packet explicitly marks prior art as UNSEARCHED. This assessment therefore makes no claim that explicit lifecycle states, discovery demotion, tombstones, successor links, preservation holds, restoration tests, or governed exceptions are novel or uncommon in digital music editions, scholarly encoding, libraries, or repositories; distinctiveness requires external research."}