From 929646875d80408a21c642ca88ef70efbc0d736a Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Tue, 6 Oct 2026 15:18:39 -0400 Subject: docs: add the GR compute-launch frontier page and align execution status across the tree New page docs/04-implementation/03-execution-frontier.md describes the chain that must fire for a guest CUDA launch (guest push -> GPFIFO/front-end -> inline launch-descriptor install -> engine read/dispatch -> completion), where the leading edge is (the descriptor install path), how we know (front-end vs engine-authored observables and their limits), what is exonerated (context validity at dispatch, destination window mapping, fetch alignment, shared-buffer rule, parenting), the ranked issues (verbatim prelude targets, missing descriptor-virtualization control, sentinel hygiene), live investigation lines and labelled theories. Align every page that still said GR execution is blocked on engine-context validity to the current frontier, and add the new page to the README reading order (row 15, later rows renumbered). Docs only; no code. --- docs/09-reference/glossary-and-faq.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'docs/09-reference') diff --git a/docs/09-reference/glossary-and-faq.md b/docs/09-reference/glossary-and-faq.md index 1668e35..248bf83 100644 --- a/docs/09-reference/glossary-and-faq.md +++ b/docs/09-reference/glossary-and-faq.md @@ -99,7 +99,10 @@ it where available. It is part of the multi-tenancy work. **How fast is it?** No published numbers yet: copy-engine-class work forwarding and engine-authored release + fault relay are implemented but default off, and GR/kernel execution -is still the open frontier; even the initialization path has not been measured +is still the open frontier (a forwarded guest launch reaches the front-end but +the inline launch-descriptor install has not been observed — see +[`../04-implementation/03-execution-frontier.md`](../04-implementation/03-execution-frontier.md)); +even the initialization path has not been measured under the project's methodology. Any performance claim will come with the methodology and the measurements together (see [`../05-operations/01-performance-correctness-security.md`](../05-operations/01-performance-correctness-security.md)). -- cgit v1.2.3