{"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__sociology_anthropology","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"sociology_anthropology","title":"Lifecycle governance for sedimented institutional rules","opportunity_summary":"Test a reversible governance process that inventories overlapping rules, identifies conflicts and dependencies, subjects proposed status changes to affected-party review, separates superseded material from current guidance, and preserves reconstructable archives. The proposed advantage over complaint-driven cleanup or one-time consolidation is continuing review with dependency, reliance, hold, contestation, and restoration safeguards; its prevalence, effects, distinctiveness, and demand remain unverified.","adopter_authorizer":"A consenting organizational unit could adopt the process, while the institution's duly constituted governing or policy body authorizes rule-status changes and records or legal officers control applicable holds.","scores":{"meaningful_impact":{"score":4,"rationale":"If the specified sedimentation occurs, reducing contradictory guidance and unequal treatment while preserving protections and accountability would materially improve institutional governance. The sealed candidate does not establish how often or severely the problem occurs."},"stakeholder_pull":{"score":2,"rationale":"The baseline describes complaint-driven cleanup and unclear removal authority, suggesting a possible need, but provides no adopter commitment, stakeholder request, budget, or evidence that affected groups prioritize this intervention."},"incremental_advantage":{"score":4,"rationale":"Relative to the named one-time consolidation rival, the proposal adds continuing review, dependency gates, affected-party contestation, reversible withdrawal, tombstones, and restoration testing. Whether these features improve decisions or merely add process burden is untested."},"distinctiveness_plausibility":{"score":3,"rationale":"The combined lifecycle, reliance, contestation, and reconstructability mechanism is coherent and potentially distinguishable from the stated rival, but prior-art status is explicitly unsearched across policy review, records governance, and administrative simplification."},"technical_implementability":{"score":4,"rationale":"A 30-rule inventory, labeling exercise, dependency map, simulated tiering, and archive-restoration test can be performed with ordinary governance and records capabilities. Implementation becomes difficult where identity, ownership, dependencies, or disposition authority cannot be established."},"adoption_authority_feasibility":{"score":3,"rationale":"The proposal identifies governing, policy, legal, and records roles and requires a consenting unit, but actual authorization is absent and contested rule classifications may require coordination across multiple authorities and affected constituencies."},"evidence_readiness":{"score":4,"rationale":"The candidate supplies a bounded 90-day setting, problem and intervention falsifiers, a baseline, exclusions, and observable outcomes. Coding rules, observation windows, comparison design, and acceptable reliance-harm thresholds still require predefinition."},"safety_net_benefit":{"score":4,"rationale":"Quarantine, tombstones, holds, contest channels, restoration checks, halt conditions, and rollback directly reduce the danger of erasing rights, evidence, or institutional memory. Practical archive inaccessibility and politically biased classification remain possible."},"scalability":{"score":3,"rationale":"A common register and class-based lifecycle process could extend across units, but review workload, local pluralism, sensitive records, cross-unit dependencies, and the risk of creating another neglected governance layer make scale uncertain."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"A bounded 90-day study in one consenting unit covering 30 overlapping rules, including inventory, baseline decision review, affected-party sessions, simulated tiering, archive-restoration testing, measurement design, and analysis without destruction.","confidence":"MODERATE","assumptions":["Existing rule and decision records are accessible without major digitization.","Policy, records, legal, frontline, affected-party, and evaluation labor is included as resource-equivalent cost.","The study uses existing software or lightweight register tooling.","No litigation, major records remediation, or live service redesign is required."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Establish the lifecycle-governance capability for an organization, including rule-register design, classification standards, dependency mapping, authority workflows, archive controls, contest procedures, training, and initial migration.","confidence":"LOW","assumptions":["The organization has multiple units but not an exceptionally large or fragmented rule estate.","Substantial legal, records, policy, technical, and stakeholder-coordination labor is required.","Existing identity, access, and archive systems can be adapted rather than replaced.","The sealed candidate provides no organizational scale or data-quality information."]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Launch governed review across participating units, including staged rule processing, notices, review panels, quality assurance, rollback readiness, service monitoring, and evaluation.","confidence":"LOW","assumptions":["Launch is staged and excludes irreversible bulk destruction.","Contested and dependency-uncertain items receive manual review.","Existing archival infrastructure is usable.","Costs could rise materially if rule ownership and dependencies are broadly undocumented."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Maintain the register, periodic reviews, affected-party notice and contestation, legal and records holds, archive accessibility, restoration tests, training, audit, and outcome monitoring.","confidence":"LOW","assumptions":["Lifecycle governance becomes a continuing organizational function rather than a one-time project.","Review volume and contest rates remain manageable.","Recurring cost includes multidisciplinary staff time and system maintenance.","No prevalence, throughput, or organization-size evidence is supplied."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"YES","reason":"The proposal identifies auditable indicators in a rule register and current decisions, including overlaps, obsolete assumptions, unknown owners, unresolved references, undated exceptions, and continued citation; this makes the local problem externally testable without assuming prevalence."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"A consenting organizational unit is the potential adopter, the duly constituted governing or policy body authorizes status changes, and records and legal officers control holds."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal claims that continuing lifecycle review with dependency gates, reversible tiering, contestation, and reconstructable archives will outperform complaint-driven cleanup or one-time consolidation on obsolete-rule citation, consistency, and reliance harms."},"bounded_next_evidence_step":{"status":"YES","reason":"The candidate specifies a 90-day, 30-rule, inventory-and-simulation study with no destruction, restoration testing, explicit falsifiers, and reversible status handling."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"For the bounded first step, consent, constituted decision authority, records and legal holds, affected-party contestation, prohibited actions, halt conditions, and rollback are specified. Actual partner approval remains necessary but no inherently unsafe action is required."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"The activities and responsible functions can be scoped, but organization size, record quality, dependency complexity, contest volume, tooling needs, and existing archive capability are absent, so deployment and recurring ranges have low confidence."}},"blocking_evidence":["A local audit has not established that overlapping or context-stale rules are common enough to justify intervention.","There is no evidence that sedimented rules, rather than discretion, resource scarcity, or unequal enforcement, materially drive inconsistent decisions.","The proposal has not demonstrated reduced obsolete-rule citation or decision inconsistency relative to baseline.","Reliance harms, contest volume, service disruption, archive accessibility, and restoration success lack operational thresholds and observed results.","No actual organizational adopter, governing authorization, records approval, or legal approval is documented.","Prior art and incremental distinctiveness are unsearched.","Rule-estate scale, data quality, dependency complexity, and ongoing review workload are unknown."],"next_evidence_step":"With one consenting unit, preregister a 90-day, 30-rule study that first audits overlap and contextual staleness and codes a baseline sample of rule citations and comparable decisions, then tests inventory, labels, and simulated tiering without destruction. Compare baseline guidance with the simulated lifecycle view on obsolete-rule citation, decision consistency, contestable reliance harms, and archive restoration; stop advancement if few sedimented rules are found, other causes explain inconsistency, outcomes do not improve, or reliance harms increase.","research_questions":["How many sampled rules are genuinely overlapping or context-stale rather than intentionally plural or constituency-specific?","What share of observed inconsistency is attributable to accumulated rule layers versus discretion, scarcity, or unequal enforcement?","Can independent reviewers reliably identify rule identity, ownership, dependencies, holds, reliance interests, and legitimate disposition authority?","Does simulated lifecycle treatment reduce obsolete-rule citation and disagreement on comparable cases relative to existing guidance?","Does the process create or worsen reliance harms, service disruption, inaccessible archives, or centralization of contested authority?","What contest, review, and maintenance workload would recur after the initial inventory?","Which elements, if any, are incrementally distinct from established policy review, records governance, and administrative simplification approaches?"],"recommendation":"PARTNERED_RESEARCH","uncertainty_constraints":["Closed-book assessment with no external verification.","Problem prevalence, severity, stakeholder demand, and realized impact are unmeasured.","Prior art, market distinctiveness, and comparative practice are unsearched.","Cost bands are resource-equivalent scenarios, not estimates based on organizational scale or observed workload.","The nearest-rival comparison is supplied by the candidate and is not externally validated.","Safety depends on actual consent, lawful authority, effective contestation, archive accessibility, and enforceable holds.","The 90-day pilot requires additional measurement definitions and halt thresholds before execution."],"closed_book_prior_art_boundary":"No claim is made that lifecycle governance, rule registers, sunset review, policy consolidation, records retention, reversible archival demotion, dependency gates, or affected-party contestation is novel or uncommon. Distinctiveness is assessed only against the candidate's stated nearest rival; external prior-art research is required."}