{"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__linguistics_semiotics","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"linguistics_semiotics","title":"Lifecycle-Governed Authority for Annotation Guidance","opportunity_summary":"Test whether identity-resolved lifecycle labels, dependency records, successor routing, and reversible discovery demotion reduce annotators' use of obsolete guidance while preserving reconstruction of historical annotations. The packet supplies a bounded mechanism and falsifiers, but the frequency and material effect of authority drift remain hypotheses.","adopter_authorizer":"Corpus owners and annotation-governance boards are the operational adopters and may change active status; records, compliance, or research-integrity authorities must additionally clear destruction, with accountable artifact owners and affected communities consulted where relevant.","scores":{"meaningful_impact":{"score":3,"rationale":"Preventing obsolete-rule use while preserving historical reconstruction could improve annotation consistency and reproducibility, but the packet explicitly leaves the frequency and material effect of authority drift unmeasured."},"stakeholder_pull":{"score":3,"rationale":"Annotators, corpus stewards, researchers, represented communities, and integrity stakeholders have plausible interests in clearer authority and preserved provenance, but no observed demand, complaints, adoption commitments, or prevalence evidence are supplied."},"incremental_advantage":{"score":4,"rationale":"Relative to immutable version history plus improved current-document ranking, the proposal adds explicit lifecycle classes, authority labels, dependency-gated disposition, quarantine, successor links, restoration tests, and governed exceptions. Whether those additions improve outcomes is still untested."},"distinctiveness_plausibility":{"score":2,"rationale":"The combination is coherently differentiated from the packet's nearest rival, but prior art and existing corpus-governance, documentation-versioning, and records-lifecycle practice are explicitly unsearched, so external distinctiveness is weakly supported."},"technical_implementability":{"score":4,"rationale":"A separate read-only index for at most 100 artifacts, status candidates, stable identities, successor links, and dependency tracing appears technically bounded and reversible. Implementability falls short of very favorable because identity resolution and dependency visibility are stated failure conditions."},"adoption_authority_feasibility":{"score":4,"rationale":"The packet identifies corpus owners and annotation-governance boards as status authorities and separately constrains destruction through records or compliance clearance. Distributed community authority, contested conventions, and unclear ownership could still impede decisions."},"evidence_readiness":{"score":4,"rationale":"The eight-week read-only pilot specifies a cap, baseline comparison, nearest-rival comparison, reconstruction outcomes, retrieval outcomes, annotation agreement, halt conditions, and rollback. Sampling representativeness and outcome definitions still require protocol work."},"safety_net_benefit":{"score":4,"rationale":"Separate-index labeling, no source alteration or deletion, dependency checks, holds, tombstones, successor links, restoration testing, and explicit rollback protect provenance and reversibility. Demotion and lifecycle metadata can nevertheless create visibility, bias, privacy, or community harms."},"scalability":{"score":3,"rationale":"Lifecycle metadata and class policies could transfer across projects, but scaling depends on stable artifact identity, visible dependencies, accountable ownership, local convention plurality, community governance, and sustained metadata maintenance."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"Eight-week read-only pilot on one annotation project covering at most 100 guidance artifacts, including inventory, identity resolution, separate-index labels, dependency tracing, baseline and nearest-rival comparisons, stakeholder review, reconstruction tests, and analysis.","confidence":"MODERATE","assumptions":["Existing repositories and search logs or controlled retrieval tasks are accessible without major procurement.","A small cross-functional team can contribute part-time labor.","No source artifacts or published annotations are changed.","The pilot does not require extensive legal review, translation, or new enterprise software."]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"Design and configure a production-capable lifecycle registry for one corpus program, including metadata schema, identity and successor-link migration, policy drafting, access controls, dependency checks, audit logging, restore procedures, and governance approval.","confidence":"LOW","assumptions":["The program contains materially more than 100 but not millions of guidance artifacts.","Existing repository and discovery systems expose usable integration points.","Most metadata can be curated with assisted workflows rather than fully manual reconstruction.","No custom enterprise records platform or major remediation of legacy annotations is required."]},"operational_launch":{"band_2026_usd":"50K_TO_250K","scope":"Launch across one corpus program, including artifact triage, owner adjudication, exception and hold review, discovery-presentation changes, training, community consultation where needed, reconstruction validation, and monitored rollout.","confidence":"LOW","assumptions":["Launch uses demotion, archiving, and successor routing rather than bulk deletion.","Contested and dependency-uncertain artifacts remain protected.","A moderate number of projects and stakeholder groups participate.","Integration and consultation complexity, rather than storage or equipment, drives cost."]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Annual operation for one corpus program, including stewardship labor, periodic revalidation, new-artifact classification, dependency maintenance, exception review, restore testing, audit response, training, software support, and stakeholder coordination.","confidence":"LOW","assumptions":["Governance is an ongoing responsibility rather than a one-time cleanup.","Review volume remains moderate and can be handled by part-time stewards and board members.","No unusually high litigation, erasure, security, or multilingual consultation burden arises.","Costs may fall below or exceed the band for very small or institution-wide programs."]}},"research_burden":"MODERATE","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The packet identifies observable coexistence of dated, incompletely labeled guidance and a plausible path to obsolete-rule use, but explicitly characterizes material effect in any given program as a hypothesis requiring a representative audit."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"Corpus owners and annotation-governance boards are identified as operational status authorities, while destruction additionally requires records or compliance clearance and accountable ownership."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal claims that lifecycle labels and demotion, beyond immutable history and search ranking, will reduce obsolete-rule retrieval or improve blinded annotation agreement without worsening reconstruction, missing references, or disputes."},"bounded_next_evidence_step":{"status":"YES","reason":"An eight-week read-only pilot on one project and at most 100 artifacts is capped, reversible, comparison-based, and includes explicit problem and intervention falsifiers."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The first step changes no source artifact, excludes deletion and contested or dependency-uncertain removal, respects holds and community objections, and has explicit halt and rollback conditions."},"implementation_cost_scope_and_range":{"status":"YES","reason":"The candidate bounds the pilot by duration, project, artifact count, and prohibited actions, allowing broad resource-equivalent ranges; later deployment ranges remain low-confidence because corpus scale and integration complexity are unspecified."}},"blocking_evidence":["A representative audit must establish that unlabeled legacy guidance is encountered and acted upon often enough to matter, rather than disagreement being driven mainly by current-rule ambiguity, task design, or training.","The pilot must show improvement relative to both baseline practice and immutable versioning with improved current-document ranking, not merely demonstrate that lifecycle metadata can be created.","Identity resolution and dependency tracing must be sufficiently complete to avoid broken reconstruction or missing-reference incidents.","Governance review must show that operational authority can be distinguished from enduring scholarly value without suppressing plural, minority-language, dialectal, genre-specific, theoretical, or historical conventions.","Scoped external research must determine whether the claimed lifecycle combination is already standard or materially anticipated in corpus governance, documentation versioning, or records management."],"next_evidence_step":"Run the authorized eight-week read-only pilot on one annotation project with at most 100 guidance artifacts: sample retrieval and use under the existing baseline, the nearest rival of immutable history plus improved current-document ranking, and the proposed separate lifecycle index and demotion treatment; compare obsolete-guidance retrieval, blinded annotation agreement, reconstruction time, missing-reference incidents, and stakeholder disputes. Falsify the problem if legacy artifacts are rarely encountered or inconsistency is primarily explained by current-guideline ambiguity, task design, or training; reject the intervention if it fails to outperform both comparisons or worsens reconstruction or disputes.","research_questions":["How often do representative annotators encounter and act on unlabeled legacy guidance, and what share of disagreement is attributable to it?","Can guidance artifacts be assigned stable identities, contexts, validity intervals, successor links, owners, and dependencies with acceptable completeness and inter-reviewer agreement?","Does the proposed treatment outperform both current practice and immutable versioning with improved current-document ranking on retrieval, blinded agreement, and reconstruction outcomes?","Which authority decisions belong to corpus owners, governance boards, represented communities, records officers, compliance staff, and research-integrity stakeholders?","How should lifecycle status distinguish current operational authority from scholarly, historical, dialectal, genre-specific, or community-specific validity?","Do demotion, quarantine, tombstones, or provenance metadata create disproportionate discoverability, privacy, erasure, or theoretical-bias harms?","What existing corpus-governance, documentation-versioning, and records-lifecycle practices anticipate the proposal's incremental components?","What staffing, integration, consultation, and recurring stewardship burden emerges beyond the capped pilot?"] ,"recommendation":"VALIDATE_PROBLEM_FIRST","uncertainty_constraints":["No external evidence establishes problem prevalence, stakeholder demand, market size, realized impact, or adoption readiness.","Prior art and external distinctiveness are unverified.","Cost bands are resource-equivalent planning ranges, not quotes or point estimates, and depend strongly on corpus scale, repository integration, ownership clarity, and consultation needs.","The analogy to technical layer decay is limited because older linguistic conventions may remain valid evidence, coexist with newer conventions, or regain relevance.","The pilot can establish local evidence but cannot by itself support broad cross-corpus scalability or general impact claims."],"closed_book_prior_art_boundary":"Prior art is unsearched and unverified: this closed-book assessment makes no claim about novelty, prevalence, existing implementations, market position, or superiority beyond the sealed candidate's stated comparison."}