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, 15 insertions, 3 deletions

diff --git a/tools/site/pages/Main-Page.wiki b/tools/site/pages/Main-Page.wiki
index f91fc17..37a1eea 100644
--- a/tools/site/pages/Main-Page.wiki
+++ b/tools/site/pages/Main-Page.wiki
@@ -12,13 +12,14 @@ The only new component is one host kernel module (<code>vgsp.ko</code>), which i
 </div>
 
 == Start here ==
+* '''[[Project Goals]]''' — what Open-IOV is for, and the status of each goal.
 * '''[[Project Status]]''' — the honest, dated state of the project.
 * '''[[Install and First Run]]''' — fresh host to a stock guest driver in about half an hour.
 * '''[[System Overview]]''' — how Open-IOV works, in one page.
 * '''[[Documentation]]''' — the full index of this wiki.
 * '''[[FAQ]]''' — the questions we get asked most.
 
-== Project status (2026-10-20) ==
+== Project status (2026-10-30) ==
 {| class="wikitable"
 ! Area !! State
 |-
@@ -30,15 +31,24 @@ The only new component is one host kernel module (<code>vgsp.ko</code>), which i
 |-
 | CUDA userspace init and the driver-API smoke (ALL OK, 64-byte payload round-trips) || Working
 |-
-| Guest CUDA kernel execution on real hardware || Working — vector-add, matrix-multiply and transformer kernels run green on fresh boots; hardening and breadth in progress
+| Guest CUDA kernel execution on real hardware || Working — vector-add, matrix-multiply and transformer kernels run green on fresh boots; the battery's staged-transfer class and per-guest isolation are in progress
 |-
-| OpenGL / Vulkan, Windows guests, multi-tenancy, migration, performance || Not yet — multiple mediated devices (different emulated VRAM sizes) and multiple guests already coexist; per-guest execution isolation is in progress
+| 3D graphics: Xorg + OpenGL, Vulkan || In progress — the X server and GLX run on the emulated vGPU, the engine executes real GL method streams, and the guest Vulkan pipeline runs end to end; rendered (non-black) pixels are the current frontier — see [[Graphics Execution]], [[OpenGL]], [[Vulkan]]
+|-
+| Windows guests, multi-tenancy, migration, performance || Not yet — multiple mediated devices (different emulated VRAM sizes) and multiple guests already coexist; per-guest execution isolation is in progress
 |}
 
 The full story, with evidence and the current wall: [[Project Status]] and [[The Execution Frontier]].
 
+== Graphics ==
+* [[Graphics Execution]] — how guest 3D work reaches the physical engines
+* [[OpenGL]] — the stock guest GL stack on the emulated vGPU
+* [[Vulkan]] — the guest Vulkan pipeline on the emulated vGPU
+* [[DirectX]] — the Windows/DirectX target
+
 == Deep dives ==
 * [[System Overview]] — the architecture before any subsystem
+* [[Project Goals]] — mission, scope and goal-by-goal status
 * [[GSP and GSP-RM]] — the firmware interface we emulate
 * [[The vGSP Execution Plane (vEP)]] — how guest work becomes execution and completion
 * [[The Host Module (vgsp.ko)]] — the module internals
@@ -48,6 +58,8 @@ The full story, with evidence and the current wall: [[Project Status]] and [[The
 * [[UVM in the Guest]] — unified memory as a correctness oracle
 * [[Physical GPU Backend and Guest Wiring]] — how work reaches real hardware
 * [[The Execution Frontier]] — the leading edge, evidence-led
+* [[Performance]] — the cost model, tracing and improvement programme
+* [[Interfaces and Stability]] — which surfaces are contracts, which may change
 * [[Guest Driver Lifecycle: A Field Guide]] — boot to CUDA with real IDs and log signatures
 
 == Firmware interoperability ==