{"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__behavioral_economics","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"behavioral_economics","title":"Lifecycle Review and Reversible Retirement of Choice Architecture","opportunity_summary":"Establish a persistent inventory, review triggers, exceptions, dependency checks, and reversible retirement process for behavioral interventions that may have become stale or conflicting. The proposal targets improved comprehension, autonomy, equity, service performance, and maintainability, but the existence and material harm of unmanaged accretion remain hypotheses.","adopter_authorizer":"The accountable service owner is the likely adopter and may authorize reversible deactivation after risk-appropriate behavioral, operational, legal, accessibility, and ethics review; irreversible deletion additionally requires records authority.","scores":{"meaningful_impact":{"score":4,"rationale":"If stale or conflicting interventions materially impair comprehension, autonomy, equity, or completion, retiring them could improve several important user-welfare and operational outcomes. The packet does not establish how often such harm occurs or its magnitude."},"stakeholder_pull":{"score":2,"rationale":"The proposal identifies affected users, service owners, operators, reviewers, and behavioral-design teams, but provides no evidence that any adopter currently prioritizes the problem, requests this solution, or will fund ongoing lifecycle governance."},"incremental_advantage":{"score":4,"rationale":"Relative to the specified one-time audit, the candidate adds a persistent registry, mandatory review triggers, differentiated exceptions, dependency checks, reversible deactivation, outcome revalidation, and restoration. Whether these additions outperform simpler recurring audits is untested."},"distinctiveness_plausibility":{"score":3,"rationale":"The integrated lifecycle-and-rollback design is plausibly distinguishable from the stated one-time audit, but prior art is explicitly unsearched and potential overlap with registries, sunset clauses, experimentation platforms, and audit practices is unresolved."},"technical_implementability":{"score":3,"rationale":"A bounded journey with identifiable interventions and reversible configuration changes appears implementable, but feasibility depends on separable interventions, observable exposure and outcomes, known dependencies, and subgroup measurement—conditions the packet identifies as possible failure points."},"adoption_authority_feasibility":{"score":4,"rationale":"The accountable service owner, required reviewers, records authority, exclusions, and restoration conditions are explicitly identified. Cross-functional approval and legal or accessibility obligations could still delay or prevent action."},"evidence_readiness":{"score":3,"rationale":"The packet supplies observable states, separate problem and intervention falsifiers, measurable outcomes, comparison options, and an eight-week pilot boundary. It supplies no empirical baseline, validated staleness measure, effect-size expectations, or evidence that suitable candidates exist."},"safety_net_benefit":{"score":5,"rationale":"Reversible deactivation, preserved prior configuration, protected-category exclusions, prespecified subgroup and service bounds, and immediate halt-and-restore conditions provide unusually explicit protection against harmful retirement decisions."},"scalability":{"score":3,"rationale":"The registry and review pattern could be reused across services, but scaling would require service-specific inventories, ownership resolution, dependency mapping, outcome instrumentation, review capacity, and compliance interpretation."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Prepare and run one eight-week bounded-service study covering inventory, ownership and evidence review, selection of no more than three low-risk candidates, comparison design, monitoring, subgroup analysis, and rollback readiness.","confidence":"MODERATE","assumptions":["Existing product analytics and configuration controls can support exposure measurement and reversible changes.","The service journey is bounded and does not involve excluded high-stakes decisions.","Behavioral, legal, accessibility, ethics, and operational reviewers contribute limited part-time effort.","No major new data platform or specialized equipment is required."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Create a production-capable lifecycle registry and governance process for an initial service portfolio, including data model, ownership assignment, review workflows, dependency records, access controls, configuration rollback, and staff training.","confidence":"LOW","assumptions":["Deployment covers several related journeys within one organization rather than an enterprise-wide transformation.","Existing workflow, experimentation, and product-management systems can be integrated rather than replaced.","Historical interventions require substantial but bounded manual reconstruction.","Compliance requirements do not demand a new records-management platform."]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Launch routine use across the initial portfolio, complete backlog triage, conduct cross-functional reviews, instrument outcomes, communicate changes, and operate heightened monitoring during early retirement decisions.","confidence":"LOW","assumptions":["Only a limited subset of inventoried interventions proceeds to deactivation at launch.","Low-risk changes remain reversible through existing release controls.","Subgroup and complaint monitoring data are legally and technically available.","Launch excludes automatic deletion and high-stakes unreviewed changes."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Maintain the registry, conduct scheduled and triggered reviews, update dependencies and evidence status, monitor outcomes and subgroup effects, preserve rollback capability, administer exceptions, and audit compliance for the initial portfolio.","confidence":"LOW","assumptions":["Recurring work supports one moderate service portfolio, not a large multinational enterprise.","Review volume remains manageable through risk-based scheduling.","Most costs are cross-functional labor, analytics, software integration, and governance overhead.","Sensitive behavioral data can be retained or minimized under existing approved controls."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The packet clearly defines an observable accretion problem and its falsifier, but the claim that unmanaged persistence materially worsens welfare or decision quality is explicitly hypothetical and lacks external or empirical support."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"The accountable service owner is named as the reversible-deactivation authority, with risk-appropriate reviewers and separate records authority for irreversible deletion."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The candidate claims that persistent lifecycle review and reversible retirement improve stale exposure and user or operational outcomes relative to status quo or a one-time audit; baseline and staggered-control comparisons and adverse-outcome falsifiers are specified."},"bounded_next_evidence_step":{"status":"YES","reason":"An eight-week study on one bounded journey, with no more than three low-risk candidates, reversible changes, measured outcomes, comparison conditions, and explicit falsifiers is defined."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The packet excludes automatic deletion and protected or high-stakes interventions, conditions action on multidisciplinary review, and requires immediate restoration for compliance, safety, subgroup, complaint, or completion breaches."},"implementation_cost_scope_and_range":{"status":"YES","reason":"A bounded first study and portfolio-level implementation can be scoped into broad resource bands, although system integration, historical reconstruction, and review burden make deployment estimates low-confidence."}},"blocking_evidence":["Whether the bounded service actually contains persistent, unowned, conflicting, or context-invalid behavioral interventions.","Whether intervention staleness is associated with comprehension errors, unwanted steering, complaints, inequitable effects, service failure, or meaningful maintenance burden rather than underlying service complexity.","Whether interventions can be separately identified, exposure-measured, reversibly deactivated, and dependency-checked.","Whether affected subgroup outcomes and welfare-relevant measures can be assessed without treating reduced uptake as improved welfare.","Whether an accountable service owner and required reviewers perceive sufficient value to sustain lifecycle governance.","Whether the proposed persistent lifecycle combination materially differs from existing registries, sunset processes, experimentation platforms, or recurring audits."],"next_evidence_step":"Run a bounded eight-week study on one service journey: first complete the intervention registry and exposure audit; then, only if at least one low-risk stale candidate exists and review authorizes it, randomize or stagger reversible deactivation of no more than three candidates against unchanged baseline periods or units. Compare comprehension, completion, choices, complaints, subgroup effects, operational incidents, stale exposure, and maintenance effort. Falsify the problem if the audit finds no persistent unowned or context-invalid intervention or associated harm; falsify the intervention if retirement produces no improvement or breaches prespecified welfare, equity, completion, compliance, or safety bounds.","research_questions":["How many interventions in the selected journey lack a current owner, objective, evidence status, dependency record, successor, or review date?","Can staleness classes be defined reliably without allowing age or a composite score to become automatic removal authority?","Are accumulated or conflicting cues associated with measurable user or maintenance harm after accounting for underlying service complexity?","Can candidate interventions be isolated and reversibly deactivated without disrupting legal, accessibility, safety, evaluation, or operational dependencies?","Which measures distinguish improved informed choice and welfare from reduced participation or uptake?","Do any vulnerable or accessibility-dependent subgroups worsen after deactivation?","Does persistent lifecycle governance add decision-relevant value beyond a one-time or periodically repeated audit?","Will the accountable owner and required reviewers accept the recurring workload, data practices, and decision rights?","What existing practices overlap with the registry, expiry triggers, exception process, dependency checks, and rollback pathway?","What minimum records must be retained for restoration and accountability without unjustified preservation of sensitive behavioral data?"],"recommendation":"VALIDATE_PROBLEM_FIRST","uncertainty_constraints":["No external sources or prior-art results are available.","Problem prevalence, stakeholder demand, market size, and realized impact are unmeasured.","The material-welfare claim and benefit of retirement are hypotheses.","Cost bands are resource-equivalent planning ranges, not observed quotations or point estimates.","Technical feasibility varies with intervention separability, instrumentation, dependency visibility, and reversibility.","Behavioral effects may persist after restoration, so configuration rollback does not guarantee full behavioral reversibility.","The assessment does not infer that a live deployment is authorized or required."],"closed_book_prior_art_boundary":"Prior art is explicitly UNSEARCHED. The packet permits comparison only with its stated status quo and nearest rival; it does not establish novelty, prevalence, adoption, or superiority relative to real-world behavioral-intervention registries, sunset clauses, experimentation platforms, lifecycle governance, or choice-architecture audit practices."}