3

docs/architecture/MESH_ROUTING_RUNTIME_IMPLEMENTATION_PLAN.md

@@ -3,7 +3,7 @@
 Status: Stage C17 planning completed. Stage C17A synthetic mesh runtime
 skeleton, Stage C17B route health/failover probes, Stage C17C relay semantic
 hardening, Stage C17D non-production test-service path experiment, Stage C17E
-live node-to-node synthetic HTTP transport skeleton, Stage C17F scoped
+historical live node-to-node synthetic HTTP transport skeleton, Stage C17F scoped
 synthetic route config boundary, Stage C17G Control Plane scoped synthetic
 config read boundary, Stage C17H deployed multi-agent synthetic config smoke,
 Stage C17I production forwarding gate, Stage C17J production envelope
@@ -44,8 +44,9 @@ invalidation. C17C added synthetic relay validation, per-channel bounded
 queues, QoS dequeue order, telemetry-only drop/backpressure, and reliable
 fabric/control rejection behavior. C17D added one bounded `synthetic.echo`
 test-service path over direct, single-relay, and forced fallback routes. C17E
-added real HTTP peer transport and a disabled-by-default node-agent synthetic
-endpoint/smoke harness for direct and single-relay synthetic traffic. C17F
+added one historical real-HTTP peer transport experiment and a
+disabled-by-default node-agent synthetic endpoint/smoke harness for direct and
+single-relay synthetic traffic only. C17F
 added scoped synthetic peer/route config loading and synthetic route-health
 link observation reporting. C17G added the Control Plane read boundary for
 node-scoped synthetic mesh config. C17H proved that boundary in a deployed
@@ -596,10 +597,12 @@ C17H implemented a deployed multi-agent synthetic config smoke on
 VPN/IP tunnel work remains a separate C18 track and must not be mixed into
 C17 mesh runtime work.
 
-## 15.4 C17E Result
+## 15.4 C17E Historical Result
 
-C17E implemented live node-to-node synthetic HTTP transport while preserving
-the production forwarding kill-switch:
+C17E implemented a historical live node-to-node synthetic HTTP transport
+experiment while preserving the production forwarding kill-switch. This result
+is retained only as test-history context; it is not the active transport
+direction for the fabric runtime:
 
 - `HTTPPeerTransport` maps explicit peer node IDs to synthetic HTTP endpoint
   URLs.
@@ -613,6 +616,13 @@ the production forwarding kill-switch:
 - `/mesh/v1/forward` remains disabled.
 - no production service traffic is authorized.
 
+Current direction:
+
+- active fabric runtime transport is QUIC-only
+- synthetic HTTP motion is historical test-only context
+- production forwarding/runtime acceptance must use QUIC route execution rather
+  than HTTP peer transport
+
 Verification:
 
 ```powershell
@@ -888,9 +898,11 @@ runtime. Stage C17A implements the first narrow runtime skeleton for synthetic
 Fabric messages only. Stage C17B adds route health/failover observations using
 synthetic Fabric messages only. Stage C17C adds relay semantic hardening for
 synthetic channel classes only. Stage C17D adds one bounded non-production
-`synthetic.echo` service-path experiment only. Stage C17E proves live
-node-to-node synthetic HTTP transport using real local endpoints only. Stage
-C17F proves scoped synthetic config loading and route-health reporting only.
+`synthetic.echo` service-path experiment only. Stage C17E proves one
+historical synthetic HTTP carrier experiment using real local endpoints only;
+it is test-only and not representative of the active QUIC fabric runtime.
+Stage C17F proves scoped synthetic config loading and route-health reporting
+only.
 Stage C17G proves Control Plane scoped synthetic config read/consume only.
 Stage C17H proves deployed multi-agent Control Plane synthetic config
 consumption and synthetic route-health reporting on `docker-test` only.