{"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__futurism_foresight","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"futurism_foresight","title":"Lifecycle-Gated Authority for Foresight Artifacts","opportunity_summary":"Apply explicit lifecycle states, owner review, dependency gates, search demotion, preservation holds, and restoration controls so superseded foresight artifacts lose current authority without erasing institutional memory. The sealed candidate provides a reversible comparative pilot, but the frequency and decision consequences of stale-artifact confusion remain hypotheses.","adopter_authorizer":"A foresight repository steward is the operational adopter; artifact owners validate classifications, while records or legal authorities govern holds and irreversible destruction.","scores":{"meaningful_impact":{"score":3,"rationale":"Mistaking obsolete scenarios, assumptions, or signals for current guidance could affect strategy and policy decisions, while preserving lineage has institutional value. The packet supplies no evidence about how often such mistakes occur or their realized consequences."},"stakeholder_pull":{"score":2,"rationale":"Repository stewards and decision-makers have identifiable interests in currency and reconstructability, but the sealed candidate reports no requests, commitments, recurring incidents, or other evidence of active demand."},"incremental_advantage":{"score":4,"rationale":"Relative to the stated date-based manual archive campaign, artifact-level supersession, dependency checks, holds, search demotion, audit logs, and tested restoration directly address authority ambiguity and preservation risk. The size of the practical improvement is unmeasured."},"distinctiveness_plausibility":{"score":3,"rationale":"The authority-centered combination is differentiated from the candidate's nearest rival, but prior-art status is explicitly unsearched and overlap with existing foresight knowledge-management or records-governance practice is unknown."},"technical_implementability":{"score":4,"rationale":"The intervention relies on feasible-seeming repository metadata, labels, indexing behavior, audit logs, reversible archiving, and restoration tests. Implementation may be constrained by missing ownership, heterogeneous repositories, unresolved dependencies, or search systems that do not honor lifecycle states."},"adoption_authority_feasibility":{"score":4,"rationale":"The packet identifies the steward, artifact owners, and records or legal authorities and limits the pilot to reversible, owner-confirmed actions. Feasibility still depends on obtaining coordinated participation and resolving disputed classifications."},"evidence_readiness":{"score":4,"rationale":"A 60-day treated-versus-untreated portfolio comparison, explicit outcome classes, rollback conditions, and separate problem and intervention falsifiers provide a strong test structure. Sampling, classification reliability, metric calculations, and thresholds are not yet operationalized."},"safety_net_benefit":{"score":4,"rationale":"Reversible authority removal, preservation holds, dependency gates, audit logs, restore testing, and rollback reduce the risk that cleanup destroys institutional memory or breaks live dependencies. These safeguards themselves remain untested."},"scalability":{"score":3,"rationale":"Lifecycle states and repository controls could be reused across artifact classes, but owner review, exception handling, dependency mapping, legal coordination, and restoration testing may create substantial per-artifact or per-repository burden."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"Pre-register and run the stated 60-day comparison on one completed scenario portfolio and one untreated portfolio, including inventory, owner review, labeling, reversible archiving, retrieval-error measurement, effort tracking, and restoration tests.","confidence":"LOW","assumptions":["The portfolios are bounded and already accessible.","Existing staff can supply stewardship, owner review, and evaluation labor part-time.","No major repository integration or legal remediation is required.","The estimate is resource-equivalent and not a vendor quote."]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"Configure lifecycle metadata, permissions, search demotion, audit logging, dependency handling, restoration procedures, governance rules, and staff training for an initial repository deployment.","confidence":"LOW","assumptions":["An existing repository can be extended rather than replaced.","Lifecycle states and search behavior are configurable.","Most ownership and retention rules can be resolved without extensive records reconstruction.","Deployment is limited to one organization or repository environment."]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Launch the operating model across multiple foresight portfolios, including backlog classification, repository integration, records and legal review, change management, quality assurance, and evaluation.","confidence":"LOW","assumptions":["The organization has several portfolios and a material historical backlog.","Human review remains necessary for meaning, dependencies, and exceptions.","No bespoke enterprise repository replacement is included.","Scale, repository heterogeneity, and backlog size are not supplied in the packet."]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Ongoing stewardship, scheduled reviews, owner coordination, exception and hold management, restoration testing, search-quality checks, training, and outcome monitoring for one organizational deployment.","confidence":"LOW","assumptions":["Review volume is moderate and partly absorbed by existing roles.","Automation assists routing but does not determine validity or deletion.","Repository licensing and infrastructure changes are limited.","Recurring burden varies materially with artifact volume and ownership quality."]}},"research_burden":"HIGH","earliest_credible_horizon":"0_TO_3_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The authority ambiguity is clearly recognizable from the candidate, but prevalence, stale-artifact selection, decision influence, and review burden are all explicitly unsupported hypotheses requiring repository evidence."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"The candidate assigns lifecycle operations to a designated foresight repository steward, semantic validation to artifact owners, and preservation or destruction authority to records or legal stakeholders."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The candidate claims that artifact-level lifecycle governance will reduce stale-artifact selection or review time relative to an untreated portfolio and date-based manual archiving without unacceptable dependency or restoration failures."},"bounded_next_evidence_step":{"status":"YES","reason":"The sealed candidate specifies a 60-day pilot on one completed portfolio, an untreated comparison, owner-confirmed reversible archiving, named outcomes, halt conditions, and full rollback from an audit log."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"Hard deletion, hold overrides, age-only validity decisions, unresolved-dependency removals, and historical rewriting are excluded; authority roles and halt-and-restore conditions are explicit."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"The candidate bounds the pilot but supplies no repository architecture, artifact volume, backlog size, integration requirements, staffing availability, or organization-wide rollout scope, so implementation ranges remain assumption-sensitive."}},"blocking_evidence":["Repository sampling showing whether obsolete artifacts are actually mistaken for current guidance or create material review burden.","Evidence that lifecycle labels and search demotion change artifact selection in decision workflows relative to the untreated portfolio.","Owner availability and classification agreement sufficient to maintain lifecycle states without excessive disputes.","Demonstrated restoration, link preservation, and dependency integrity under reversible archiving.","Prior-art comparison with existing foresight repository, knowledge-management, and records-governance systems.","Repository-specific integration, backlog, compliance, and recurring stewardship requirements needed to refine cost and scalability."],"next_evidence_step":"Pre-register and conduct the stated 60-day pilot on one completed scenario portfolio, with an untreated portfolio as comparator: inventory artifacts, obtain owner-confirmed review-due or superseded classifications, apply only reversible labels and archive demotion, and compare stale-item retrieval errors, review effort, classification disputes, dependency failures, and restore success. Falsify the problem if baseline sampling finds consistently enforced authority states and no meaningful stale-item confusion; reject the intervention if it fails to improve selection or effort or exceeds preset dependency, restoration, or dispute thresholds.","research_questions":["How often do users retrieve or act on obsolete foresight artifacts as though they were current?","Which artifact classes require authority states, and which retain value without any monotonic decay assumption?","Do users and repository search functions consistently honor lifecycle labels and demotion?","What reviewer agreement is achievable for superseded, review-due, archived, held, and active classifications?","How much owner and steward effort is required per artifact and portfolio?","Can archived artifacts be restored with context, links, provenance, and dependencies intact?","What established repository, scenario-library, knowledge-management, or records-governance practices already implement the proposed combination?","What dispute, dependency-failure, and restore-failure thresholds should halt the pilot?","Do lifecycle controls disproportionately suppress dissenting or minority scenarios?","What repository architecture, backlog size, retention obligations, and staffing model determine deployment and recurring cost?"] ,"recommendation":"VALIDATE_PROBLEM_FIRST","uncertainty_constraints":["Problem prevalence and realized decision impact are unsupported hypotheses.","Stakeholder demand and willingness to fund or operate the intervention are unmeasured.","World novelty and incremental distinctiveness beyond the stated nearest rival are unmeasured.","Cost bands are resource-equivalent assumptions because system scale, artifact volume, and integration requirements are absent.","The analogy is limited because scenarios are possibilities rather than truth claims and older artifacts may gain longitudinal value.","Classification reliability, metric definitions, sampling, and halt thresholds are not fully specified.","Scalability depends on ownership coverage, repository configurability, dependency complexity, and legal or records requirements."],"closed_book_prior_art_boundary":"No conclusion is made about novelty, prevalence, market size, realized impact, or existing implementations. The packet labels prior art as unsearched and supports only comparison with its stated periodic date-based archive rival; external research is required before any broader distinctiveness claim."}