hatiyildiz
a9913ed6be
docs(pass-62): PLATFORM-TECH-STACK §7 subsection order (Pass 23 carry-over); temporal third-cycle clean
PLATFORM-TECH-STACK §7 had broken subsection numerical order:
§7.1 → §7.4 → §7.2 → §7.3. Pass 23 added §7.4 (per-host-cluster
infrastructure overhead, categorization split) but inserted it
physically between §7.1 and §7.2 instead of after §7.3.
Reordered to canonical §7.1 → §7.2 → §7.3 → §7.4. The "Total mgt
cluster RAM" computation in §7.4 still correctly sums §7.1 + §7.4;
cross-reference in §7.1 ("its budget is in §7.4 below") still reads
accurately since §7.4 follows §7.1 in document order.
Methodology lesson #20: When inserting new subsections, ensure
placement is after existing higher-numbered subsections. Pass 23
added §7.4 logically but inserted physically out-of-order. New-cycle
audits should grep `^###\s+\d+\.\d+` and verify monotonically
increasing subsection numbers.
PLATFORM-TECH-STACK §1-§11 fourth-cycle deep re-scan otherwise clean:
- §1-§5 union-equality holds (Pass 40 + 55 confirmed)
- §6 multi-region mermaid diagram intact
- §10 bp-siem retention fix (Pass 23) intact
- §11 license posture: all Catalyst control-plane components are
Apache 2.0 / MPL 2.0 / MIT / BSD-3, no BSL
platform/temporal/README.md third-cycle clean — all three
architectural fixes intact:
- Pass 32 image: harbor.<location-code>.<sovereign-domain>/fabric/...
- Pass 35 DNS: temporal.<env>.<sovereign-domain>
- Pass 38 namespace: fabric (post-fuse rename)
Cross-namespace pattern (temporal control plane in `temporal` namespace,
customer workers in `fabric`) correctly modelled.