← all sampled attempts · show highlighted in source
docs/spec-fabric-pe-temporal.md, lines 473–480
The CGRA execution-plan importer consumes the same projected logical queue, its complete consumer set, allocation-unit ordinal, and entry capacity. Its runtime reserves every distinct unit in one ingress match group before requesting the selected enqueue actions, commits all matching queue tails together, and retires one physical queue head only on the common consumer handshake. Software channel storage is only the dense per-consumer token view of those physical queues; it cannot multiply physical occupancy, impose a one-token default, or bypass shared-unit occupancy and Fabric grant policy.
blocked generator source gap
No shown documentation defines the CGRA execution-plan record shape itself (its fields for projected logical queue, consumer set, allocation-unit ordinal, and entry capacity) or how a legal plan input is spelled for the importer; the shown text only defines the Fabric-side projection the plan must preserve. | No shown text defines the importer's failure/refusal behavior when a plan violates the shared-unit occupancy or grant policy, so the outcome for an ill-formed plan is undetermined.
| input generator | unrun |
|---|---|
| output condition | unrun |
| native evaluation | unrun |
obligation coverage: not measured / no validated evidence · code coverage: not measured / no validated evidence · coverage-preserving minimized case: not measured / no validated evidence
command.json · stderr.txt · stdout.txt · syntax-hashproof.json · anchor-response.request.json · anchor-response.txt · anchoring.json · claim.json · context.json · outline-response.request.json · outline-response.txt · sections.json · breadth-06-syntax.toml