{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp03_full320_20260801","cell_id":"layer_decay_and_expiration_management__public_administration_policy","trajectory_id":"R","attempt_index":0,"archetype_slug":"layer_decay_and_expiration_management","domain_slug":"public_administration_policy","decision":"CANDIDATE","problem_id":"obsolete_administrative_policy_stack","causal_lever_id":"authoritative_policy_lifecycle_and_supersession_gate","proposal":{"problem":"Agencies accumulate directives, guidance, forms, waivers, procedures, and implementing rules that remain discoverable or operational after their authority, factual assumptions, or usefulness has changed. Staff and the public may follow obsolete or conflicting instructions because retirement, supersession, dependency, preservation, and archival states are not explicit.","actors_substrate":["agency policy owners and records officers","frontline public employees","regulated or service-seeking members of the public","oversight, legal, audit, and archival functions","administrative instruments and their references, versions, and repositories"],"observable_state":"Repositories and workflows contain multiple dated instruments on the same subject without reliable current, superseded, archived, held, or withdrawn status; obsolete instruments still appear in searches, forms, training, or operational references.","consequence":"Implementation becomes inconsistent, staff apply outdated requirements, the public receives conflicting instructions, and cleanup is avoided or performed without preserving legal and historical accountability.","affected_objective":"Keep administrative implementation current, consistent, searchable, lawful, and reconstructable while bounding policy sprawl.","structural_mapping":[{"archetype_element":"sequential deposits","domain_realization":"successive directives, manuals, forms, waivers, guidance, and implementing procedures","claim_kind":"INFERENCE"},{"archetype_element":"stale layers masquerading as current","domain_realization":"obsolete instruments remain searchable or embedded in workflows without authoritative status labels","claim_kind":"HYPOTHESIS"},{"archetype_element":"retention versus removal tension","domain_realization":"retiring operational authority must not erase audit, legal, evidentiary, or historical records","claim_kind":"INFERENCE"},{"archetype_element":"lifecycle governance layer","domain_realization":"a governed registry assigns active, review, superseded, archived, held, quarantined, or destroyed states","claim_kind":"HYPOTHESIS"}],"component_map":[{"component":"layer_inventory_and_identity_map","status":"direct","domain_realization":"canonical registry of instruments, versions, owners, subjects, and identifiers"},{"component":"deposition_order_and_age_index","status":"direct","domain_realization":"issuance and effective-date chronology for each policy family"},{"component":"retention_policy_matrix","status":"direct","domain_realization":"instrument-class rules for operational retention, archival retention, and disposition"},{"component":"decay_function_or_aging_rule","status":"adapted","domain_realization":"age raises review priority but never alone terminates authority"},{"component":"expiration_trigger_definition","status":"adapted","domain_realization":"review triggers based on elapsed time, legal change, factual change, owner departure, or successor issuance"},{"component":"layer_value_and_risk_score","status":"adapted","domain_realization":"rank by public reliance, legal force, use, conflict risk, and reconstruction value"},{"component":"dependency_and_reconstruction_check","status":"direct","domain_realization":"trace citations, forms, training, systems, delegated authorities, and audit paths before retirement"},{"component":"pruning_or_archival_pathway","status":"direct","domain_realization":"refresh, consolidate, supersede, withdraw, archive, or lawfully destroy"},{"component":"preservation_exception_register","status":"direct","domain_realization":"named historical, evidentiary, safety, and continuing-reliance exceptions"},{"component":"deletion_audit_and_rollback_window","status":"direct","domain_realization":"logged withdrawal with a time-bounded recoverable quarantine"},{"component":"resource_budget_and_storage_tier","status":"adapted","domain_realization":"staff-review budget plus active, reference, and archival repository tiers"},{"component":"review_cadence_and_revalidation_loop","status":"direct","domain_realization":"periodic owner attestation and event-triggered revalidation"},{"component":"legal_hold_or_compliance_override","status":"direct","domain_realization":"litigation, investigation, records-law, and archival holds block destruction"},{"component":"hot_warm_cold_access_state","status":"adapted","domain_realization":"current authoritative, retained reference, and restricted archival visibility states"},{"component":"orphan_layer_detection","status":"adapted","domain_realization":"identify instruments with no live citations, workflow use, public reliance, or reconstruction dependency"},{"component":"supersession_marker","status":"direct","domain_realization":"durable withdrawn or superseded notice pointing to the controlling successor"},{"component":"layer_compaction_candidate_flag","status":"adapted","domain_realization":"flag overlapping instruments for consolidation into one authoritative instrument"},{"component":"rehydration_or_restore_procedure","status":"direct","domain_realization":"documented retrieval of archived text, metadata, attachments, and citation relationships"},{"component":"deletion_impact_estimate","status":"adapted","domain_realization":"estimate affected programs, staff, public users, rights, obligations, and recovery cost"},{"component":"stale_context_detector","status":"adapted","domain_realization":"detect conflicts with current law, organization, systems, facts, forms, or successor policy"}],"mechanism_dispositions":[{"slug":"age_weighted_value_score","disposition":"selected_supporting","contribution_type":"OPERATIONAL","adaptation_or_rejection":"Use only to prioritize human review; legal force and reliance are veto factors.","counterfactual_removal":"Triage becomes slower but the lifecycle remains viable."},{"slug":"archive_restore_test","disposition":"selected_supporting","contribution_type":"TEST_DESIGN","adaptation_or_rejection":"Sample archived instruments and prove readable retrieval with metadata and links.","counterfactual_removal":"Archival recoverability becomes an untested assumption."},{"slug":"cache_eviction_rule","disposition":"considered_rejected","contribution_type":"NONE","adaptation_or_rejection":"Capacity-driven recency eviction cannot govern public-policy authority or retention.","counterfactual_removal":"No material change; registry capacity is not the causal problem."},{"slug":"dependency_safe_delete_check","disposition":"selected_load_bearing","contribution_type":"SAFETY_GUARDRAIL","adaptation_or_rejection":"Retirement or destruction is blocked until live legal, workflow, reliance, and audit dependencies are resolved.","counterfactual_removal":"Cleanup could break implementation or accountability, hard-gating viability."},{"slug":"lifecycle_storage_tiering_policy","disposition":"selected_supporting","contribution_type":"OPERATIONAL","adaptation_or_rejection":"Translate storage tiers into authoritative-active, reference-only, and archival access states.","counterfactual_removal":"Status can still work, but search clutter and archival cost remain higher."},{"slug":"log_rotation_and_cleanup_job","disposition":"incompatible","contribution_type":"NONE","adaptation_or_rejection":"Blind generational rotation ignores instrument-specific authority and dependencies.","counterfactual_removal":"No change because administrative instruments are not a uniform append-only stream."},{"slug":"retention_schedule","disposition":"selected_load_bearing","contribution_type":"CORE_CAUSAL","adaptation_or_rejection":"Assign instrument classes review, archival, destruction, exception, and hold rules with accountable owners.","counterfactual_removal":"Disposition reverts to ad hoc choices without legitimate, repeatable authority."},{"slug":"soft_delete_quarantine_window","disposition":"selected_load_bearing","contribution_type":"SAFETY_GUARDRAIL","adaptation_or_rejection":"Withdraw from normal use before destruction and preserve logged restoration for a bounded period.","counterfactual_removal":"Mistaken cleanup becomes prematurely irreversible."},{"slug":"stale_layer_detection_dashboard","disposition":"selected_load_bearing","contribution_type":"CORE_CAUSAL","adaptation_or_rejection":"Expose a canonical inventory and evidence-based stale or conflicting candidates.","counterfactual_removal":"Obsolete instruments remain invisible and cannot be systematically reviewed."},{"slug":"time_to_live_ttl_policy","disposition":"considered_rejected","contribution_type":"NONE","adaptation_or_rejection":"Fixed self-executing expiry is unsafe; use expiry dates only as mandatory review triggers.","counterfactual_removal":"No loss because event- and review-based triggers supply safer aging discipline."},{"slug":"tombstone_or_deletion_marker","disposition":"selected_load_bearing","contribution_type":"CORE_CAUSAL","adaptation_or_rejection":"Leave a durable supersession or withdrawal marker at the old identifier with successor and reason.","counterfactual_removal":"Absence stays ambiguous and obsolete copies may continue competing for authority."}],"causal_chain":["Inventory instruments and resolve versions and owners.","Detect stale, conflicting, unowned, or superseded candidates and prioritize review.","Apply class rules, holds, exceptions, value, and dependency checks.","Authorized owners refresh, consolidate, supersede, archive, quarantine, or destroy.","Durable markers redirect users while audits and restore tests preserve accountability.","Obsolete instruments lose operational authority and visibility without erasing required memory."],"baseline":"Periodic manual cleanup by individual program offices, with inconsistent naming, retention rules, status labels, and follow-through.","nearest_rival":"A one-time policy-consolidation project that rewrites overlapping instruments but does not install continuing lifecycle states, triggers, holds, and retirement controls.","authority_safety":{"affected_parties":["frontline staff","policy owners","people receiving public services","regulated parties","records, legal, audit, and archival personnel"],"decision_authority":"The legally designated policy owner may change operational status; records, legal, privacy, and archival authorities must approve destruction or applicable overrides.","authorized_first_step":"In one program, inventory one bounded policy family, label status without deleting anything, and review a stratified sample of 30 instruments for conflicts, dependencies, holds, and user search errors.","excluded_actions":["automatic termination of legal authority from age or score alone","destruction while a hold or unresolved dependency exists","concealing withdrawn instruments without a redirect marker","changing substantive rights or duties through repository metadata"],"halt_rollback":"Halt if status labels conflict with governing law, a relied-upon instrument is hidden, unresolved dependencies appear, or affected users cannot identify current guidance; restore prior visibility and labels from the audit log."}},"negative_tests":{"strongest_counterevidence":"Existing records schedules may already govern preservation and destruction, while the observed confusion may arise from poor drafting, training, search ranking, or decentralized authority rather than lifecycle absence.","analogy_break":"Administrative instruments are normative acts that can affect rights and duties, not inert storage objects; age, access frequency, and capacity cannot by themselves revoke authority or justify destruction.","failure_condition":"The pilot cannot reliably identify controlling authority, owners, dependencies, or preservation obligations, making lifecycle labels less trustworthy than the existing repositories.","problem_falsifier":"A representative inventory shows obsolete or conflicting instruments are rare, clearly labeled, absent from live workflows and public search, and not materially associated with implementation errors or maintenance burden.","intervention_falsifier":"Despite accurate inventory and lawful status changes, the pilot does not improve users' identification of controlling guidance or reduce stale-instrument use relative to the baseline.","risks":["incorrectly retiring guidance still relied upon by the public","metadata labels being mistaken for lawful revocation","legal or historical records destroyed prematurely","central registry becoming another stale layer","scoring bias concentrating review on easy rather than consequential items","archival access delays impairing oversight or due process"]},"null_rationale":null,"classification":{"candidate_kind":"DOMAIN_TRANSFER","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 inference from the supplied packet; domain prevalence and intervention effects remain unverified."}