compatibility-evolution-work
Use this when a task can affect public or durable state: CLI, SDK exports,
package exports, schemas, database tables, workspace or global files, bridge or
runtime protocols, routes, agent instructions, skills, receipts, backups,
imports, exports, indexes, permissions, grants, approvals, audit, or Clawix
host state.
Procedure
- Run
claw search evolution compatibility migration rescue --json.
- Inspect current policy with
claw evolution show policy --json and
claw evolution verify --json.
- Classify each logical change as
additive, compatible,
migration_required, adapter_required, or breaking_requires_adr.
- Add or update a
docs/evolution/ record before changing a stable surface.
- Keep current implementation clean. Put old-version knowledge in migrators,
adapters, receipts, repair tools, or fixtures.
- For risky repair, deletion, movement, external mutation, secret access,
report submission, or large backup thresholds, require explicit approval.
- Preserve the Clawix survival core: launch, chat, and repair before
non-critical UI or subsystem behavior.
- Validate with
claw evolution verify --json, the focused tests, and
scripts/evolution-governance-check.mjs.
Constraints
- Do not make legacy branches part of the main current-model code path.
- Do not mutate external sources or copy them wholesale.
- Do not include prompts, secrets, sensitive payloads, or full local paths in
receipts or reports.
- Do not close work that touches a stable surface unless the ledger, tests, and
rescue implications have been reviewed.
1---2name: compatibility-evolution-work3description: Add or change stable public state, contracts, routes, migrations, adapters, rescue behavior, or compatibility-sensitive surfaces through the evolution ledger.4---56# compatibility-evolution-work78Use this when a task can affect public or durable state: CLI, SDK exports,9package exports, schemas, database tables, workspace or global files, bridge or10runtime protocols, routes, agent instructions, skills, receipts, backups,11imports, exports, indexes, permissions, grants, approvals, audit, or Clawix12host state.1314## Procedure15161. Run `claw search evolution compatibility migration rescue --json`.172. Inspect current policy with `claw evolution show policy --json` and18 `claw evolution verify --json`.193. Classify each logical change as `additive`, `compatible`,20 `migration_required`, `adapter_required`, or `breaking_requires_adr`.214. Add or update a `docs/evolution/` record before changing a stable surface.225. Keep current implementation clean. Put old-version knowledge in migrators,23 adapters, receipts, repair tools, or fixtures.246. For risky repair, deletion, movement, external mutation, secret access,25 report submission, or large backup thresholds, require explicit approval.267. Preserve the Clawix survival core: launch, chat, and repair before27 non-critical UI or subsystem behavior.288. Validate with `claw evolution verify --json`, the focused tests, and29 `scripts/evolution-governance-check.mjs`.3031## Constraints3233- Do not make legacy branches part of the main current-model code path.34- Do not mutate external sources or copy them wholesale.35- Do not include prompts, secrets, sensitive payloads, or full local paths in36 receipts or reports.37- Do not close work that touches a stable surface unless the ledger, tests, and38 rescue implications have been reviewed.
clawic