diff --git a/docs/changelog-20260724-stage5-committee-fork1.md b/docs/changelog-20260724-stage5-committee-fork1.md index 157aaf3..c465909 100644 --- a/docs/changelog-20260724-stage5-committee-fork1.md +++ b/docs/changelog-20260724-stage5-committee-fork1.md @@ -269,6 +269,20 @@ the subcarve as open. **Revert:** `git revert ` -- single-file text change, no behavioural effect. +## Item 17 -- DOCFIX-203: mark D-134's superseded original band table in place + +**What:** added a `**SUPERSEDED ... do NOT use these bands**` marker immediately above the +ORIGINAL D-134 band table in `docs/design-decisions.md` (control .10-.19 / compute .20-.49 / +storage .201-.254), pointing at the authoritative 2026-07-23 AMENDMENT (contiguous: .4-.49 +utility, .50-.99 VIP, .100-.200 nodes, .201-.254 dynamic). Original kept as history. +**Why:** the amendment header says it supersedes the original, but the original table carried +NO in-place marker -- a reader grepping `D-134` hits the original first and gets the rejected +bands. The Chat seat did exactly this 2026-07-25 (one read from a false discrepancy), and the +band-modelling this coupling (D-136) must do reads these bands. Committee-confirmed. +**Verify:** `awk '/## D-134:/,/## D-134 -- AMENDMENT/'` shows the marker before the first +table row. +**Revert:** `git revert ` -- single text addition, no behavioural effect. + ## Next (not done this session; gated) Commit+push this batch (GA-R5: rulings land before dependent work). Then, each diff --git a/docs/design-decisions.md b/docs/design-decisions.md index 524bad0..7b1b80b 100644 --- a/docs/design-decisions.md +++ b/docs/design-decisions.md @@ -4604,6 +4604,11 @@ **Decision.** On every VR1 DC plane (/22), the LAST-OCTET bands are: +**SUPERSEDED by the 2026-07-23 AMENDMENT below (DOCFIX-203) -- do NOT use these bands. The +CONTIGUOUS table under `## D-134 -- AMENDMENT (2026-07-23)` is authoritative (.4-.49 utility, +.50-.99 VIP, .100-.200 nodes [control .100-.119 / compute .120-.149 / storage .150-.200], +.201-.254 dynamic). This original is kept only as the record of what was rejected and why.** + | Band | Purpose | |---|---| | .1-.9 | infrastructure: .1 gateway (routed planes), .2 rack, .3 DNS forwarder (metal-admin); .4-.9 RESERVED for future per-DC utility/infra nodes (D-131 sub-4 / D-132 context) |