summaryrefslogtreecommitdiffstats
path: root/STATE-CURRENT.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-06 15:18:39 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-06 15:18:39 -0400
commit929646875d80408a21c642ca88ef70efbc0d736a (patch)
treedeb2946cc4407e4edcc6e3b56f37420e321acf40 /STATE-CURRENT.md
parent039daee13c5bac50919eff1ca26977ac49e37b06 (diff)
downloadopen-iov-929646875d80408a21c642ca88ef70efbc0d736a.tar.gz
open-iov-929646875d80408a21c642ca88ef70efbc0d736a.zip
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.
Diffstat (limited to 'STATE-CURRENT.md')
0 files changed, 0 insertions, 0 deletions