Templates

A1Core templates

This section covers the template and how an instance is raised from it. A template record has four parts, a declared document type, the slots an instance fills, the constraints every instance must satisfy, and a body in which every slot appears by name, as shown in template record. template and sibling shows how a template differs from a sibling instance. Raising an instance is a resolution in which each slot is substituted, a slot left unresolved is reported rather than guessed, and a value outside a slot's declared set is a violation. resolution lists the three outcomes. The record and workflow body are the grammar's own workflow template, read from its records rather than restated here.

The whole of Core templates

B1Coordination templates

This section covers the two templates for coordination between parties, surface protocol and decision protocol. They share one transport and have opposite lifetimes, as described in the board and the venue and shown in one transport. Each is a template record whose slots are drawn from closed sets, and it is raised into an instance by resolving them. two lifetimes shows why the fields of one never transfer to the other.

The whole of Coordination templates

C1Planning templates

This section covers the checklist template and the ten nodes of the loop that produce a checklist, each owning one kind of decision and closed by a gate, with the repair edge running between them, as shown in the ten nodes. checklist generator is the grammar's own checklist template record, and rendered checklist is the surface it emits. That surface carries what is true now and what remains, as described in derived state, and verification report is the verdict that travels with it.

The whole of Planning templates

D1Template families

This section covers the template families, which the families lists with the genesis question each answers. A family document has no runtime, so it is walked by the reasoning model its type declares, on the axis its type names, and an adapter performs the effects, as shown in type to artifact. Every node states its layer, its axis, the shape its decision yields, the contract it transforms and one evidence-bearing gate, as shown in one node beneath family header. The transitions are declared once in loop spine, and every node cites it. A template is used by walking its nodes as the spine declares, as described in execute the template, and walk or read shows the difference that decides whether its guarantees hold.

The whole of Template families

E1Agent templates

This section covers how a document expresses an agent, a verifier and a creator. An agent is a document of the agent type, a cognition walked on the reasoning axis, as shown in an agent, and a verifier is a document of the verification type, an epistemology walked on the verification axis, as shown in a verifier. A creator is a template that generates an agent, as shown in a creator, and the first two bodies are the grammar's own template records. What an agent is, why it is a walked loop and never a persona, and how a verifier earns trust are described in agents as executed contracts and verify the verifier, and where guarantees live maps where each guarantee is expressed.

The whole of Agent templates