---
name: refresh-solutions
description: Reconcile selected project solution records with current evidence, preserving accepted policy, historical reasoning, and unverifiable claims.
---

# Refresh Solutions

Establish selected records or topic, consumer knowledge convention and permitted
edit scope. Use the [project knowledge guide](../_shared/references/project-knowledge.md)
for retrieval and record evidence. A refresh is a bounded maintenance task,
not a repository-wide sweep or automatic store setup.

Inspect each selected record's claims, evidence, source references, last
verification and applicability. Compare with relevant current source,
accepted policy and deliberately supplied runtime artifacts. Age prompts an
inspection; it does not prove a record is wrong. Missing operational evidence
is an unknown rather than a false claim.

Distinguish descriptive drift from a policy conflict. Changed paths or names
can be repaired from current source. If implementation violates an independently
supported constraint, retain the constraint and report a potential product bug.
Do not rewrite the lesson to bless the violation or guess an undocumented
successor.

Choose a supported disposition: keep, update factual references, mark a
verification gap, propose a successor, or consolidate proven overlap. Check
inbound links and preserve unique reasoning before any restructuring. Similar
topics can have distinct retrieval value. Do not delete a record because code
moved, a source is unavailable or a lesson looks old. Retirement or deletion
requires supported supersession or loss of applicability and authorization
covering that action.

Apply only established factual repairs within scope. Preserve historical
context, cause, rejected alternatives and verification limits. Revalidate changed
claims and links. A new timestamp alone is not verification, and a broad policy
or guidance rewrite remains an owner decision.

Complete with reviewed records, evidence-based dispositions, actual edits,
conflicting policy or behavior, and unresolved verification. Product code,
root instructions, global memory, configuration and provider operations remain
outside this procedure unless separately assigned. Use
[capture-solution](../capture-solution/SKILL.md) for a newly verified non-obvious
lesson rather than inventing one during refresh.