site: 2026-10-30 wiki refresh - new Project Goals, Performance and Interfaces and Stability pages; GSP explainer expanded (bare-metal behaviour + the two emulation modes); graphics pages (Graphics Execution, OpenGL, Vulkan, DirectX) with two new diagrams; status refresh across 15 pages; canonical docs updated (README status table, purpose-and-scope, performance contract); published to open-iov.org (67 pages, 0 problems)

1 files changed, 14 insertions, 6 deletions

diff --git a/wiki/System-Overview.md b/wiki/System-Overview.md
index 3f2d3e2..685926c 100644
--- a/wiki/System-Overview.md
+++ b/wiki/System-Overview.md
@@ -7,7 +7,7 @@
 > and [`../docs/03-architecture/10-interaction-and-scheduling.md`](../docs/03-architecture/10-interaction-and-scheduling.md)
 > for the full picture); the docs tree wins on disagreement.
 
-Status: 2026-10-12, tree `master @ 2f066727`. Tags: `[live]` proven with the
+Status: 2026-10-30, tree `master @ b4930168`. Tags: `[live]` proven with the
 stock guest driver; `[gated]` implemented default-off; `[wip]` partial;
 `[wall]` current blocker; `[target]` designed end state.
 
@@ -32,8 +32,10 @@ EMULATE  (software; the guest expects virtual hardware)
 PASS THROUGH  (real hardware; correctness and performance)
   GPU memory: guest VRAM objects backed by real VRAM       [target]
   page tables / GMMU state used by the GPU                 [wip]
-  channel execution: guest push buffers on real channels   [gated/wall]
-  compute (CUDA) and, later, 3D/video work                 [wip/planned]
+  channel execution: guest push buffers on real channels   [wip]
+  compute (CUDA) kernel launches on the real engine        [live]
+  3D graphics method streams on the real engine            [wip]
+  rendered 3D pixels / video work                          [wall/planned]
   DMA, completion and fault interrupts relayed to the guest
 ```
 
@@ -130,9 +132,15 @@ RPC from the guest to "firmware":
    payload round-trips).
 5. CE-class copies are forwarded to the physical copy engine (default off)
    with engine-authored semaphore releases and a fault relay. For GR
-   (graphics/compute), a forwarded guest launch reaches the front-end but the
-   engine has not executed it yet — the current frontier
-   ([`Execution-Frontier.md`](Execution-Frontier.md)).
+   (graphics/compute), forwarded guest CUDA launches execute on the engine
+   with engine-authored completions relayed to the guest, and graphics
+   method streams execute in two lanes
+   ([`Graphics-Execution.md`](Graphics-Execution.md)); rendered 3D pixels are
+   the graphics frontier ([`Execution-Frontier.md`](Execution-Frontier.md)).
+6. On the graphics side, the X server and GLX come up on the emulated vGPU
+   with the stock driver (`glxinfo` reports the NVIDIA renderer); the guest
+   Vulkan pipeline runs end to end; rendered (non-black) frames are the open
+   frontier ([`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md)).
 
 ## 6. Where the detail lives