# Changelog 2026-07-09 -- Stage 0 ratification: D-100..D-110 ADOPTED (DOCFIX-150)

No live infrastructure touched -- decision-record edits only. Closes Stage 0
of `docs/dc-dc-deployment-workflow.md`, the gate blocking real Phase-0/1/2
work since the DC-DC design was drafted this same day.

## Item

### 1. DOCFIX-150 -- Stage 0 decision ratification
FILES: `docs/design-decisions.md` (11 status-line updates + D-101
amendment + D-102 merge), `docs/dc-dc-buildout-design.md` (Section 10
rewritten as a ruling record, Section 3's Ceph gate annotated, stray
"Section D-102" cross-reference corrected to D-101), `docs/session-ledger.md`
(machine-derived block re-seeded, narrative entry).

WHAT: operator ruled on the buildout design's 6 redline items (via two
AskUserQuestion rounds, live) and on each of D-100 through D-110
individually, per this repo's own discipline ("present options, do not
implement" until ruled -- this delivery is the ruling, not a unilateral
implementation).

**Redline rulings:**
- Ceph replication factor: size=3 by default; size=2 only as an explicit,
  logged Phase-0 fallback if the measured disk budget doesn't fit -- never a
  silent choice.
- `tc netem` link profile: same-metro dark-fiber lean, confirmed; re-tune
  when a specific Roosevelt inter-DC target is known.
- D-102 (IPv6 tenant/MTU sub-policy) folds into D-101 (address plan); D-109
  (Vault posture) stays standalone, NOT merged.
- metal-admin: GAINS a ULA (IPv6) leg alongside its existing v4 -- this
  REVERSES the buildout design's own stated lean ("keep metal-admin
  v4-only"). A genuine ruling, not a rubber-stamp of the recommended default.
- COS (observability): per-DC only for VR1, confirmed (no Office1 roll-up).
- Per-DC artifact mirror sync topology: independent upstream pull per DC,
  confirmed (not one DC seeding the peer).

**Per-decision disposition, `docs/design-decisions.md`:**
- D-100, D-103, D-104, D-105, D-106, D-107, D-108, D-110: status flipped
  PROPOSED -> ADOPTED 2026-07-09 (operator ruling). D-100's netem/Office1-
  fiber sub-items, D-105's COS sub-item, and D-107's mirror-topology
  sub-item rewritten from "Open sub-item(s)" to "Sub-item(s) RULED," with
  the operator's specific answer recorded inline.
- D-101: status ADOPTED + AMENDED same day -- the family matrix's
  metal-admin line moved from "IPv4 retained" to the dual-stack group (the
  ULA-leg ruling); D-102's full decision body folded in as a new "Tenant/MTU
  sub-policy" section; the "Open sub-items" line narrowed to only the
  genuinely still-open NetBox literals (a NetBox-assignment task, not a
  ratification question -- already tracked as gap #3 in the deployment
  workflow's tooling gap register).
- D-102: status changed to `MERGED INTO D-101 (2026-07-09, operator
  ruling)`. Body text LEFT IN PLACE, per this repo's append-only
  decision-record discipline -- the entry is retained for numbering/history,
  not deleted; D-101 is now the current, authoritative text for this
  sub-policy.
- D-109: status ADOPTED, explicitly noting it was confirmed to stand alone
  despite D-102 folding into D-101 the same day (a real, considered
  distinction, not an oversight -- Vault/security posture is different
  enough from addressing to keep independently amendable).
- D-106's own open sub-item (cross-DC name resolution, not needed for VR1)
  was NOT one of the six items the buildout doc flagged for explicit
  redline -- adopted per its own stated lean along with the rest of D-106,
  noted plainly in the decision text rather than silently assumed.

VERIFIED, not just asserted: `bash scripts/ledger-scan.sh`'s "PROPOSED / OPEN
decisions" list no longer contains any of D-100 through D-110 -- only D-068
and D-071 remain (pre-existing, unrelated to this gate). `repo-lint.sh`:
0 fail / 1 documented legacy warn (unchanged). `tests/repo-lint` harness:
34/34 (unchanged -- no script logic touched, decision-record content only).

`docs/dc-dc-deployment-workflow.md`'s Stage 0 banner and summary table,
plus the companion visual tracker, updated to reflect Stage 0 CLEARED (see
the companion Artifact redeploy).

REVERT: `git checkout HEAD~ -- docs/design-decisions.md
docs/dc-dc-buildout-design.md docs/session-ledger.md` (re-opens Stage 0 --
not recommended; if a specific ruling needs reconsidering, amend that one
decision's entry instead of reverting the whole ratification).

## Next actionable step

Stage 0 cleared -- Stage 1 (Phase 0: vcloud host prep) and onward can now
proceed on runbook/tooling authorship without an open-decision blocker.
Real values still pending NetBox assignment (DC2's supernet, the org ULA
/48, per-DC GUA carve) and infrastructure access (a `tofu`/`qemu-img`/
ISO-tool-capable machine, a real vcloud host) remain separate, non-decision
blockers -- tracked in the tooling gap register, not this ratification.
