Specifications

Authoritative markdown specifications in the repository. Prefer the illustrated site pages where they exist; open the GitHub source when you need to edit or cite the canonical text.

Workflow and activity YAML shapes are also defined by the generated schema reference (from Zod sources). When a model page and a prose spec disagree on technique anatomy, the technique protocol wins.

Architecture models

SpecificationSummaryOn-site
architecture.md Hub for the architectural models that govern server and agent interaction. Overview
dispatch-model.md Three agent layers — meta orchestrator, workflow orchestrator, and activity workers — and how work is spawned and resumed. Dispatch
checkpoint-model.md Just-in-time checkpoints: yield bubble-up, presentation, response timing, and resume with recorded effects. Checkpoints
state-management-model.md Deterministic transitions: the variable bag, checkpoint and worker mutations, and conditional branching. State
artifact-management-model.md Workspace isolation, planning folders, artifact naming, and the server-synthesized artifacts contract. Artifacts
resource-resolution-model.md Technique and resource resolution: :: paths, bundling, lazy-loaded reference material, and the meta/ fallback. Resolution
workflow-fidelity.md Enforcement layers — manifests, traces, seals, and schema validation — that keep agents on the defined path. Fidelity

Authoring contracts

Start here when you define or change workflows. Read the plain-language openings in each document before the formal sections. Generated wire shapes: schema reference.

SpecificationSummaryRelated
orchestra-specification.md Grammar and semantic constraints for workflow primitives — activities, steps, decisions, and loops — in the Orchestra definition language. Workflows
technique-protocol-specification.md Normative contract for technique files: capability, inputs, outputs, protocol, rules, :: addressing, composition, and delivery. Resolution
schemas/README.md Schema guide for authoring workflow definitions: manifest shapes, activity files, conditions, and validation conventions. Generated schemas