3

docs/architecture/ARCHITECTURE_GUARDRAILS.md

@@ -6,6 +6,16 @@ This file exists so architecture documents have a stable guardrails reference
 inside `docs/architecture`. The operational Codex guardrails remain in
 `docs/codex/ARCHITECTURE_GUARDRAILS.md`.
 
+Transport clarification: references in this document to direct worker WSS and
+backend gateway fallback belong to the preserved historical RDP service
+baseline. They are not the active source of truth for inter-node transport.
+Current fabric node-to-node transport is QUIC-only and is defined by
+`docs/architecture/DISTRIBUTED_FABRIC_NODE_PROTOCOL_PLAN.md`,
+`docs/architecture/FABRIC_FIRST_TRANSPORT_AND_STRESS_PLAN.md`, and
+`docs/architecture/SECURE_ACCESS_FABRIC_TARGET.md`.
+Node survivability, recovery overlap, and no-manual-access repair rules are
+defined by `docs/architecture/FABRIC_NODE_SURVIVAL_AND_RECOVERY_POLICY.md`.
+
 ## 1. Preserve the Proven RDP Baseline
 
 The following are already proven and must remain stable:
@@ -16,8 +26,8 @@ The following are already proven and must remain stable:
 - detach without killing the remote session
 - reattach without recreating the remote session
 - takeover without recreating the remote session
-- direct worker WSS data plane
-- backend gateway fallback
+- historical direct worker WSS RDP path
+- historical backend gateway fallback for the RDP baseline
 - C++ RDP Adapter as the active RDP runtime
 
 Architecture clarification must not silently weaken this behavior.
@@ -191,6 +201,9 @@ Updates must support:
 - local update cache where approved
 - OS / architecture specific artifacts under signed release manifests
 - explicit migration bundles when data structures change
+- legacy recovery compatibility until the fleet is converged or explicitly
+  retired
+- multi-source artifact retrieval for stranded or NAT-only nodes
 
 Version Storage stores immutable release manifests, artifacts, hashes,
 signatures, compatibility metadata, provenance, and approved migration bundles.