{"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__physics","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"physics","title":"Validity-Gated Lifecycle Management for Detector Calibration Payloads","opportunity_summary":"Evaluate a per-payload lifecycle system that uses explicit validity, supersession, dependency checks, tiering, quarantine, and restore testing to prevent obsolete calibrations from default use while preserving historical reconstruction. The candidate is specific and safely testable, but the prevalence of out-of-validity selection, its advantage over campaign-level approval and frozen environments, and its distinctiveness from established conditions-data practices remain unverified.","adopter_authorizer":"Detector calibration and operations groups would adopt the workflow; calibration owners authorize validity and supersession, data stewards authorize tiering, and records or publication authorities authorize holds and any irreversible deletion.","scores":{"meaningful_impact":{"score":4,"rationale":"If obsolete constants remain selectable, reconstructed observables and uncertainty estimates can be biased, while careless removal can undermine published-result reproducibility. The consequence is scientifically important, although its frequency and magnitude are unsupported."},"stakeholder_pull":{"score":3,"rationale":"Analysts, calibration teams, data stewards, and publication authorities have identifiable interests in correct selection and reproducibility, but the candidate supplies no evidence that they currently experience enough ambiguity, failures, or operating burden to demand a new lifecycle system."},"incremental_advantage":{"score":3,"rationale":"Per-payload validity and dependency-gated archival could improve on one approved calibration per campaign plus frozen historical environments by exposing lifecycle state and hidden dependents. Whether it reduces errors or clutter enough to justify added metadata and coordination is untested."},"distinctiveness_plausibility":{"score":2,"rationale":"The integrated composition is coherent, but the packet explicitly notes that conditions-database validity intervals, provenance, and reproducibility practices may already provide similar machinery. Prior art and deployed practice are unsearched."},"technical_implementability":{"score":4,"rationale":"Inventorying payloads, adding lifecycle metadata, generating shadow warnings, archiving immutable copies, and running restore tests are technically bounded extensions to the named conditions-database and reconstruction systems. Hidden or dynamic dependencies remain a material implementation risk."},"adoption_authority_feasibility":{"score":4,"rationale":"The candidate assigns validity, tiering, holds, and deletion decisions to specific authorities and permits a non-destructive subsystem pilot. Multi-party approval and records obligations may slow broader adoption but do not prevent the authorized first step."},"evidence_readiness":{"score":4,"rationale":"The proposal defines observable states, a representative-job problem falsifier, an intervention comparison against the nearest rival, harm measures, halt conditions, and a bounded shadow-mode test. Baseline rates and numerical tolerances still must be established."},"safety_net_benefit":{"score":5,"rationale":"Immutable archive copies, dependency and hold checks, quarantine, restore drills, shadow operation, explicit exclusions, and rollback directly protect reproducibility while testing whether stale selections can be reduced."},"scalability":{"score":3,"rationale":"The lifecycle model could extend across payload types and detector subsystems, but metadata stewardship, subsystem-specific validity rules, dependency discovery, storage tiers, and restore verification may impose substantial recurring coordination at scale."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Inventory and label payloads for one detector subsystem and two completed run periods; map dependencies; replay representative reconstruction jobs in shadow mode; archive copies; restore a stratified sample; and compare outcomes with the campaign-level rival without deleting or changing production artifacts.","confidence":"MODERATE","assumptions":["Existing conditions-database logs and representative reconstruction jobs are accessible.","The subsystem contains a manageable payload set and can be assessed by a small cross-functional team.","No new detector hardware or production enforcement is required.","Compliance, archive, and calibration-owner review are included."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Design and integrate lifecycle metadata, selection warnings or gates, dependency reporting, archive and quarantine workflows, audit records, operational documentation, and validation across several subsystems.","confidence":"LOW","assumptions":["Existing database and reconstruction platforms can be extended rather than replaced.","Integration must accommodate subsystem-specific validity semantics and external dependencies.","The scope excludes organization-wide historical remediation and irreversible deletion.","Security, records, software, testing, and partner coordination are included."]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Production rollout across the experiment, including migration of active payloads, governance approvals, training, monitoring, restore drills, staged enforcement, and remediation of unresolved references.","confidence":"LOW","assumptions":["The pilot demonstrates benefit without exceeding predeclared reconstruction or restore-failure tolerances.","Rollout covers one experimental collaboration rather than multiple institutions or experiments.","Existing archival infrastructure has adequate capacity or can be expanded within the band.","Deletion remains separately authorized and is not necessary for launch."]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Maintain lifecycle metadata and selection rules, review supersession and holds, monitor out-of-validity loads, operate archive tiers, conduct periodic restore drills, and support audits and exceptions.","confidence":"LOW","assumptions":["Most work is absorbed by an existing calibration, software, and data-stewardship team.","Storage growth and cold-tier retrieval remain moderate.","Lifecycle metadata can be updated through established calibration-release workflows.","Major platform replacement or large-scale reprocessing is excluded."]}},"research_burden":"MODERATE","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The candidate identifies observable out-of-validity loads, ambiguous lifecycle state, and reproducibility risks, but supplies no external or empirical evidence that these conditions occur in representative detector workflows."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"Calibration and operations groups are identifiable adopters, with calibration owners, data stewards, and records or publication authorities assigned distinct approval responsibilities."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal can test whether per-payload lifecycle gating reduces out-of-validity selection and active clutter relative to one approved calibration per campaign plus frozen historical environments, without increasing reconstruction, reference, or restore failures beyond tolerance."},"bounded_next_evidence_step":{"status":"YES","reason":"The authorized first step is limited to one subsystem and two completed run periods, operates in shadow mode, archives copies, restores a sample, forbids deletion, and has explicit halt conditions."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The first step does not change production or published artifacts, assigns relevant authority, preserves immutable originals, and halts on incomplete dependency coverage, selection conflicts, or restore-fidelity failures."},"implementation_cost_scope_and_range":{"status":"YES","reason":"The subsystem pilot, platform integration, experiment-level launch, and recurring stewardship are separable scopes that support broad resource-equivalent bands, although estimates remain assumption-dependent."}},"blocking_evidence":["Representative baseline measurements of out-of-validity payload loads, missing lifecycle fields, selection ambiguity, active-tier burden, and maintenance effort are absent.","Prior art and deployed conditions-data practices have not been searched or verified, so the proposal's incremental distinctiveness is unknown.","The completeness of dynamic, external, and publication-related dependency discovery is unproven.","No comparative pilot result shows that lifecycle gating outperforms the campaign-level rival without increasing reconstruction or restore failures.","Acceptable tolerances for changed selections, unresolved references, cold-tier latency, and restore fidelity have not been authorized."],"next_evidence_step":"For one detector subsystem and two completed run periods, compare the proposed per-payload lifecycle rules with the current campaign-level approval and frozen-environment rival by inventorying validity and dependencies, replaying a predeclared representative job set in shadow mode, measuring out-of-validity selections and active clutter, archiving immutable copies, and restoring a stratified sample. Falsify advancement if no baseline problem is observed, no incremental reduction occurs, dependency coverage is incomplete, or reconstruction, unresolved-reference, or restore failures exceed predeclared tolerances; do not delete originals or alter production selections.","research_questions":["How often do representative reconstruction jobs currently load payloads outside their validated conditions, and with what downstream effects?","Which lifecycle, interval-of-validity, provenance, dependency, archival, and reproducibility capabilities already exist in deployed conditions-data systems?","What contribution, if any, remains distinct from those established practices and from the named campaign-level rival?","Can all dynamic, external, frozen-environment, and publication-related dependencies be identified before tiering or quarantine?","What thresholds should govern warnings, enforcement, archival latency, unresolved references, and restore fidelity?","How much recurring calibration-owner and data-steward effort is required to prevent lifecycle metadata itself from becoming stale?","Which records, investigation, publication, or destruction obligations constrain quarantine, retention, and irreversible deletion?"],"recommendation":"PRIOR_ART_RESEARCH","uncertainty_constraints":["No external sources, prior-art search, or empirical prevalence evidence were available.","Problem frequency, scientific effect size, stakeholder demand, and realized operational savings are unknown.","Cost bands are resource-equivalent planning ranges based only on the stated scope and assumptions, not measured budgets.","Technical feasibility depends on dependency visibility and the extensibility of existing conditions and reconstruction systems.","Scalability across subsystems, institutions, and payload types is untested.","Old payloads may remain scientifically correct for their original conditions, so lifecycle status must not be interpreted as decay of scientific truth."],"closed_book_prior_art_boundary":"Prior art is unsearched and unverified. This closed-book assessment does not establish novelty, prevalence, market size, deployed adoption, empirical impact, or whether established conditions-database validity, provenance, dependency, archival, and reproducibility systems already implement the proposed lifecycle composition."}