dds

# 0.14.0 — the carried meta-register lands (issue #39)

`dds upgrade` now installs the framework's own meta-risks
(dds-design-record-staleness, dds-un-assessed-change,
dds-coverage-blindness, dds-unratified-drift) and their carried
strategy ADRs into docs/risks/ and docs/adr/. Nothing to author: they
arrive covered, closed, and outside the judged corpus.

## Steps

1. Run `dds upgrade` — the meta files land; re-run `dds`: the walk
   gains four covered meta-risks.
2. Fill the local slot in `docs/adr/dds-assess-change-impact.md`
   (`<!-- dds-local triggers -->`): what counts as a significant
   change IN THIS REPO. Slot content is yours; it survives upgrades
   and is never drift.
3. If this repo authored its own version of the same rule (e.g. an
   `assess-change-impact-*` ADR): move its trigger list into the
   carried ADR's slot, quote any non-trigger content it carried in
   the PR, and DELETE the local file — inherited rules are not
   re-authored. Point its old `Concern:`/`Risk:` consumers at the
   `dds-*` stems.