knowledge-refresh-and-drift-control

name	knowledge-refresh-and-drift-control
description	Use when auditing, refreshing, consolidating, replacing, or deleting stale skills, knowledge docs, templates, solved-problem lessons, provenance notes, or load-order references so the Super Build Kit stays current without parallel truth.
activation	Activate when the description trigger applies to the current task.
required_inputs	Task request, relevant repository context, constraints, and authority dependencies.
required_outputs	Skill-specific artifact, verification evidence, canonical verdict, and next action.
authority_dependencies	00_start_here/SOURCE_OF_TRUTH.md; 10_governance/APIVR_EXECUTION_LIFECYCLE.md; 10_governance/source_of_truth/Elite_Build_Goals_v3.md.
evidence_requirements	Executed checks or an honest Unknown, Not Run, or Blocked state for every material claim.

Knowledge Refresh And Drift Control

Use this skill to keep the kit's knowledge clean. Its job is to prevent stale guidance, duplicate lessons, and outdated references from quietly becoming false authority.

Do not preserve a file merely because it exists. Every durable skill, knowledge doc, template, and solved-problem lesson must remain accurate, routed, useful, and subordinate to the source-of-truth order.

Refresh Outcomes

Every reviewed item receives one outcome:

• Keep: still accurate, routed, and useful.
• Update: useful but stale, incomplete, or missing evidence.
• Consolidate: overlaps another file and should be merged into the stronger canonical file.
• Replace: concept remains useful but the current artifact is misleading or structurally wrong.
• Archive: no longer active, but provenance should remain.
• Delete From Active Use: unsafe, misleading, duplicate, or unsupported; preserve provenance when needed.

APIVR Placement

Use during audits, release retrospectives, source integrations, and scheduled maintenance.

1. Audit: inventory active files and references.
2. Plan: choose Keep/Update/Consolidate/Replace/Archive/Delete outcomes.
3. Implement: edit canonical files narrowly.
4. Audit Implementation: check activation paths and duplicate truth.
5. Verify Implementation: run doctor, link checks, and sample workflow dry-runs.
6. Re-Audit: record the refresh report and remaining risks.

Decision Flow

flowchart TD
  A["Review active knowledge item"] --> B{"Still accurate?"}
  B -- "No" --> C{"Concept still useful?"}
  C -- "No" --> D["Archive or delete from active use"]
  C -- "Yes" --> E["Update or replace"]
  B -- "Yes" --> F{"Duplicates stronger canonical file?"}
  F -- "Yes" --> G["Consolidate into canonical file"]
  F -- "No" --> H{"Referenced by load order, doctor, or relevant skill?"}
  H -- "No" --> I["Wire it or archive it"]
  H -- "Yes" --> J["Keep with evidence"]
  E --> K["Verify links and APIVR routing"]
  G --> K
  I --> K
  J --> K

Required Checks

• Authority: does the item conflict with APIVR or Elite Build Goals?
• Activation: can agents find it through 00_start_here/LOAD_ORDER.md or a relevant skill?
• Duplication: does it create a second source of truth?
• Evidence: are claims backed by Verified, Likely, Suspected, Unknown, Not Run, or Blocked states?
• Freshness: are provider, platform, cost, security, or workflow details date-sensitive?