Workflow contracts
Workflow schema, version policy, and public contracts keep execution inputs and outputs stable.
- Workflow schema
- Connector manifests
- OpenAPI and event schemas
Product
Workflow runtime, not a generic automation facade.
Opora is organized around contracts, execution, and observability. The system is designed so workflow behavior, policy boundaries, and operator visibility remain coherent as the product evolves.
Orchestrator control
The orchestrator owns the run lifecycle and state transitions across nodes and execution states.
- State-machine ownership
- Run creation and cancellation
- Deferred queue and policy hooks
Runner isolation
Execution can be routed through isolated runtime boundaries with artifact- and policy-aware behavior.
- Local, warm-worker, and k8s adapters
- Artifact resolution boundaries
- Auditable execution flow
Auth and workspace model
User, workspace, project, process, and data-table surfaces support a product-facing control plane.
Billing and metrics surfaces
Usage, limits, reporting, manifests, and cleanup diagnostics make operations visible and controllable.
Docs and contracts split
Developer docs are intentionally published on opora.dev/docs, not buried inside the app surface.