beads-schema

Bead workflow execution decomposes tasks into discrete units with explicit dependencies and verification steps. You need it when coordinating complex execution chains that require deterministic progression, state tracking, and end-to-end traceability to guarantee quality.

To define a bead, complete its required fields: Objective, Files and Touch Points, Dependency Links, Verification Commands, and Traceability. This structure establishes deterministic execution by binding each bead to explicit dependencies and validation steps.

The bead state model recovery semantics handle blocked states and crashes by enforcing robust progression rules. It specifies state transitions and recovery primitives like bd lock, bd pin, and bd slot to safely resume or roll back stalled workflows.

Available bead types include Standard, Formula, Molecules, and Wisps. These types combine with gate beads and coordination primitives to enable flexible, safe orchestration across complex task chains with varying execution requirements.

Yes, bead schema supports designing complex tasks as chains of beads with explicit dependencies and verification steps. It enforces traceability through Spec ID and dependency links, guaranteeing end-to-end quality across the entire workflow lifecycle.

Bead schema requires all required fields—Objective, Touch Points, Dependencies, Verification Commands, Traceability, and Spec ID—to be explicitly defined. Workflows lacking these fields cannot enforce deterministic execution, state recovery, or coordination primitives.