{"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__criminology_forensic","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"criminology_forensic","title":"Governed Artifact-Level Lifecycle Management for Forensic Case Repositories","opportunity_summary":"Apply explicit lifecycle states, class-based retention rules, legal holds, dependency checks, archival demotion, controlled quarantine, restoration testing, and auditable disposition records to forensic originals, derivatives, notes, interpretations, and reports. The proposal aims to reduce misleading stale artifacts in active search while preserving disclosure, appeal, reconstruction, and evidentiary integrity; both problem prevalence and realized benefit remain hypotheses.","adopter_authorizer":"A forensic laboratory evidence custodian and records authority, acting with legal counsel and subject to court orders, disclosure obligations, accredited policy, and review by affected case authorities.","scores":{"meaningful_impact":{"score":3,"rationale":"Avoiding obsolete interpretations, unnecessary sensitive-data exposure, and loss of material needed for disclosure or appeal could be consequential, but the packet provides no evidence about prevalence, incident frequency, or aggregate burden."},"stakeholder_pull":{"score":3,"rationale":"Laboratory managers, custodians, examiners, courts, prosecution, defense, and data subjects have identifiable interests in the problem, but no stakeholder request, purchasing commitment, adoption inquiry, or demonstrated operational demand is supplied."},"incremental_advantage":{"score":4,"rationale":"Relative to retaining artifacts in active search or archiving whole case folders by age, artifact-level authority, supersession, dependency, hold, and restoration gates directly address the stated failure modes. The size of the improvement remains untested."},"distinctiveness_plausibility":{"score":3,"rationale":"The combination is more specific than the stated whole-folder archival rival, but prior art is explicitly unsearched, so distinctiveness within existing forensic retention and evidence-management practice cannot be established closed-book."},"technical_implementability":{"score":3,"rationale":"Read-only inventory, simulated rules, and copied-sample restoration tests are technically bounded, while production feasibility depends on resolving artifact identities, lineage, dependencies, formats, credentials, and archive integrity across existing repositories."},"adoption_authority_feasibility":{"score":3,"rationale":"The packet identifies custodial and records authorities and limits examiner authority, but lawful action remains conditional on jurisdiction-specific holds, disclosure duties, court orders, counsel, and case-authority review."},"evidence_readiness":{"score":4,"rationale":"The candidate supplies separate problem and intervention falsifiers, a reversible read-only first step, a baseline comparison, zero-tolerance safety events, and explicit halt conditions. Sampling, adjudication, and outcome definitions still require predeclaration."},"safety_net_benefit":{"score":4,"rationale":"The mechanism could protect defendants, convicted persons, victims, witnesses, and other data subjects by preserving probative or exculpatory material while limiting stale authority signals and unnecessary exposure. Archive failure, biased labels, and mistaken disposition remain serious risks."},"scalability":{"score":3,"rationale":"Class-based policies and reusable lifecycle states could extend across artifacts and cases, but repository heterogeneity, incomplete lineage, format obsolescence, and jurisdiction-specific retention authority constrain replication."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"One laboratory's bounded, read-only study covering a stratified closed-case sample, artifact inventory and adjudication, simulated lifecycle rules, baseline comparison, copied-archive restoration tests, legal and records review, and an evaluation report.","confidence":"LOW","assumptions":["Repository exports and audit records are available without major new integration.","The sample is bounded and no production deletion or access change occurs.","Laboratory, legal, defense-disclosure, records, and technical personnel must contribute time.","Sensitive case data remain inside an approved environment."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Policy specification and approval, repository integration design, metadata and lineage remediation, hold and authority-rule configuration, archival architecture, security assessment, validation planning, and staff training for one laboratory environment.","confidence":"LOW","assumptions":["A usable repository API or export mechanism exists.","Original evidence is excluded from automated disposition.","Existing identity and lineage data need material but not complete reconstruction.","Jurisdiction-specific legal review is required."]},"operational_launch":{"band_2026_usd":"1M_TO_5M","scope":"Production implementation for one laboratory or comparable forensic organization, including integrations, metadata remediation, archival and restoration infrastructure, shadow validation, security and compliance work, training, independent review, and controlled operational rollout.","confidence":"LOW","assumptions":["Multiple artifact classes and legacy case formats are in scope.","Zero-tolerance hold, dependency, and restoration controls require extensive testing.","Launch does not authorize bulk deletion or override external case authority.","Major replacement of the core evidence-management platform is not required."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Ongoing policy and hold revalidation, exception review, artifact adjudication, archive integrity and restoration testing, credential and format maintenance, audit support, software and storage, incident response, and training.","confidence":"LOW","assumptions":["The estimate covers one laboratory-scale operation.","Human review remains mandatory for consequential lifecycle changes.","Case volume, retention duration, and archive size are unspecified.","Periodic legal and policy updates are necessary."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"YES","reason":"The sealed candidate identifies a coherent conflict between stale derivatives retaining apparent authority and indiscriminate cleanup threatening disclosure, appeal, chain-of-custody reconstruction, and reproducibility. Its prevalence and magnitude still require measurement."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"The laboratory evidence custodian and records authority are named as decision authorities, with legal counsel, court orders, disclosure duties, accredited policy, and affected case authorities defining their limits."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The candidate claims that artifact-level lifecycle and dependency rules will outperform ordinary retention or age-based whole-case archiving by reducing stale items in active search and review effort without missed holds, broken dependencies, incorrect authority labels, or failed restoration."},"bounded_next_evidence_step":{"status":"YES","reason":"A stratified, read-only closed-case study with simulated gates and restoration tests on copied archive samples is specified; it makes no production deletion or access change and has explicit falsifiers and halt conditions."},"no_unresolved_safety_or_authority_stop":{"status":"UNCERTAIN","reason":"The proposed first step is reversible and excludes destructive action, but local legal authority, hold completeness, disclosure obligations, lineage reliability, and restoration integrity must be confirmed by authorized partners before even simulated disposition findings can support adoption."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"The packet bounds the mechanism and pilot activities but does not state repository scale, case volume, metadata quality, integration interfaces, archive condition, staffing, or jurisdictional coordination needs; only low-confidence resource bands are supportable."}},"blocking_evidence":["A representative audit must establish that incomplete lifecycle metadata or accumulated artifacts cause material stale-search, review-effort, exposure, maintenance, or capacity consequences.","Artifact identity, lineage, dependency, hold, and authority-label accuracy must satisfy predeclared safety criteria; any missed hold or relied-upon dependency is a stop condition.","Copied archival samples must restore with verified integrity, usable credentials, and reconstructable lineage.","Authorized local legal and records review must establish applicable retention, disclosure, appeal, court-order, and disposition rules.","External prior-art research is required before asserting that the artifact-level lifecycle combination is distinct from existing forensic repository practice."],"next_evidence_step":"With one authorized forensic laboratory, predeclare a stratified closed-case sampling frame, artifact denominators, label-adjudication procedure, baseline observation window, review-effort measure, and zero-tolerance safety accounting. Run a read-only shadow study comparing current active-search results and review effort with simulated artifact-level lifecycle rules, and test restoration only on copied archive samples. Reject progression if the problem falsifier is met, if stale-search or effort outcomes do not improve, or if any missed hold, broken dependency, incorrect authority label, impaired disclosure or reconstruction, or failed integrity restoration occurs.","research_questions":["How often do closed and long-running cases contain artifacts with missing or conflicting authority, supersession, retention, hold, dependency, access, or recoverability metadata?","What measurable search errors, review effort, exposure, maintenance burden, or capacity consequences are attributable to those artifacts under the ordinary baseline?","Can artifact identities and lineage be resolved reliably enough to prevent originals and relied-upon derivatives from entering disposition pathways?","Do simulated lifecycle rules reduce stale items in active search and review effort relative to the baseline without any safety-threshold violation?","Which artifact classes, case types, legal statuses, and jurisdictions require distinct retention and authority rules?","Can archived copies be restored repeatedly with verified integrity, usable formats and credentials, and complete audit lineage?","How does the proposal compare with documented forensic retention, supersession, evidence-management, and archival-restoration workflows?","What production integration, metadata-remediation, staffing, compliance, and recurring review resources would a specific laboratory require?"],"recommendation":"PARTNERED_RESEARCH","uncertainty_constraints":["No external evidence supports problem prevalence, stakeholder demand, benefit magnitude, market size, or realized impact.","Prior art is unsearched, so world novelty and practice-level distinctiveness are unmeasured.","Legal authority and retention obligations vary by jurisdiction, case type, procedural status, and court order.","Repository scale, artifact volume, metadata quality, interfaces, archive condition, staffing, and restoration performance are unspecified.","The candidate is a hypothesis and does not establish that staleness labels are accurate, unbiased, or safe for production decisions.","Cost bands are resource-equivalent planning ranges, not quotations or point estimates."],"closed_book_prior_art_boundary":"No prior-art search or external comparison was performed. The assessment can recognize structural differences from the packet's stated baseline and nearest rival, but it cannot claim novelty, prevalence, market differentiation, or absence of equivalent forensic laboratory workflows."}