Skip to content

Repository files navigation

Workflow

Workflow is the standalone, generated Rust service for user-maintained workflow definitions and immutable revisions. Authors edit draft directed acyclic graphs, publish canonical snapshots, and activate an owned revision. Tenant, authority, and optional realm come only from Identity.

Current status

Version 0.3.0 replaces the former WorkflowId placeholder. The ESS model, runtime annotations, generated WorkflowClient, Identity-authenticated HTTP server, OpenAPI, Connector contribution, and conformance scenarios are one deterministic package rooted at service.yaml. Service SDK also generates the executable host, durable SQLite lifecycle, ESS component/build/ runtime IR, BuildKit graph, and configuration-neutral Helm chart. There is no handwritten host, Dockerfile, service/client adapter, or compatibility path for the predecessor or the 0.1.0 crate.

Semantic node kinds are closed to compute, read, call, judge, wait, invoke, emit, and complete. Layout coordinates remain a product concern and are not persisted in semantic graphs. All mutations carry optimistic concurrency and idempotency. Nodes must be disconnected before removal; connections refuse missing endpoints, self edges, duplicates, and cycles. Publishing freezes ordered node/edge data with a deterministic digest; published revisions are never edited.

The HTTP resource audience is exactly urn:b10x:workflow. Reads require workflows.read, while draft authoring, publishing, and activation require workflows.manage. Tenant library reads use verified conjunctive scope facts without conferring aggregate ownership; every mutation remains owner-bound. Verification and exact scope authorization happen before operation JSON is decoded.

Build and validate the boundary that exists today:

task check

Execution, triggers, schedules, leases, cancellation, and revision deletion remain planned.

Documentation

Workflow documentation · Start · Ecosystem · Impact · Releases

About

Experimental Rust domain model for workflow definitions and immutable revisions; service transport, persistence, triggers, durable runs, leasing, cancellation, and evidence remain planned.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages