{"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__security_intelligence","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"security_intelligence","title":"Lifecycle-State Gating for Stale Security Intelligence","opportunity_summary":"Test whether explicit active, superseded, expired, held, archived, and quarantined states can reduce stale intelligence in current-facing retrieval while preserving provenance, dependencies, legal holds, reconstruction, and recoverability. The candidate is well specified and safely testable, but local prevalence, consequential use, dependency completeness, effect size, and distinctiveness remain unestablished.","adopter_authorizer":"Repository owners are the immediate adopters for visibility controls; records, legal, oversight, source-protection, security administration, and relevant product or downstream-system owners must authorize exceptions, preservation rules, operational suppression, and irreversible destruction within their mandates.","scores":{"meaningful_impact":{"score":4,"rationale":"If stale reports, indicators, assessments, or watchlist entries are materially influencing prioritization, attribution, alerts, or scrutiny, authoritative lifecycle gating could prevent consequential errors while retaining historical evidence. The packet does not establish how often such influence occurs."},"stakeholder_pull":{"score":3,"rationale":"The candidate identifies concrete beneficiaries and governance stakeholders and describes a recognizable tension between currency and preservation, but supplies no evidence of expressed demand, adoption commitments, incident frequency, or current cleanup burden."},"incremental_advantage":{"score":4,"rationale":"Compared with freshness warnings and ranking alone, the proposal adds authoritative lifecycle states, holds, dependency checks, recoverable archival, restoration testing, and controlled disposition. Whether these additions improve decisions enough to justify their burden requires comparison in the shadow pilot."},"distinctiveness_plausibility":{"score":3,"rationale":"The combination of retrieval gating and preservation safeguards is coherent and potentially differentiated from the stated nearest rival, but prior-art status is explicitly unsearched, so distinctiveness beyond that comparison is uncertain."},"technical_implementability":{"score":3,"rationale":"A labels-and-test-index shadow pilot appears technically bounded, but production implementation depends on incomplete ownership and dependency metadata, state propagation to feeds and exports, archive restoration, auditability, and control of downstream copies."},"adoption_authority_feasibility":{"score":3,"rationale":"Repository owners can authorize limited visibility experiments, and the packet identifies the additional authorities needed. Feasibility is constrained by fragmented mandates and the need for records, legal, oversight, source-protection, product-owner, and downstream-system coordination."},"evidence_readiness":{"score":4,"rationale":"The candidate provides an observable state, separate problem and intervention falsifiers, a 30-day shadow design, a baseline comparison, restoration sampling, halt conditions, and rollback. Readiness falls short of very favorable because sampling, evaluation ownership, and quantitative success and halt tolerances are unspecified."},"safety_net_benefit":{"score":4,"rationale":"Holds, dependency checks, resolvable markers, recoverable archives, restoration tests, audit-log rollback, and delayed destruction directly protect provenance and reconstruction. Residual risks include missed warnings, archive exposure, manipulated lifecycle signals, and ungoverned downstream copies."},"scalability":{"score":3,"rationale":"Lifecycle states could form a reusable control pattern across artifact classes, but policies must be class-specific and scaling requires reliable metadata and propagation across repositories, feeds, exports, alerts, cases, and copied artifacts."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"50K_TO_250K","scope":"Design and execute the proposed 30-day shadow pilot for one non-live artifact class, including sampling, inventory, proposed-state labeling, a test index, baseline comparison, dependency tracing, archive-and-restore sampling, governance review, and analysis.","confidence":"LOW","assumptions":["One repository and one bounded artifact class are included.","Existing access, test-index, logging, and archive capabilities can be reused.","No live feed suppression or hard deletion occurs.","Security-cleared analyst, administrator, records, legal, and evaluation labor is included.","The packet supplies no repository size, integration complexity, labor rates, or data-access constraints."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Productionize lifecycle-state controls for an initial repository and limited set of artifact classes, including policy configuration, metadata remediation, audit controls, archival workflows, restoration validation, training, and selected downstream integrations.","confidence":"LOW","assumptions":["Deployment begins only after the shadow pilot supports the problem and intervention claims.","The initial scope excludes enterprise-wide migration and irreversible bulk destruction.","Some existing repository, identity, archive, and audit infrastructure is reusable.","Ownership and dependency metadata require material but bounded remediation."]},"operational_launch":{"band_2026_usd":"1M_TO_5M","scope":"Launch governed lifecycle gating across a substantial operational repository environment, with feed and export propagation, exception and hold workflows, downstream-owner coordination, monitoring, security review, training, restoration exercises, and staged migration of multiple artifact classes.","confidence":"LOW","assumptions":["Multiple sensitive artifact classes and downstream consumers are in scope.","Launch requires cross-functional governance and compliance work as well as engineering.","Legacy copies and integrations require discovery and remediation.","The band does not represent a universal or enterprise-wide exact cost."]},"annual_recurring":{"band_2026_usd":"250K_TO_1M","scope":"Operate lifecycle review, exception and hold administration, metadata stewardship, archive security, restoration tests, audit review, downstream propagation monitoring, policy updates, analyst support, and evaluation.","confidence":"LOW","assumptions":["A limited production estate is maintained rather than a global intelligence enterprise.","Human review remains necessary because validity does not decay monotonically with age.","Existing hosting and repository operations absorb some infrastructure costs.","Recurring burden varies materially with corpus volume, sensitivity, exception rates, and number of integrations."]}},"research_burden":"HIGH","earliest_credible_horizon":"0_TO_3_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The packet defines an observable and consequentially plausible stale-active retrieval problem, but it provides no representative baseline showing that stale artifacts are prevalent or actually influence analyst or automated decisions."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"Repository owners are identified as adopters for visibility controls, with records, legal, oversight, source-protection, product, and downstream-system owners explicitly assigned authorization roles for exceptions and irreversible actions."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The candidate claims that lifecycle-state gating will reduce stale-active retrieval relative to active-by-default search with freshness warnings, without unacceptable missed retrieval, unresolved dependencies, or restoration failures."},"bounded_next_evidence_step":{"status":"YES","reason":"A 30-day shadow pilot on one non-live artifact class is bounded, non-destructive, baseline-comparative, and includes dependency tracing and sampled archive restoration."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The first step permits only labels and test indexes, preserves all artifacts, respects holds and mandates, excludes live-feed suppression and deletion, and specifies halt and rollback conditions. Production authority remains a later gate rather than an unresolved stop to the shadow study."},"implementation_cost_scope_and_range":{"status":"YES","reason":"The candidate defines a bounded initial test and separable production stages, permitting broad resource-equivalent ranges, although confidence is low because repository scale and integration complexity are absent."}},"blocking_evidence":["Representative evidence that stale or superseded artifacts occur in current-facing results and are used consequentially by analysts or automated consumers.","Baseline coverage of explicit lifecycle states and existing retention, search, warning, and dependency controls.","Predeclared sampling frame and success, harm, dependency, and restoration thresholds approved by evaluation and governance owners.","Evidence that lifecycle states propagate reliably to relevant search, feeds, exports, alerts, and downstream copies.","Evidence that ownership, holds, source obligations, and dependencies are sufficiently complete for safe gating.","Scoped prior-art evidence before asserting novelty or unusual distinctiveness."],"next_evidence_step":"Pre-register and run the authorized 30-day shadow pilot on one non-live artifact class: sample current-facing baseline retrievals, measure stale or superseded artifacts and documented analyst or automated use, assign proposed lifecycle states in a test index, compare stale-active and relevant-retrieval outcomes against the unchanged baseline, trace dependencies, and restore a sampled archive. Falsify the problem if baseline stale-active retrieval and consequential use are negligible or lifecycle coverage is already explicit; reject the intervention if it does not reduce stale-active retrieval or breaches predeclared missed-retrieval, unresolved-dependency, or restoration-failure tolerances. Make no live suppression or deletion.","research_questions":["How frequently do stale or superseded artifacts appear in representative current-facing searches, feeds, or enrichment results?","How often and with what consequences do analysts or automated systems act on those artifacts?","What explicit lifecycle, retention, warning, and archival controls already cover the sampled corpus?","Which measurable thresholds define acceptable stale-active reduction, missed relevant retrieval, unresolved dependencies, and restoration reliability?","Can lifecycle states propagate consistently through feeds, exports, alerts, cases, and downstream copies?","How complete and reliable are artifact ownership, dependency, hold, source-obligation, and exception metadata?","Can adversarial or biased manipulation of staleness and exception signals be detected and governed?","What security exposure is introduced by recoverable archives, quarantine, lifecycle metadata, and resolvable markers?","Which artifact classes require non-age-based validity rules because old intelligence can regain relevance?","What related intelligence-records, indicator-lifecycle, watchlist-governance, and archival-control practices already exist?"] ,"recommendation":"VALIDATE_PROBLEM_FIRST","uncertainty_constraints":["Closed-book assessment provides no external evidence of prevalence, demand, prior art, market size, realized impact, or exact cost.","Analytic validity is not assumed to decay monotonically with age.","The candidate does not define numerical success or halt tolerances.","Repository scale, corpus composition, metadata quality, integration count, and labor requirements are unspecified.","Production safety depends on downstream propagation and dependency completeness that the packet identifies as possible failure conditions.","Cost bands are resource-equivalent planning ranges, not quotations or point estimates."],"closed_book_prior_art_boundary":"Prior-art status is UNSEARCHED. This assessment compares the proposal only with the sealed candidate's stated baseline and nearest rival; it makes no claim about novelty, prevalence, competitive uniqueness, or existing intelligence-records, indicator-lifecycle, watchlist, archival, or retention practices."}