{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp03_full320_20260801","cell_id":"layer_decay_and_expiration_management__physics","trajectory_id":"R","attempt_index":0,"archetype_slug":"layer_decay_and_expiration_management","domain_slug":"physics","decision":"CANDIDATE","problem_id":"stale_detector_calibration_payloads_remain_active","causal_lever_id":"validity_gated_calibration_lifecycle","proposal":{"problem":"Successive detector-calibration payloads remain discoverable or active after their validated run conditions have ended. Analysts can therefore apply obsolete constants to new measurements, while cleanup is avoided because historical payloads are needed to reproduce published results.","actors_substrate":["experimental physicists and analysis teams","detector calibration and operations groups","conditions database and reconstruction software","versioned calibration constants, geometry, masks, and uncertainty payloads","published and ongoing measurement datasets"],"observable_state":"Count and fraction of calibration payloads lacking explicit validity, supersession, or lifecycle state; rate of reconstruction jobs loading payloads outside validated conditions; unresolved dependents; archive-restore success; active-tier volume and lookup time.","consequence":"A stale calibration can bias reconstructed observables or invalidate uncertainty estimates; indiscriminate deletion can instead make historical analyses irreproducible.","affected_objective":"Keep current measurements tied to validated detector conditions while preserving reproducibility, lineage, and bounded operational cost.","structural_mapping":[{"archetype_element":"sequential deposits","domain_realization":"New calibration payloads are deposited for successive detector states, run ranges, and reconstruction campaigns.","claim_kind":"INFERENCE"},{"archetype_element":"changed active usefulness or validity","domain_realization":"A payload validated for one hardware configuration or run interval may be inappropriate after detector conditions change.","claim_kind":"HYPOTHESIS"},{"archetype_element":"stale layers mistaken for current truth","domain_realization":"Insufficient validity and supersession metadata can let reconstruction select an obsolete payload.","claim_kind":"HYPOTHESIS"},{"archetype_element":"retention exceptions","domain_realization":"Payloads underlying publications, investigations, or preserved datasets require reproducibility holds.","claim_kind":"INFERENCE"},{"archetype_element":"dependency-sensitive removal","domain_realization":"Historical reconstruction recipes and datasets may reference exact payload identities.","claim_kind":"INFERENCE"},{"archetype_element":"differentiated expiration","domain_realization":"Expired payloads leave active selection but may be archived, compacted, or preserved rather than destroyed.","claim_kind":"INFERENCE"}],"component_map":[{"component":"layer_inventory_and_identity_map","status":"direct","domain_realization":"Registry of uniquely identified calibration payloads and versions."},{"component":"deposition_order_and_age_index","status":"direct","domain_realization":"Creation time, run range, campaign, and version lineage."},{"component":"retention_policy_matrix","status":"adapted","domain_realization":"Rules by payload class and reproducibility obligation."},{"component":"decay_function_or_aging_rule","status":"adapted","domain_realization":"Age and detector-change increase review priority, but do not establish invalidity alone."},{"component":"expiration_trigger_definition","status":"adapted","domain_realization":"End of validity interval, supersession, detector change, or failed validation triggers removal from active selection."},{"component":"layer_value_and_risk_score","status":"adapted","domain_realization":"Ranks review using reuse, provenance, recreation cost, and misapplication impact."},{"component":"dependency_and_reconstruction_check","status":"direct","domain_realization":"Trace analyses, datasets, workflows, and publications referencing a payload."},{"component":"pruning_or_archival_pathway","status":"direct","domain_realization":"Deactivate, archive, compact, quarantine, or delete."},{"component":"preservation_exception_register","status":"direct","domain_realization":"Named reproducibility, investigation, and historical holds."},{"component":"deletion_audit_and_rollback_window","status":"direct","domain_realization":"Logged soft deletion with time-bounded restoration."},{"component":"resource_budget_and_storage_tier","status":"direct","domain_realization":"Capacity and latency budgets for active, nearline, and archive stores."},{"component":"review_cadence_and_revalidation_loop","status":"direct","domain_realization":"Scheduled owner review and restoration drills."},{"component":"legal_hold_or_compliance_override","status":"adapted","domain_realization":"Institutional, funder, investigation, or records holds override disposal."},{"component":"hot_warm_cold_access_state","status":"direct","domain_realization":"Current-production, reproducibility-nearline, and deep-archive states."},{"component":"orphan_layer_detection","status":"direct","domain_realization":"Identify payloads with no live reconstruction or evidentiary dependency."},{"component":"supersession_marker","status":"direct","domain_realization":"Marker points obsolete payload identity to its successor and blocks default selection."},{"component":"layer_compaction_candidate_flag","status":"adapted","domain_realization":"Flag small immutable payload bundles for lossless packaging without erasing identities."},{"component":"rehydration_or_restore_procedure","status":"direct","domain_realization":"Restore archived payload and reconnect it to a historical reconstruction environment."},{"component":"deletion_impact_estimate","status":"direct","domain_realization":"Estimate affected analyses, recreation difficulty, and scientific impact."},{"component":"stale_context_detector","status":"adapted","domain_realization":"Detect mismatch between payload validity metadata and current detector/run conditions."}],"mechanism_dispositions":[{"slug":"age_weighted_value_score","disposition":"considered_rejected","contribution_type":"NONE","adaptation_or_rejection":"Reject as decision authority: physical validity and dependencies are hard gates that a composite age score could obscure.","counterfactual_removal":"No material loss; rule-based validity and impact fields still prioritize review."},{"slug":"archive_restore_test","disposition":"selected_supporting","contribution_type":"TEST_DESIGN","adaptation_or_rejection":"Sample payloads across ages and formats and reproduce a bounded historical reconstruction.","counterfactual_removal":"Archival could silently become irreversible, defeating reproducibility."},{"slug":"cache_eviction_rule","disposition":"selected_supporting","contribution_type":"OPERATIONAL","adaptation_or_rejection":"Evict only from the fast replica tier; the authoritative payload remains nearline or archived.","counterfactual_removal":"Scientific validity is unchanged, but active-tier capacity and latency may become unbounded."},{"slug":"dependency_safe_delete_check","disposition":"selected_load_bearing","contribution_type":"SAFETY_GUARDRAIL","adaptation_or_rejection":"Trace exact payload references before irreversible deletion; unknown external dependencies force review.","counterfactual_removal":"Cleanup could break reconstruction and published-result auditability."},{"slug":"lifecycle_storage_tiering_policy","disposition":"selected_supporting","contribution_type":"OPERATIONAL","adaptation_or_rejection":"Demote inactive payloads while preserving immutable identity and lossless content.","counterfactual_removal":"Retention remains possible but expensive, encouraging unsafe deletion or indefinite active clutter."},{"slug":"log_rotation_and_cleanup_job","disposition":"incompatible","contribution_type":"NONE","adaptation_or_rejection":"Generation-position deletion is content-blind and unsuitable for payloads with non-monotonic scientific value.","counterfactual_removal":"No loss; calibrated validity intervals replace rotation depth."},{"slug":"retention_schedule","disposition":"selected_load_bearing","contribution_type":"CORE_CAUSAL","adaptation_or_rejection":"Map payload classes to active, archival, and disposal rules plus reproducibility holds.","counterfactual_removal":"Expiry and exceptions become ad hoc, so obsolete payloads remain active or needed ones disappear."},{"slug":"soft_delete_quarantine_window","disposition":"selected_supporting","contribution_type":"SAFETY_GUARDRAIL","adaptation_or_rejection":"Hide first, retain immutable bytes for an impact-sized grace period, then destroy only after approval.","counterfactual_removal":"Operator or automation errors become immediately irreversible."},{"slug":"stale_layer_detection_dashboard","disposition":"selected_load_bearing","contribution_type":"CORE_CAUSAL","adaptation_or_rejection":"Show ownership, validity gaps, detector-condition mismatch, dependencies, and lifecycle state.","counterfactual_removal":"Stale active payloads remain difficult to discover and prioritize."},{"slug":"time_to_live_ttl_policy","disposition":"selected_load_bearing","contribution_type":"CORE_CAUSAL","adaptation_or_rejection":"Use a renewable validation lease whose expiry disables default selection and triggers review, never automatic destruction.","counterfactual_removal":"Payloads without explicit end conditions can remain selectable indefinitely."},{"slug":"tombstone_or_deletion_marker","disposition":"selected_load_bearing","contribution_type":"SAFETY_GUARDRAIL","adaptation_or_rejection":"Retain identity, disposition reason, and successor pointer after deactivation or deletion.","counterfactual_removal":"Missing payloads become ambiguous and stale replicas or references can revive obsolete state."}],"causal_chain":["Calibration payloads accumulate across changing detector conditions.","Explicit validity leases and condition-mismatch detection identify payloads no longer justified for current reconstruction.","Supersession markers and selection gates remove those payloads from default use.","Dependency and hold checks separate reproducibility-critical payloads from true orphans.","Tiering, archival, quarantine, and audited deletion bound the active stack without silently erasing scientific lineage.","Restore drills test whether archived payloads still support historical reconstruction."],"baseline":"Teams keep most payloads indefinitely in the conditions system, rely on naming conventions and analyst judgment to choose versions, and perform occasional manual cleanup.","nearest_rival":"Maintain one approved current calibration per campaign and freeze complete analysis environments for history, without a per-payload lifecycle registry or dependency-gated archival.","authority_safety":{"affected_parties":["analysts using current calibrations","authors and readers of published measurements","detector operations and calibration teams","data stewards and institutional records owners"],"decision_authority":"Calibration owners approve validity and supersession; data stewards approve tiering; designated records or publication authorities approve irreversible deletion and holds.","authorized_first_step":"In one detector subsystem and two completed run periods, inventory payloads, label validity and dependencies, shadow-test selection warnings, archive copies, and restore a stratified sample; do not delete originals.","excluded_actions":["automatic hard deletion","changing published analysis artifacts","treating age alone as physical invalidity","overriding investigation or reproducibility holds","blocking production solely on an unvalidated staleness heuristic"],"halt_rollback":"Halt if a warning would change an unresolved production selection, dependency coverage is incomplete, or any restore fails fidelity checks; disable enforcement and restore quarantined payloads from immutable copies."}},"negative_tests":{"strongest_counterevidence":"The problem is weak if the conditions system already enforces complete run-validity intervals, immutable provenance, unique default selection, frozen reproducibility bundles, and measured absence of out-of-validity loads.","analogy_break":"Calibration versions are not uniformly decaying deposits: an old payload may remain exactly correct for its original run forever, so expiration must govern active applicability and access state rather than scientific truth or age alone.","failure_condition":"Lifecycle metadata becomes another stale layer, or deactivation occurs before all dynamic and external dependencies are visible.","problem_falsifier":"Across representative reconstruction jobs, no payload is selectable outside its validated conditions, every payload has explicit lifecycle and successor state, and accumulated active versions cause no measurable ambiguity, cost, or maintenance burden.","intervention_falsifier":"In the bounded pilot, lifecycle gating does not reduce out-of-validity selections or active clutter relative to the rival, or it increases reconstruction failures, unresolved references, or archive-restore failures beyond the predeclared tolerance.","risks":["False staleness flags could suppress a valid calibration.","Hidden dependencies could make archival or deletion break reproducibility.","Validity metadata may encode mistaken detector assumptions.","Cold-tier latency could delay urgent reanalysis.","Quarantine may conflict with a binding destruction requirement."]},"null_rationale":null,"classification":{"candidate_kind":"MECHANISM_COMPOSITION","prior_art_status":"UNSEARCHED","evidence_maturity":"HYPOTHESIS"},"revision_change_log":{"revision_kind":"ORIGINAL","prior_problem_id":null,"prior_causal_lever_id":null,"problem_changed":false,"causal_lever_changed":false,"conceptual_changes":[],"operational_changes":[],"repairs_addressed":[]},"confidence":0.84,"generator_notes":"Closed-book structural transfer. Domain-specific prevalence and effect sizes are hypotheses; no prior-art or empirical search was performed."}