dds

# Migration to 0.6.0 — modes, the instrument, claim files

Mechanical steps, in order. The firmness contract applies: reshape
structure; never touch a human's content bytes — stop and surface any
conflict.

## 1. Skill surface (informational — APM applies it)

`/dds-identify` → `/dds-sync` (survey + stubs, now instrument-backed,
with the offered improve continuation). `/dds-maintain` →
`/dds-upgrade` (this skill; structural enforcement moved to `/dds-sync`,
verdicts to the new `/dds-check`). Repo references to the old skill
names (`AGENTS.md`, `CLAUDE.md`, docs prose) are rewritten to the new
ones.

## 2. New canon file

Install `claim-files.md` → `docs/claim-files.md` (verbatim; three-way
rules apply on any later upgrade).

## 3. Canon reconcile

`docs/registers.md` gains the **Judgmental-structured** claim mode;
`deriving-from-code.md`'s carried copy gains **Witnessed drafts
(v0.6)**. Both arrive through the standard three-way merge.

## 4. Claim-file scaffold

Create `docs/registers/` (and `docs/registers/subjects/`) if absent —
empty directories with no seeded content: population is `/dds-sync`'s
job (run it after upgrading; it drafts per the carried witnessing and
proposing procedures).

## 5. The two-worlds split (informational)

`docs/adr/` is the human world — sync no longer stubs there; the new
`/dds-suggest-adrs` is the bridge. `docs/risks/` joins the register
world (machine-drafted, merge-ratified). Existing ADR stubs written by
v0.5 identify are untouched — they are already `Proposed` holes a human
owns.

## 6. CI hook (surface, do not apply)

Recommend adding a `/dds-check` invocation to CI (an agent step — the
skills are self-contained; there is no separate binary). Wiring CI is
a project decision — name it in the hand-off; do not edit workflows
unasked.