{"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 State and Reversible Retirement for Operational Guidance","opportunity_summary":"The candidate proposes explicit current, superseded, held, and archived states for sequential operational artifacts, with dependency and authority checks before reversible retirement. It could reduce selection of stale guidance and search friction while preserving accountability and reconstruction evidence, but the prevalence of harmful repository sprawl, improvement over existing controls, and distinctiveness from established military practice are unverified.","adopter_authorizer":"A headquarters command and its repository or knowledge-management owner would adopt the approach; commanders would authorize operational-validity judgments, while records, legal, classification, security, and investigative authorities would authorize retention or disposition within their respective mandates.","scores":{"meaningful_impact":{"score":4,"rationale":"If obsolete guidance is mistaken for current authority, the stated consequences include contradictory interpretation and operational action based on stale assumptions; preserving inquiry and reconstruction records also matters. The magnitude and frequency of these consequences are not established."},"stakeholder_pull":{"score":3,"rationale":"Command staffs, consuming units, coalition partners, and specialist authorities have recognizable interests in authoritative discovery and lawful retention, but the packet contains no interviews, demand evidence, prevalence measurements, or commitment from an adopter."},"incremental_advantage":{"score":3,"rationale":"Relative to shared-drive conventions and a manually curated current-plan library, the proposed dependency gates, exception revalidation, reversible retirement, and restoration testing offer a coherent possible advantage. No comparative result establishes that these additions outperform existing practice or justify their review burden."},"distinctiveness_plausibility":{"score":2,"rationale":"The proposed combination is specifically articulated, but command-publication, records-management, archival, and knowledge-management controls are plausible close precedents. Prior art is explicitly unsearched, so distinctiveness cannot presently be credited beyond a hypothesis."},"technical_implementability":{"score":3,"rationale":"A shadow classification exercise over at most 200 non-live artifacts is technically bounded and avoids repository modification. Broader implementation is constrained by secrecy, disconnected systems, dynamic references, coalition-held copies, incomplete dependency graphs, and restoration requirements."},"adoption_authority_feasibility":{"score":3,"rationale":"The packet identifies commanders and the relevant records, legal, classification, security, and investigative authorities, and separates their mandates. Joint authorization across these parties and coalition dependencies could make adoption slow or fragmented."},"evidence_readiness":{"score":4,"rationale":"The candidate supplies separate problem and intervention falsifiers, an eight-week shadow pilot, comparison measures, excluded actions, and halt conditions. Readiness is reduced because sampling, adjudication rules, metric definitions, and acceptance tolerances are not fixed."},"safety_net_benefit":{"score":4,"rationale":"Reversible retirement, holds, dependency blocks, preserved logs, simulated restoration, and an untouched baseline directly protect accountability and institutional memory while testing stale-guidance reduction. These safeguards remain unvalidated and could fail if inventories or dependencies are incomplete."},"scalability":{"score":2,"rationale":"The lifecycle structure could be repeated across repositories, but scaling would require policy alignment, controlled metadata aggregation, expert review, graph maintenance, coalition coordination, and support for disconnected or classified systems. The packet provides no evidence that review labor remains economical at larger scale."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Prepare and run the proposed eight-week shadow pilot on at most 200 non-live artifacts from one headquarters, including secure access, sampling, expert adjudication, measurement, simulated restoration, and reporting.","confidence":"MODERATE","assumptions":["Existing repository access and a suitable secure analysis environment are available.","The pilot makes no repository changes, visibility changes, or deletions.","Command, records, legal, classification, security, and investigative experts contribute limited review time.","No custom production integration or major data remediation is included."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Establish a controlled implementation for one headquarters, including lifecycle policy, authority workflows, repository integration, metadata controls, training, audit logging, dependency handling, and restoration testing.","confidence":"LOW","assumptions":["The headquarters has a limited number of repositories with usable interfaces or export mechanisms.","The implementation supplements rather than replaces core repositories.","Classification and access-control accreditation can reuse existing infrastructure.","Extensive coalition-system integration and enterprise-wide migration are excluded."]},"operational_launch":{"band_2026_usd":"1M_TO_5M","scope":"Launch the governed lifecycle process across the headquarters' principal operational-guidance repositories, with production integrations, security and compliance validation, user training, operational support, archive capability, and evaluation.","confidence":"LOW","assumptions":["Launch covers one headquarters rather than a military-wide enterprise.","Several repositories and security domains require integration.","Human validity adjudication remains required for consequential artifacts.","Coalition coordination is bounded and does not require replacing partner systems."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Operate and maintain the one-headquarters capability, including expert reviews, exception revalidation, audit and compliance work, dependency maintenance, archive and restoration tests, software support, and training.","confidence":"LOW","assumptions":["Artifact volumes and exception rates remain manageable by a small dedicated team plus part-time authorities.","Existing storage and identity infrastructure are reused.","No major repository replacement or continuous military-wide support is included.","Review labor does not grow faster than the search burden removed."]}},"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 repository-governance problem with a clear falsifier, but labels it a hypothesis and supplies no external evidence that harmful sprawl or stale-guidance selection occurs materially."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"A headquarters and its repository owner are identifiable adopters, while commanders and designated records, legal, classification, security, and investigative authorities have explicitly assigned authorization roles."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The candidate claims that explicit lifecycle states, dependency gates, reversible retirement, exception revalidation, and restoration testing improve stale-artifact selection and search time beyond ordinary repositories or manual single-current-plan curation; the stated pilot can test that claim."},"bounded_next_evidence_step":{"status":"YES","reason":"The sealed candidate authorizes an eight-week shadow pilot on at most 200 non-live artifacts, with no repository changes or deletions, comparing lifecycle classifications with expert adjudication and the untouched baseline."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The pilot excludes live guidance changes, automatic cancellation, destruction, visibility changes, and bypass of holds; it also defines authority roles and halt conditions for live-artifact inclusion, missed dependencies or holds, weakened access controls, and excessive false-stale classifications."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"A one-headquarters scope and broad resource bands can be framed, but repository count, security domains, accreditation needs, integration interfaces, artifact volume, coalition dependencies, and continuing expert-review load are unspecified."}},"blocking_evidence":["Whether consumers at a bounded headquarters actually encounter ambiguous or obsolete guidance often enough to create material decision or maintenance burden.","Whether existing command-publication, records-management, archival, and knowledge-management controls already provide the proposed functions or causal benefit.","Preregistered sampling, expert-adjudication rules, metric definitions, baseline comparison method, and authority-set thresholds for false-stale and missed-dependency results.","Whether representative dependencies and holds can be identified with acceptable miss rates across classified, disconnected, dynamic-reference, and coalition-held artifacts.","Whether representative archived artifacts can be restored within agreed fidelity and latency limits.","Whether recurring expert review and exception revalidation cost less than the search and decision burden removed."],"next_evidence_step":"Run the authorized eight-week shadow pilot on no more than 200 non-live artifacts from one headquarters. Compare proposed lifecycle classifications against both the existing baseline's current-guidance selections and blinded expert adjudication; measure stale-item selection, search time, false-stale flags, dependency or hold misses, and simulated restore success. Falsify progression if the bounded audit shows negligible baseline burden, the proposal fails to improve selection or search time, error rates exceed authority-set tolerances, or representative restoration fails agreed fidelity or latency limits.","research_questions":["Do personnel reliably select canonical current guidance under existing repository and publication controls, and how often are superseded artifacts misinterpreted?","Which proposed functions are already present in command-publication, records, archival, knowledge-management, or repository systems?","What incremental causal claim remains after comparison with a manually curated single-current-plan library?","Can expert adjudicators consistently distinguish current, superseded, held, and archived states without lifecycle labels gaining de facto command authority?","What false-stale and missed-dependency rates are acceptable to commanders and specialist authorities?","How complete can dependency and hold detection be across classified, disconnected, coalition, and externally controlled repositories?","Can representative archived artifacts be restored within required fidelity and operational latency?","Does review, exception-revalidation, and integration labor remain below the burden removed at headquarters scale?","Can inventory aggregation avoid exposing classified relationships or weakening existing access controls?","How should tombstones and lifecycle labels themselves be governed to prevent a new unmanaged layer?"] ,"recommendation":"PRIOR_ART_RESEARCH","uncertainty_constraints":["Problem prevalence and effect size are unmeasured.","No stakeholder-demand or adopter-commitment evidence is supplied.","Prior art and real-world distinctiveness are unverified.","Pilot measurement rules and acceptance thresholds are incomplete.","Repository architecture, security accreditation, coalition dependencies, and artifact volumes are unspecified.","Cost bands are resource-equivalent planning ranges, not observed implementation costs.","Scalability depends on uncertain inventory completeness and continuing expert-review labor."],"closed_book_prior_art_boundary":"Prior art is unsearched and unverified. This closed-book assessment makes no claim about novelty, prevalence, market size, realized impact, or whether existing military command-publication, records-management, archival, knowledge-management, or repository systems already implement the proposed combination."}