summaryrefslogtreecommitdiffstats
path: root/docs/03-architecture/11-physical-backend-guest-wiring.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/03-architecture/11-physical-backend-guest-wiring.md')
-rw-r--r--docs/03-architecture/11-physical-backend-guest-wiring.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/03-architecture/11-physical-backend-guest-wiring.md b/docs/03-architecture/11-physical-backend-guest-wiring.md
index 943dd44..22d06ed 100644
--- a/docs/03-architecture/11-physical-backend-guest-wiring.md
+++ b/docs/03-architecture/11-physical-backend-guest-wiring.md
@@ -27,6 +27,14 @@
> forwarded-engine fault relay is live green, default off. The P6a trigger
> residual is fixed: triggers 6/7 re-translate at trigger time and use fresh
> scratch lines.
+>
+> **Update (2026-10-06): the frontier has moved.** A forwarded guest CUDA
+> launch now reaches the front-end (ring entry fetched, methods executed) but
+> the inline launch-descriptor (QMD) install has not been observed and no grid
+> has dispatched; context validity at dispatch is ruled out. The current wall
+> is the form of the forwarded launch method stream — the chain, evidence and
+> live investigation lines are in
+> [`../04-implementation/03-execution-frontier.md`](../04-implementation/03-execution-frontier.md).
> The physical backend itself is live: the module-owned
> GSP-RM completes initialization on the real TU104, serves the full
> static-config reply, and shuts down gracefully. The host resource-manager