{"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__public_administration_policy","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"public_administration_policy","title":"Authoritative Lifecycle and Supersession Controls for Administrative Policy Stacks","opportunity_summary":"Establish explicit, authority-bounded lifecycle states, review triggers, dependency checks, holds, archival controls, and durable redirects so obsolete administrative instruments lose operational visibility without erasing legally or historically required records. The candidate is coherent and testable, but the prevalence of harmful policy-stack decay, stakeholder demand, intervention effects, and distinctiveness from existing government practice remain unverified.","adopter_authorizer":"A bounded program office is the prospective adopter; the legally designated policy owner authorizes operational status changes, while records, legal, privacy, and archival authorities approve destruction and applicable overrides.","scores":{"meaningful_impact":{"score":4,"rationale":"The proposal targets inconsistent implementation, outdated requirements, conflicting public instructions, and loss of legal or historical accountability, all consequential outcomes if the stated obsolete-policy stack is materially present; prevalence and realized impact are unverified."},"stakeholder_pull":{"score":2,"rationale":"The packet identifies affected staff, policy owners, public users, and oversight functions but provides no evidence that any adopter has requested the intervention, allocated resources, or prioritized the problem."},"incremental_advantage":{"score":4,"rationale":"Relative to periodic decentralized cleanup and a one-time consolidation project, the continuing lifecycle states, triggers, holds, dependency gates, authorized disposition, audit logs, and redirects provide a clear incremental mechanism; outcome improvement remains hypothetical."},"distinctiveness_plausibility":{"score":3,"rationale":"The integrated combination of policy-status governance, dependencies, preservation controls, and user redirects could be distinctive as a package, but prior art in records schedules, registries, supersession practices, and continuous review programs is explicitly unsearched."},"technical_implementability":{"score":4,"rationale":"A bounded inventory, status model, ownership mapping, audit log, dependency review, and non-destructive labels use feasible administrative and information-management methods, although fragmented repositories and unreliable metadata could materially complicate implementation."},"adoption_authority_feasibility":{"score":3,"rationale":"The proposal names the legally designated policy owner and required records, legal, privacy, and archival approvals, but decentralized or disputed authority and unresolved preservation obligations could prevent reliable status changes."},"evidence_readiness":{"score":3,"rationale":"A safe sample of 30 instruments, explicit problem and intervention falsifiers, and reversible labeling support an initial study, but representative sampling, measurement reliability, comparison procedures, and decision thresholds are not yet operationalized."},"safety_net_benefit":{"score":4,"rationale":"Holds, dependency checks, durable redirect markers, audit logs, restoration tests, separated legal and metadata authority, and rollback conditions directly reduce the risks of hidden guidance and premature destruction, though their reliability is untested."},"scalability":{"score":3,"rationale":"A common lifecycle model and registry could extend across policy families, but heterogeneous legal authorities, repositories, retention schedules, dependencies, and ownership structures may require substantial local adaptation and ongoing governance."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"One non-production program study covering one bounded policy family, inventory construction, a stratified review of 30 instruments, authority and dependency checks, baseline comparison, user identification tasks, reviewer-agreement measurement, and a written decision report.","confidence":"MODERATE","assumptions":["Existing repositories can be accessed without major procurement or litigation.","The study uses status labels in a shadow inventory and deletes or hides nothing.","Policy, records, legal, archival, and user representatives contribute part-time labor.","No custom enterprise software integration is required for the first study."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Design and configure lifecycle states, governance rules, ownership workflows, audit logging, redirect behavior, training, compliance review, and limited integrations for one program or policy portfolio.","confidence":"LOW","assumptions":["An existing content or records platform can be configured rather than replaced.","The initial portfolio has tractable ownership and retention obligations.","Costs include program management, legal review, data cleanup, testing, and training.","Substantive policy revision and large-scale digitization are outside this phase."]},"operational_launch":{"band_2026_usd":"1M_TO_5M","scope":"Agency-level rollout across multiple policy families and repositories, including integrations, migration, governance staffing, accessibility, security, records and legal validation, training, evaluation, and rollback capability.","confidence":"LOW","assumptions":["The agency has several heterogeneous repositories but no requirement to replace every source system.","Launch includes human review for consequential status decisions.","Legacy metadata and cross-reference cleanup require material labor.","The estimate excludes unusually large litigation holds or wholesale modernization of agency records infrastructure."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Ongoing ownership review, stale-item triage, legal and records oversight, registry administration, audit and restore tests, user support, training, metrics, and maintenance of repository integrations for a moderate agency deployment.","confidence":"LOW","assumptions":["Review is risk-prioritized rather than a full annual review of every instrument.","Existing staff absorb some policy-owner duties.","No automatic revocation or destruction is permitted.","Repository count and instrument volume remain moderate and are not supplied in the packet."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The candidate specifies observable conflicting or unlabeled instruments, affected users, consequences, and a problem falsifier, but supplies no external evidence that the condition is prevalent or materially associated with errors or maintenance burden."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"The packet identifies a program office and policy owners as adopters, the legally designated policy owner as status-change authority, and records, legal, privacy, and archival functions as required disposition or override authorities."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The claim that continuing lifecycle states, dependency gates, holds, and redirects improve identification and use of controlling guidance can be compared with periodic manual cleanup or an unchanged repository and falsified if no improvement occurs."},"bounded_next_evidence_step":{"status":"YES","reason":"The sealed candidate authorizes a one-program, one-policy-family inventory and stratified review of 30 instruments with labeling but no deletion, providing a reversible basis for a controlled comparison."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The proposed evidence step is non-destructive and does not change rights or legal authority; automatic expiry, destruction under holds, concealment without redirects, and metadata-based substantive changes are excluded, with explicit halt and rollback conditions."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"A bounded pilot and likely cost drivers can be scoped into broad bands, but instrument volume, repository complexity, integration requirements, staffing, and legal-review burden are absent, making deployment and recurring ranges low-confidence."}},"blocking_evidence":["A representative estimate of how often obsolete, conflicting, unowned, or superseded instruments remain visible in live workflows and public search.","Evidence linking those conditions to user errors, inconsistent implementation, or material maintenance burden rather than primarily to drafting, training, ranking, or decentralized authority.","Reliable identification of controlling authority, instrument owners, cross-references, dependencies, holds, and preservation obligations.","Comparative prior-art evidence on records schedules, policy registries, supersession practices, archival controls, and continuous policy-review programs.","Validated measures and decision thresholds for controlling-guidance identification, stale-instrument use, false retirement, missed dependencies, reviewer agreement, and restoration success."],"next_evidence_step":"In one program, build a non-production inventory of one bounded policy family and have two qualified reviewers independently classify a stratified sample of 30 instruments for authority, ownership, status, conflicts, dependencies, and holds. Then compare representative users' accuracy and time in identifying controlling guidance using the existing repository versus the shadow inventory with proposed labels and redirects. Proceed only if reviewer agreement and authority coverage meet predefined thresholds and the shadow condition materially improves identification without hiding a relied-upon instrument; falsify or redesign if obsolete conflicts are rare, classifications are unreliable, or user performance does not improve.","research_questions":["How frequent and consequential are obsolete or conflicting instruments in a representative policy family?","Can reviewers reliably determine controlling authority, ownership, dependencies, holds, and preservation duties from available records?","Does the lifecycle-labeled shadow inventory improve identification of controlling guidance relative to the unchanged repository?","Are observed errors better explained by lifecycle absence than by drafting, training, search ranking, or decentralized authority?","What false-retirement, missed-dependency, and restoration thresholds would legal, records, archival, policy-owner, and affected-user stakeholders accept?","Which parts of the integrated design are incremental to existing policy-governance and records-management practices?","What governance and staffing are required to keep the registry from becoming another stale layer?","How do repository count, instrument volume, integration complexity, and mandatory review effort affect deployment and recurring cost bands?"],"recommendation":"PARTNERED_RESEARCH","uncertainty_constraints":["Closed-book assessment with no external sources.","Problem prevalence, stakeholder demand, realized impact, and market size are unmeasured.","Prior-art novelty and comparative distinctiveness are unverified.","No validated effect size, success threshold, or measurement instrument is supplied.","Deployment complexity and costs depend on undisclosed repository, instrument, staffing, and legal-review conditions.","Metadata status cannot itself revoke legal authority or alter substantive rights and duties."],"closed_book_prior_art_boundary":"Prior art was not searched and remains unverified. No claim is made about novelty, prevalence, or superiority relative to existing government records management, policy registries, supersession practices, archival controls, or continuous policy-review programs."}