Welcome to the Durable Workflow project! This project is dedicated to creating tools and libraries for developers to build and manage durable, long-running, persistent, distributed workflows.
The machine-readable product-train authority maps one Durable Workflow 2.0 choice to the exact seven-component tuple, every required distribution, and their ecosystem install commands. It also defines synchronized beta progression and the historical-prerelease policy.
This repository also owns the organization-level automation that records verified, immutable beta candidate tuples on GitHub. See the candidate record contract for the public artifact surfaces, source-identity checks, durable query paths, and recovery behavior.
It also records and observes channel-aware, pre-publication release plans. Publication remains repository-owned: each component discovers plans and resumes with only its own GitHub token and repository-local publication environment.
The protected beta authorization authority binds a product-owner decision to the exact proposed beta plan and its public qualification, candidate, conformance, continuity, and backlog evidence. Its append-only Git and GitHub Release record authorizes beta only; stable 2.0 has a separate decision boundary.
The stable 2.0 authorization authority evaluates a fixed release-critical conformance tier against one tagged seven-component artifact tuple. It publishes per-experiment and per-SDK-cell readouts, rejects incomplete or stale evidence, and reaches its protected human decision only after the evidence gate passes.
The scheduled workspace-unavailable continuity controller assembles those public authorities into an interruption-and-resume drill. Its append-only phase records bind GitHub issue intake, exact qualification, release recovery, public verification, and clean-runner conformance without a bootstrap workspace.
Published candidate tuples can be exercised by the independently runnable beta conformance workflow. Its retained GitHub Release evidence binds every experiment to the exact seven-component tuple, all required distribution identities, their source identities, and the conformance runner revision.
New public product work and the deliberately selected unresolved beta backlog use GitHub issue authority. Organization issue forms capture durable intake context, while a one-way lifecycle audit prevents an external mirror from reopening completed GitHub work.
Confirmed replay and payload-codec defects are also governed by an append-only regression-corpus contract. Its repository-local completion checks distinguish durable protocol evidence from tests that merely repeat implementation details.
The public target qualification policy also enforces the organization-wide Actions trust boundary: immutable action and container references, job-scoped credentials, isolated pull requests and caches, and reviewed artifact consumers.
The machine-readable public repository hygiene inventory records the maintained protected branches, the synchronized release train, and the cleanup completed for the 2.0 product surface.