Area guide · 12 packages · Compose an existing workflow
Workflows, jobs and automation
Compose repeatable work with explicit state, persistence, branching and operation-execution responsibilities.
What are you trying to do?
- Do I need workflow composition, a scheduler or a product module?
- How are extensions applied without breaking the graph?
- Where are state and effect execution supplied?
Why start with these packages
Suggested entry point
@lssm-tech/lib.workflow-composerUse the workflow registry, composition/validation and supplied-authority runner surfaces.
Suggested entry point
@lssm-tech/module.workflow-orchestrationInspect reusable boards, DAG/composer views, instance lifecycle and approval composition.
Suggested entry point
@lssm-tech/lib.jobsInspect the shared job scheduling/execution abstractions used by a host.
Suggested entry point
@lssm-tech/lib.sop-runtimeExplore the source runtime for living operating procedures and their generation context.
Practical steps
Step 01
Follow an existing graph
Record the entry, operation references, branch conditions and terminal outcomes. Inspect one extension and compare the composed graph to its base. Check which registry and source version resolve each step.
Step 02
Select state and execution adapters
Begin with the maintained memory/file or supplied adapter appropriate to the example. Identify the durable store and scheduler needed for the intended host before claiming restart or retry guarantees.
Step 03
Review interruption and recovery
Use existing tests or fixtures to inspect a failed step, repeated delivery and cancelled instance. Confirm that persisted state and returned results explain what happened and that retry behavior belongs to an explicit host/runtime contract.
Choose composition before scheduling
WorkflowComposer supplies tenant-aware composition, validation, a runner, state and persistence adapters. Its runner requires supplied operation execution and state persistence. A provider-specific scheduler belongs at a different boundary. The workflow-orchestration module adds reusable product-facing views and lifecycle/approval behavior. Start by deciding whether your task is to describe a graph, execute selected steps, schedule work durably, or present an operator view; that decision identifies which package to open first.
Keep graph changes deterministic
The maintained composer applies extensions in stable priority order, rejects duplicate injected step IDs and invalid anchors, and checks hidden-step overlays so they do not orphan the remaining graph. Metadata and annotations are merged into the composed result. These details matter when adding a tenant or product extension: inspect the resulting graph and its references, not just the added step. Keep step identity stable enough for state, traces and operator actions to refer to the same work.
Make execution and persistence visible
The canonical leaves include workflow context, SLA monitoring and SDK error conversion as well as validation and shared task validators. Choose the state store and operation executor the host actually supplies. A saved plan, a running instance, a retried step and a completed external effect are different states. Capture outcomes and failure paths at the point where callbacks or adapters return. For automation that can improve or regenerate itself, use the separate governed proposal and promotion lifecycle rather than replacing an active workflow silently.
Follow a practical path.
Follow an existing graph
Record the entry, operation references, branch conditions and terminal outcomes. Inspect one extension and compare the composed graph to its base. Check which registry and source version resolve each step.
Select state and execution adapters
Begin with the maintained memory/file or supplied adapter appropriate to the example. Identify the durable store and scheduler needed for the intended host before claiming restart or retry guarantees.
Review interruption and recovery
Use existing tests or fixtures to inspect a failed step, repeated delivery and cancelled instance. Confirm that persisted state and returned results explain what happened and that retry behavior belongs to an explicit host/runtime contract.
Packages in this area (12)
12 of 12 shown
- Open manual →
Headless controllers and operator view models for governed self-improvement
- Open manual →
Contained EVE runtime adapter for ContractSpec agents
- Open manual →
Generated transports for governed self-improvement
- Open manual →
Workflow DevKit compiler and runtime bridges for ContractSpec workflows
- Open manual →
Event bus and messaging primitives
- Open manual →
Background jobs and scheduler module for ContractSpec applications
Inspect the shared job scheduling/execution abstractions used by a host.
- Open manual →
Provider-neutral cross-domain orchestration semantics for autonomous-company workflows.
- Open manual →
Deterministic policy, compilation, and replay runtime for governed self-improvement.
- Open manual →
Living SOP generation, qualification, drift, health-trigger, and workflow compiler runtime.
Explore the source runtime for living operating procedures and their generation context.
- Open manual →
Tenant-aware workflow composition helpers for ContractSpec.
Use the workflow registry, composition/validation and supplied-authority runner surfaces.
- Open manual →
Headless orchestration for governed, goal-bound self-improvement.
- Open manual →
Workflow orchestration module — board, DAG, dashboard, composer, state-machine, instance lifecycle, approvals.
Inspect reusable boards, DAG/composer views, instance lifecycle and approval composition.
What connects to this area
Core contracts
A step refers to a known operation or event, with its declared outcomes.
Governance and approvals
Branching and planning must preserve the effect authority of each step.
Agents and context
Agents can propose or perform bounded work inside a declared workflow.
Delivery and infrastructure
Durable workers and execution environments implement operational concerns.