{"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":"Test whether explicit validity, supersession, dependency, archival, and restoration controls can reduce obsolete calibration selection and active-tier clutter without compromising historical reproducibility. The candidate is technically coherent and safely testable, but problem prevalence, incremental benefit, and distinctiveness from established conditions-data practices are unverified.","adopter_authorizer":"Detector calibration and operations groups would adopt the workflow; calibration owners authorize validity and supersession, data stewards authorize tiering, and designated records or publication authorities control holds and irreversible deletion.","scores":{"meaningful_impact":{"score":4,"rationale":"If obsolete constants are loaded, reconstructed observables or uncertainty estimates can be biased, while improper deletion can impair published-result reproduction. The consequences are scientifically important, although their frequency and realized magnitude are unsupported."},"stakeholder_pull":{"score":3,"rationale":"Analysts, calibration groups, data stewards, and publication authorities have identifiable interests in validated selection and reproducibility, but the packet supplies no evidence of experienced demand, incident frequency, or willingness to change workflows."},"incremental_advantage":{"score":3,"rationale":"Relative to one approved calibration per campaign plus frozen historical environments, the proposal adds per-payload lifecycle state, dependency-gated archival, warnings, and restore drills. Whether that composition materially improves selection errors, clutter, or cost is explicitly untested."},"distinctiveness_plausibility":{"score":2,"rationale":"The integrated composition could contain a useful contribution, but prior art is unsearched and the packet itself identifies likely overlap with validity intervals, provenance, conditions databases, and reproducibility practices. Distinctiveness therefore has weak closed-book support."},"technical_implementability":{"score":4,"rationale":"The mechanisms operate on identifiable payload metadata, selection logic, dependency records, storage tiers, and reconstruction tests. Hidden or dynamic dependencies and inaccurate validity metadata are material difficulties, but the proposed shadow-mode implementation is technically bounded."},"adoption_authority_feasibility":{"score":4,"rationale":"The candidate allocates decisions among calibration owners, data stewards, and records or publication authorities and excludes automatic deletion or changes to published artifacts. Multi-party coordination remains necessary, especially for holds and eventual deletion."},"evidence_readiness":{"score":4,"rationale":"The packet specifies observable measures, separate problem and intervention falsifiers, a rival workflow, one subsystem and two completed periods, shadow warnings, archived copies, and sampled restore tests. Predeclared tolerances and sampling details remain to be established."},"safety_net_benefit":{"score":5,"rationale":"Immutable copies, quarantine, dependency and hold checks, non-destructive shadow testing, restore drills, explicit halt conditions, and rollback directly protect against suppressing valid calibrations or losing reproducibility."},"scalability":{"score":3,"rationale":"A registry and selection gates could extend across payload types and run periods, but subsystem-specific validity semantics, external dependencies, authority differences, metadata upkeep, and cold-tier latency may limit economical scaling."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Inventory one detector subsystem across two completed run periods, label validity and dependencies, execute shadow comparisons against the approved-current-plus-frozen-environment rival, archive copies, and restore a stratified sample without deleting originals.","confidence":"LOW","assumptions":["Existing payload, job, and storage records are accessible.","The work requires specialized calibration, software, data-stewardship, and evaluation labor.","No major new hardware or production enforcement is included.","Payload volume and dependency complexity are not supplied."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Implement and validate lifecycle metadata, selection warnings or gates, supersession handling, dependency and hold checks, immutable archival, audit records, rollback procedures, and operator documentation for an initial detector scope.","confidence":"LOW","assumptions":["The existing conditions database and reconstruction software can be extended rather than replaced.","Security, records, and collaboration approvals are required but no novel regulatory regime is assumed.","Historical metadata requires partial manual reconciliation.","Irreversible deletion remains outside initial deployment."]},"operational_launch":{"band_2026_usd":"1M_TO_5M","scope":"Launch across a multi-subsystem experimental program, including metadata migration, integration testing, archive capacity, restore drills, training, governance, monitoring, and staged enforcement.","confidence":"LOW","assumptions":["Subsystems have heterogeneous validity and dependency rules.","Production reconstruction requires extensive regression testing and coordination.","Existing storage and workflow platforms remain usable.","The packet does not establish experiment size or historical payload volume."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Maintain lifecycle metadata and selection logic, review exceptions and holds, operate archival tiers, monitor loads, conduct restore drills, support users, and audit governance decisions.","confidence":"LOW","assumptions":["Recurring work spans software, calibration, stewardship, storage, and evaluation labor.","Archive growth and urgent reanalysis remain within existing infrastructure capacity.","No cost savings from reduced active-tier volume are credited because they are unmeasured."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"YES","reason":"The candidate defines observable out-of-validity loads, missing lifecycle states, unresolved dependencies, restore success, active-tier volume, and lookup time, allowing the alleged problem to be tested even though its prevalence is unknown."},"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 powers."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal claims that per-payload lifecycle gating and dependency-aware archival outperform the approved-current-plus-frozen-environment rival on invalid selection and active clutter without increasing reconstruction, reference, or restore failures."},"bounded_next_evidence_step":{"status":"YES","reason":"The authorized first step is limited to one subsystem and two completed periods, uses shadow warnings and archived copies, tests restores, and prohibits deletion or production blocking."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The first step is non-destructive, respects investigation and reproducibility holds, assigns authority, and halts on unresolved production-selection changes, incomplete dependency coverage, or restore-fidelity failure."},"implementation_cost_scope_and_range":{"status":"YES","reason":"A staged scope can be bounded around inventory, metadata, shadow selection, archival, restore testing, and later integration; broad resource bands can be assigned, although confidence is low because scale and system complexity are undisclosed."}},"blocking_evidence":["No evidence establishes how often payloads lack explicit validity, supersession, or lifecycle state.","No representative-job measurement establishes whether out-of-validity payloads are currently selectable or loaded.","No comparison establishes improvement over approved-current calibrations plus frozen historical environments.","Dependency completeness, including dynamic and external references, is unknown.","Archive restoration fidelity and acceptable failure tolerances have not been demonstrated.","Prior art and deployed conditions-data practices are unsearched, leaving the incremental contribution unestablished.","Adopter demand, governance acceptance, and recurring metadata-maintenance burden are unsupported."],"next_evidence_step":"In one detector subsystem and two completed run periods, compare the proposed lifecycle registry and shadow selection warnings with the approved-current-plus-frozen-environment rival across representative reconstruction jobs. Measure out-of-validity selections, ambiguous defaults, active payload count, unresolved dependencies, reconstruction failures, and stratified archive-restore fidelity; falsify advancement if gating produces no reduction in invalid selection or clutter, or exceeds predeclared tolerances for broken references, reconstruction failures, or restore failures. Do not delete originals or block production.","research_questions":["Do representative reconstruction jobs currently select or permit payloads outside validated run conditions?","How complete are existing validity intervals, provenance, successor states, unique-default rules, and frozen reproducibility bundles?","Which elements of the proposed integrated lifecycle composition, if any, are absent from deployed conditions-data systems?","Can dynamic and external dependencies be identified with sufficient coverage before tiering or quarantine?","What reduction in invalid selection or active clutter occurs relative to the nearest rival?","What reconstruction, reference-resolution, restore-fidelity, and latency tolerances should govern advancement?","Who will maintain validity and lifecycle metadata, and how will stale metadata be detected?","Do calibration owners, data stewards, and records or publication authorities accept the proposed division of authority?","What recurring labor, storage, coordination, and audit burden arises at multi-subsystem scale?"],"recommendation":"PRIOR_ART_RESEARCH","uncertainty_constraints":["Closed-book assessment provides no external evidence of prevalence, demand, realized impact, or market size.","Prior-art status is explicitly unsearched, and likely overlap with existing validity and provenance mechanisms cannot be resolved internally.","Cost bands are resource-equivalent planning ranges, not estimates derived from disclosed payload volume, staffing, or infrastructure.","Impact scoring reflects the severity of the specified failure modes, not their measured frequency.","Technical feasibility depends on dependency visibility and metadata accuracy that the packet does not demonstrate.","Scalability across detector subsystems and collaborations is untested."],"closed_book_prior_art_boundary":"No claim is made that validity intervals, supersession state, dependency-aware archival, restore drills, or their composition are novel or uncommon. The sealed packet supports only structural plausibility and a bounded test design; external research is required to establish existing implementations, deployment prevalence, distinctiveness, empirical benefit, and realized cost."}