{"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__military_strategic_studies","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"military_strategic_studies","title":"Explicit validity states and reversible retirement for superseded operational guidance","opportunity_summary":"The candidate proposes explicit current, superseded, held, and archived states; dependency and authority gates; reversible retirement; and restoration testing for sequential headquarters guidance. It could reduce selection of stale artifacts and search friction while preserving accountability, but harmful prevalence, incremental effect, and differentiation from existing military publication and records controls are unestablished.","adopter_authorizer":"A headquarters operations or knowledge-management organization could adopt the workflow, subject to commanders retaining authority over operational validity and designated records, legal, classification, security, and investigative authorities approving retention and disposition within their mandates.","scores":{"meaningful_impact":{"score":4,"rationale":"If obsolete guidance is mistaken for current authority, the candidate could materially improve command reliability and protect accountability and reconstruction. The packet does not establish how often this occurs, so the potential impact cannot support the maximum score."},"stakeholder_pull":{"score":3,"rationale":"Command staffs and records, legal, intelligence, and security authorities have plausible interests in authoritative retrieval and lawful preservation, but the sealed candidate supplies no observed demand, adoption request, or burden measurement."},"incremental_advantage":{"score":4,"rationale":"Relative to shared drives and a manually curated single-current-plan library, the proposal adds dependency gates, exception revalidation, reversible retirement, auditability, and tested restoration. Whether these additions improve outcomes enough to justify their review burden remains untested."},"distinctiveness_plausibility":{"score":2,"rationale":"The proposed combination is coherent, but prior art is explicitly unsearched and the candidate itself identifies existing command-publication and records controls as potentially providing authoritative versions, rescission, and historical preservation."},"technical_implementability":{"score":3,"rationale":"A shadow classification pilot on at most 200 non-live artifacts appears technically bounded, but disconnected classified systems, dynamic references, coalition-held copies, and incomplete dependency graphs may prevent reliable implementation beyond the pilot."},"adoption_authority_feasibility":{"score":3,"rationale":"The packet identifies relevant command and specialist authorities and preserves their mandates, but operational adoption would require coordination across several authorities and potentially coalition or external custodians."},"evidence_readiness":{"score":4,"rationale":"The candidate specifies a safe eight-week shadow pilot, baseline comparisons, measurable outcomes, falsifiers, and halt conditions. Sampling, adjudication rules, metric definitions, and acceptance thresholds still require preregistration."},"safety_net_benefit":{"score":4,"rationale":"Reversible retirement, holds, audit logs, restoration tests, and an untouched baseline directly limit irreversible loss and support reconstruction. Residual risks include missed dependencies, exposed classified metadata, and archive latency."},"scalability":{"score":2,"rationale":"Scaling across missions, classifications, repositories, and coalition environments would face heterogeneous policies, incomplete inventories, access constraints, and potentially high recurring expert-review labor."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"A bounded prior-art and doctrine review followed by the specified eight-week shadow assessment of at most 200 non-live artifacts at one headquarters, including secure access, expert adjudication, metric preregistration, analysis, and reporting.","confidence":"MODERATE","assumptions":["No live guidance, repository visibility, or retention state is changed.","Existing secure facilities and repository access can be used.","Command, records, legal, classification, and security experts contribute limited part-time labor.","No major software integration or new accredited infrastructure is required."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Design and preparation of a production-capable implementation for one headquarters, including lifecycle policy mapping, metadata design, dependency rules, access-control review, prototype integration, testing, training materials, and approval coordination.","confidence":"LOW","assumptions":["The headquarters has a manageable number of principal repositories.","Existing repository interfaces can support labels, audit records, and segregated discovery.","Accreditation can extend existing infrastructure rather than require a new platform.","Legacy artifact remediation is limited to a prioritized collection."]},"operational_launch":{"band_2026_usd":"1M_TO_5M","scope":"Authorized launch across the principal repositories of one headquarters, including inventory reconciliation, expert validation, integration, security and compliance work, user training, restoration exercises, and initial operational support.","confidence":"LOW","assumptions":["Launch does not include enterprise-wide or coalition-wide deployment.","Human authorities review consequential validity and disposition decisions.","Classified environments require separate integration and testing work.","Existing archives can be adapted for tested restoration."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Annual operation at one headquarters, including lifecycle reviews, exception revalidation, dependency maintenance, audit and restoration tests, user support, training, software maintenance, and authority coordination.","confidence":"LOW","assumptions":["Automation assists triage but does not determine command validity or destruction.","Artifact volume and exception rates remain moderate.","Existing records, legal, security, and operational personnel absorb some review duties.","Major repository replacement and enterprise expansion are excluded."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The packet describes an observable and consequential problem hypothesis with a clear falsifier, but provides no external evidence that harmful repository sprawl is prevalent or burdensome in the proposed setting."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"The candidate identifies headquarters users, commanders responsible for operational validity, and records, legal, classification, security, and investigative authorities responsible for retention or disposition."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal claims that dependency gates, reversible retirement, exception revalidation, and restoration testing improve stale-item selection and search outcomes beyond shared-drive practice or manual single-current-plan curation; the shadow pilot can test that claim."},"bounded_next_evidence_step":{"status":"YES","reason":"The sealed candidate authorizes an eight-week, at-most-200-artifact shadow pilot with no repository changes or deletions and identifies baseline comparisons, outcome measures, falsifiers, and halt conditions."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"For the evidence step, live artifacts and operational changes are excluded, authority remains with commanders and designated specialists, and explicit halt and rollback rules address holds, dependencies, access controls, and false-stale classifications."},"implementation_cost_scope_and_range":{"status":"YES","reason":"The candidate bounds the initial pilot by duration, artifact count, site, and prohibited actions, permitting broad resource bands; later deployment ranges remain low-confidence because repository complexity and accreditation requirements are unknown."}},"blocking_evidence":["Whether consumers at a representative headquarters actually encounter ambiguous supersession states, select stale artifacts, or incur material search burden.","Whether established command-publication, records-management, archival, or knowledge-management controls already provide the proposed combination or its intended effects.","Whether lifecycle classifications agree with authorized expert adjudication at acceptable false-stale and missed-dependency rates.","Whether representative archived artifacts can be restored within authority-defined fidelity and latency limits.","Whether the expert-review and exception-revalidation labor is lower than the search and decision burden removed.","Whether classified, disconnected, coalition, and external holdings can be handled without exposing metadata or implying a falsely complete dependency graph."],"next_evidence_step":"Conduct a six-to-eight-week study at one headquarters covering at most 200 non-live artifacts: first map the candidate's mechanisms against applicable existing publication, records, archival, and knowledge-management controls, then run the authorized shadow classification against ordinary search and expert adjudication. Preregister sampling and tolerances; falsify further pursuit if existing controls already supply the claimed combination and consumers reliably select canonical guidance, or if the shadow method fails to reduce stale selection or search time without unacceptable false-stale, missed-dependency, or restoration results.","research_questions":["How often do users retrieve or act upon superseded artifacts when performing representative planning tasks under the ordinary baseline?","Which proposed mechanisms are absent from, or materially weaker than, existing command-publication and records controls?","What authority-defined error tolerances apply to false-stale classifications and missed dependencies?","Can artifact identity and dependencies be resolved adequately across classified, disconnected, and coalition repositories?","How much expert labor is required per artifact and per exception, and does it exceed the burden removed?","Can archived artifacts and their relevant context be restored within agreed fidelity and latency limits?","Does metadata aggregation introduce classification, operational-security, or access-control risks that negate the benefit?","Do lifecycle labels remain advisory, or do users begin treating them as de facto command authority?"] ,"recommendation":"PRIOR_ART_RESEARCH","uncertainty_constraints":["Closed-book assessment with no external validation of prevalence, demand, novelty, realized impact, or market size.","Prior-art status is explicitly unsearched.","Costs are broad resource-equivalent bands, not quotations, and depend heavily on repository count, classification boundaries, accreditation, and expert-review intensity.","The candidate's strongest comparison and safety claims remain hypotheses until measured against existing controls and authorized adjudication.","Operational validity cannot be inferred from age, access frequency, or an incomplete dependency graph.","The safe shadow pilot does not establish feasibility of live retirement, visibility changes, archiving, or destruction."],"closed_book_prior_art_boundary":"No conclusion is made about world novelty, existing military doctrine, product availability, prevalence, or established practice. The sealed packet only supports treating differentiation from command-publication, records-management, archival, and knowledge-management controls as an unresolved research question."}