{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp03_full320_20260801","cell_id":"layer_decay_and_expiration_management__robotics_automation","trajectory_id":"R","attempt_index":0,"archetype_slug":"layer_decay_and_expiration_management","domain_slug":"robotics_automation","decision":"CANDIDATE","problem_id":"stale_robot_world_model_layer_accumulation","causal_lever_id":"dependency_gated_world_model_lifecycle","proposal":{"problem":"HYPOTHESIS: A long-running robot fleet accumulates mission-specific maps, submaps, semantic annotations, calibration-derived overlays, and learned cost layers. Superseded layers remain selectable as if current, increasing localization or planning errors and maintenance burden; indiscriminate deletion can destroy incident reconstruction, rollback, or relocalization evidence.","actors_substrate":["mobile robots and autonomy software","fleet operations and safety engineers","map and artifact registry","mission-derived spatial layers","incident investigators and affected site personnel"],"observable_state":"Layer count and storage grow across missions; multiple layers cover the same place without explicit current, superseded, archived, held, or deleted states; robots or operators can retrieve stale layers; lineage and restore tests are incomplete.","consequence":"Robots may plan or localize against obsolete geometry or semantics, while operators postpone cleanup because dependencies and reconstruction value are unknown.","affected_objective":"Maintain bounded, interpretable world-model storage while preserving safe operation, rollback, incident reconstruction, and accountable deletion.","structural_mapping":[{"archetype_element":"sequential deposits","domain_realization":"Mission runs deposit timestamped submaps, semantic overlays, calibration products, and cost layers.","claim_kind":"HYPOTHESIS"},{"archetype_element":"stale layers remain active","domain_realization":"Superseded spatial artifacts remain discoverable and may be loaded as current robot context.","claim_kind":"HYPOTHESIS"},{"archetype_element":"retention versus deletion tension","domain_realization":"Removing obsolete maps reduces ambiguity and cost but may break localization lineage, rollback, or incident reconstruction.","claim_kind":"INFERENCE"},{"archetype_element":"managed lifecycle","domain_realization":"Each artifact receives lifecycle state, validity evidence, dependency gates, exception holds, tiered archival, and audited removal.","claim_kind":"INFERENCE"}],"component_map":[{"component":"layer_inventory_and_identity_map","status":"direct","domain_realization":"Registry keyed by artifact ID, site, spatial extent, mission, robot, and lineage."},{"component":"deposition_order_and_age_index","status":"direct","domain_realization":"Creation time, observation interval, and supersession sequence per site."},{"component":"retention_policy_matrix","status":"adapted","domain_realization":"Artifact class and safety purpose determine minimum evidence retention and maximum active duration."},{"component":"decay_function_or_aging_rule","status":"adapted","domain_realization":"Confidence decays using elapsed time plus detected environmental and calibration change, not age alone."},{"component":"expiration_trigger_definition","status":"direct","domain_realization":"Change, failed validation, supersession, or review deadline triggers demotion review."},{"component":"layer_value_and_risk_score","status":"adapted","domain_realization":"Ranks candidates using reuse, uniqueness, reconstruction value, staleness evidence, and storage cost."},{"component":"dependency_and_reconstruction_check","status":"direct","domain_realization":"Trace active missions, localization references, derived products, and incident bundles before deletion."},{"component":"pruning_or_archival_pathway","status":"direct","domain_realization":"Refresh, supersede, compact, archive, quarantine, or destroy."},{"component":"preservation_exception_register","status":"direct","domain_realization":"Named holds for incidents, validation benchmarks, rare environments, and safety evidence."},{"component":"deletion_audit_and_rollback_window","status":"direct","domain_realization":"Signed disposition record plus recoverable quarantine before destruction."},{"component":"resource_budget_and_storage_tier","status":"direct","domain_realization":"Budgets for onboard, edge, central, and deep-archive storage."},{"component":"review_cadence_and_revalidation_loop","status":"direct","domain_realization":"Periodic validation and sampled restoration, with review after site or software changes."},{"component":"legal_hold_or_compliance_override","status":"adapted","domain_realization":"Investigation, contractual, regulatory, or litigation hold blocks disposal."},{"component":"hot_warm_cold_access_state","status":"direct","domain_realization":"Operational, nearline, offline, and deep-archive states with explicit retrieval latency."},{"component":"orphan_layer_detection","status":"direct","domain_realization":"Artifact is deletion-eligible only when no live or reconstruction dependency remains."},{"component":"supersession_marker","status":"direct","domain_realization":"Old artifact points to its validated successor and is excluded from default selection."},{"component":"layer_compaction_candidate_flag","status":"adapted","domain_realization":"Flag overlapping submaps or redundant observations for loss-bounded consolidation."},{"component":"rehydration_or_restore_procedure","status":"direct","domain_realization":"Retrieve, decode, validate frame metadata, and reconnect archived artifacts in a sandbox."},{"component":"deletion_impact_estimate","status":"direct","domain_realization":"Estimate robots, missions, investigations, and derived artifacts affected by loss."},{"component":"stale_context_detector","status":"adapted","domain_realization":"Compare stored geometry, semantics, calibration frame, and validation results with current observations."}],"mechanism_dispositions":[{"slug":"age_weighted_value_score","disposition":"selected_supporting","contribution_type":"OPERATIONAL","adaptation_or_rejection":"Use change-sensitive confidence and safety vetoes; age only ranks review priority.","counterfactual_removal":"Cleanup remains possible but triage becomes slower and less repeatable."},{"slug":"archive_restore_test","disposition":"selected_load_bearing","contribution_type":"SAFETY_GUARDRAIL","adaptation_or_rejection":"Exercise real decoding, coordinate-frame validation, and lineage reconnection across artifact age bands.","counterfactual_removal":"Archival could silently eliminate usable rollback and reconstruction, hard-gating safe cleanup."},{"slug":"cache_eviction_rule","disposition":"considered_rejected","contribution_type":"NONE","adaptation_or_rejection":"Recency-based eviction cannot establish spatial validity or safe deletion; onboard caching is a separate performance problem.","counterfactual_removal":"The lifecycle causal chain is unchanged."},{"slug":"dependency_safe_delete_check","disposition":"selected_load_bearing","contribution_type":"SAFETY_GUARDRAIL","adaptation_or_rejection":"Trace runtime, derived-artifact, rollback, and investigation dependencies; incomplete visibility blocks destruction.","counterfactual_removal":"Deletion can break active autonomy or erase reconstruction evidence."},{"slug":"lifecycle_storage_tiering_policy","disposition":"selected_load_bearing","contribution_type":"CORE_CAUSAL","adaptation_or_rejection":"Demote validated inactive layers from operational stores while retaining recoverability.","counterfactual_removal":"The system again faces a binary keep-active-or-delete choice, undermining bounded safe retention."},{"slug":"log_rotation_and_cleanup_job","disposition":"considered_rejected","contribution_type":"NONE","adaptation_or_rejection":"Generation-blind rotation may purge uniquely valuable maps and treats structured artifacts as an append-only log.","counterfactual_removal":"No material loss; archival workflows execute class-aware dispositions."},{"slug":"retention_schedule","disposition":"selected_supporting","contribution_type":"OPERATIONAL","adaptation_or_rejection":"Map artifact classes to evidence obligations, review periods, and named holds; it does not itself authorize deletion.","counterfactual_removal":"Exceptions and review deadlines become inconsistent, though dependency gating still protects immediate safety."},{"slug":"soft_delete_quarantine_window","disposition":"selected_load_bearing","contribution_type":"SAFETY_GUARDRAIL","adaptation_or_rejection":"Hide artifacts from production selection while preserving a risk-sized recovery window.","counterfactual_removal":"Automated cleanup becomes irreversibly hazardous and likely unacceptable to safety authority."},{"slug":"stale_layer_detection_dashboard","disposition":"selected_load_bearing","contribution_type":"CORE_CAUSAL","adaptation_or_rejection":"Inventory spatial artifacts and surface semantic, geometric, frame, and validation mismatch.","counterfactual_removal":"Stale active layers remain unidentified, so the proposed lever cannot target the diagnosed problem."},{"slug":"time_to_live_ttl_policy","disposition":"considered_rejected","contribution_type":"NONE","adaptation_or_rejection":"Fixed self-expiry is unsafe because stable sites may retain value while rapidly changed sites become stale early; deadlines may trigger review only.","counterfactual_removal":"Change-sensitive expiration and scheduled review remain sufficient."},{"slug":"tombstone_or_deletion_marker","disposition":"selected_load_bearing","contribution_type":"CORE_CAUSAL","adaptation_or_rejection":"Preserve artifact identity, deletion reason, propagation state, and validated successor reference.","counterfactual_removal":"Deleted maps can ambiguously reappear from replicas or leave unresolved lineage."}],"causal_chain":["Inventory and identity resolution expose accumulated artifacts and competing versions.","Change-sensitive validation flags layers that may no longer represent the operating site.","Policy, value, holds, and dependency checks choose refresh, supersession, archival, quarantine, or blocked status.","Supersession markers remove stale layers from default robot selection without erasing lineage.","Tiering and compaction bound active storage while restore tests preserve usable historical evidence.","Two-phase deletion and tombstones make eligible removal reversible, auditable, and propagation-safe.","Periodic revalidation prevents exceptions, archives, and thresholds from silently becoming invalid."],"baseline":"Operators retain most world-model artifacts in shared or robot-local stores, manually rename preferred versions, and delete only during storage pressure or incidents.","nearest_rival":"Keep all artifacts but improve version selection by always loading the newest validated layer; this reduces stale use but does not bound retention, verify recoverability, or govern deletion dependencies.","authority_safety":{"affected_parties":["robot operators","maintenance and safety staff","workers and bystanders near robots","customers or site owners","incident investigators"],"decision_authority":"Fleet safety owner authorizes production exclusion; data steward authorizes archival or destruction; investigation or compliance owner controls holds.","authorized_first_step":"Run a 30-day read-only pilot at one site: inventory layers, replay historical selection decisions, flag stale and orphan candidates, and restore a stratified archive sample; no production selection or deletion changes.","excluded_actions":["automatic hard deletion","loading unvalidated restored maps into production","overriding incident or compliance holds","treating age score as proof of invalidity","lossy compaction without task-specific fidelity checks"],"halt_rollback":"Halt if the detector would exclude a layer needed by a validated mission, dependency coverage is incomplete, restore fidelity fails, or false-positive stale flags exceed the predeclared bound; revert registry labels and retain all bytes."}},"negative_tests":{"strongest_counterevidence":"Fleet artifacts may already be immutable, content-addressed, lineage-complete, automatically excluded after validation failure, and cheap enough to retain; then accumulation is not causing selection, safety, or material maintenance harm.","analogy_break":"Spatial maps can remain correct for years or become wrong immediately after a site change, so ordinary age decay is a weak proxy; the mapping fails if change and task-validity evidence cannot govern lifecycle state.","failure_condition":"The proposal fails if artifact identity or runtime references cannot be resolved well enough to distinguish superseded, dependent, and orphan layers without disrupting operations.","problem_falsifier":"Reject the diagnosed problem if audit and replay show stale or superseded layers are never eligible for operational selection and accumulated artifacts cause no meaningful storage, search, maintenance, or governance burden.","intervention_falsifier":"Reject the intervention if, versus newest-validated-only selection, the pilot does not improve stale-layer detection or active-store boundedness, or if it cannot meet predeclared dependency recall and archive-restore fidelity thresholds.","risks":["False stale flags can remove useful environmental coverage from default selection.","Incomplete dependency graphs can permit unsafe deletion.","Cold-tier retrieval may be too slow during incident response.","Compaction may erase rare geometry or provenance.","Quarantine may conflict with mandatory destruction deadlines.","Lifecycle metadata and tombstones may themselves accumulate."]},"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.82,"generator_notes":"Closed-book structural transfer. Domain-specific prevalence and performance claims are hypotheses; no prior-art search was performed."}