Workflows, Hooks & Webhooks
Connect lifecycle events to deterministic or agentic actions.
Primitive's target is one event-driven layer: workflows describe multi-step work, hooks intercept internal lifecycle points, and webhooks move events across system boundaries.
A workflow is the recipe, a hook is a place inside Primitive where something can react, and a webhook is the doorbell used by another system.
These mechanisms are related but should not be collapsed into one word. Hooks are local interception points, webhooks are external event transport, and workflows coordinate steps. All three should emit observable events and reuse the same execution/governance machinery rather than growing separate automation engines.
Hooks
Control already uses inbox-gate and lifecycle-hook concepts to ensure harnesses observe the same intake/control boundaries. Hooks should be explicit and versioned.
Webhooks
Webhook adapters should translate external events into Primitive event/trigger contracts and translate authorised Primitive events outward without making external systems an authority source by accident.
Workflow execution
Workflow steps may be deterministic or delegated to agents, but execution state, retries, authority and receipts need one inspectable model.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.