The frame builder

§8 says a frame is the canonical unit of intent: the request triad, its bindings, every stated constraint, its slots and a governing law. So here you assemble one. Set what it is for, who may act, which resource, which authority it carries, its horizon and its proof obligation — and the page composes the frame, shows every field it binds, and runs the chapter's own rules over it. A frame that is incomplete or contradicts itself is refused, with the field named and the fix given; the composed frame appears only when every check passes.

§8 Frames: rules 1–8, the four slot states, and the constraint-mapping table. The request dialect and the capability dialect are read from this repository's grammar modules at build time — the five legal cells and the five acts are not typed into this page.

Assemble it

What it is for Rule 2: the words as said, snapped to the request dialect. A word off the list is a parse error, never new vocabulary.
Who may act, and which authority The frame spends one act from gk.capability/v1 on the resource it binds. RFC §2 answers whether that principal holds it: explicit row, then derived, then the owner chain, then none.
Which resource Bindings are the concrete identifiers the request references. Rule 6 keeps the selection evidence for each resolved id.
    Constraints One per line, in the words they were said in. Rule 1 carries every one; rule 7 maps each to a primitive or keeps it in the unresolved collection.
    Its horizon Rule 6: every temporal reference resolves against an explicit timestamp and timezone. A by deadline is computed from them, never guessed.
    Its proof obligation Rule 7 and rule 3: the frame names the law that governs it and the evidence that would prove the act happened. Acceptance criteria are ALWAYS critical.
    Parameter slots Rule 3: every slot is critical or noncritical by schema; recipients, quantities, deadlines, scope, permissions and acceptance criteria are always critical. The state is the slot table's: bound, alternatives, absent, unsupported.

    What the frame records about itself Rule 6: the request schema version, the source span and the compiler revision.

    The verdict

    Every rule, over this frame

    CheckFieldStateWhat it found