Skip to content

Releases

Workflow OS 0.3.0-preview.1 — Governed Execution and Continuity Preview

Workflow OS 0.3.0-preview.1 — Governed Execution and Continuity Preview Pre-release
Pre-release

Choose a tag to compare

View all tags
@rcs2153 rcs2153 released this 01 Nov 09:32
v0.3.0-preview.1
48403d6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Workflow OS 0.3.0-preview.1 moves the project from governance primitives to
composed, inspectable local execution.

The kernel now binds governed work to immutable run identity, current
authority, policy, checks, approvals, evidence, side effects, durable events,
reports, and lawful continuation.

Highlights

  • governed sequential multi-step local workflows;
  • proof-bound approval presentation and fresh-fact resume checks;
  • proportional governance with quiet capture, visible disclosure, blocking
    approval, and denial;
  • durable WorkReports and explicit create-only local report artifacts;
  • bounded existing-repository onboarding and workflow authoring;
  • filesystem, SQLite, and PostgreSQL preview state paths;
  • private trusted-host no-write execution compositions;
  • single-tenant no-write hosted alpha and optional OpenShell contracts; and
  • narrow GitHub PR-comment and managed draft-PR sandbox proofs.

The new first-run quiet-success path performs real bounded posture analysis,
runs authoritative project validation, and persists one local WorkReport.
Complete low-risk facts can proceed without an approval record; escalated work
still blocks on proof-backed approval.

Important Boundaries

This remains a preview. It is not:

  • production-ready or multi-tenant;
  • a general agent runtime or autonomous scheduler;
  • arbitrary shell or repository-command execution;
  • broad GitHub, Jira, CI, cloud, SaaS, or HTTP write support;
  • enterprise RBAC/IdP/policy administration;
  • a stable CLI JSON or persisted-state compatibility promise; or
  • Level 3/4 autonomy enablement.

Mock skills demonstrate kernel sequencing only. Hosted, OpenShell,
trusted-host, PostgreSQL, and provider-write surfaces are bounded alpha/proof
paths, not production support claims.

Read the full release notes, current product
contract, and known
limitations.

Please report bugs through GitHub Issues. Do not include credentials, private
provider payloads, raw logs, or sensitive repository content.

Loading

Workflow OS 0.2.0-preview.1 — Public Read-Only Integration Preview

Workflow OS 0.2.0-preview.1 — Public Read-Only Integration Preview Pre-release
Pre-release

Choose a tag to compare

View all tags
@rcs2153 rcs2153 released this 19 Jun 16:16
v0.2.0-preview.1
5931673

Workflow OS 0.2.0-preview.1 is a public preview of read-only integration capability for the local Workflow OS kernel.

This release demonstrates fixture-first and opt-in live read-only adapter contracts for:

  • GitHub read-only context
  • Jira read-only issue context
  • GitHub Actions / CI read-only run context

It is not production-ready. It does not include writes, reruns, dispatches, webhooks, OAuth, hosted operation, distributed workers, production backends, generic live adapter execution, domain packs, production telemetry export, or Level 3/4 autonomy.

What To Try

Build the CLI:

cargo build -p workflow-cli --bin workflow-os

Run fixture-backed examples:

target/debug/workflow-os --project-dir examples/github-read-only-review-context validate
target/debug/workflow-os --project-dir examples/github-read-only-review-context --mock-all-local-skills run ex/gh

target/debug/workflow-os --project-dir examples/jira-read-only-intake-quality validate
target/debug/workflow-os --project-dir examples/jira-read-only-intake-quality --mock-all-local-skills run ex/jira

target/debug/workflow-os --project-dir examples/ci-read-only-failure-summary validate
target/debug/workflow-os --project-dir examples/ci-read-only-failure-summary --mock-all-local-skills run ex/ci

Each example uses fixture-backed provider data and deterministic local mock handlers. They do not require live credentials and do not write to providers.

These examples pause for approval; see the RC1 Evaluation Guide for approve and inspect commands.

Live Provider Posture

Live provider tests are opt-in maintainer checks, not normal CI. Use read-only credentials only and follow the live-smoke runbooks.

Recorded smoke limitations:

  • GitHub live smoke exercised octocat/Hello-World repository metadata, not rcs2153/workflow-os.
  • Jira live smoke exercised issue metadata only.
  • GitHub Actions live smoke exercised workflow run metadata only.
  • Jira sandbox token rotation was recommended because a sandbox token was pasted into the local evaluation thread before smoke execution.

Security And Privacy

Do not include tokens, authorization headers, private keys, full private issues, full pull requests, raw CI logs, or raw provider payloads in specs, issues, screenshots, or bug reports.

Provider metadata can still be sensitive even when read-only. Redaction is deterministic preview redaction, not enterprise DLP.

Reporting Issues

Please include:

  • commit SHA
  • command run
  • fixture/mock/live mode
  • redacted output summary
  • expected vs actual behavior

Issues: https://github.com/rcs2153/workflow-os/issues

Full Notes

Full release notes: https://github.com/rcs2153/workflow-os/blob/main/docs/release/0.2.0-preview.1_RELEASE_NOTES.md

Known limitations: https://github.com/rcs2153/workflow-os/blob/main/docs/release/V0_KNOWN_LIMITATIONS.md

What Comes Next

Likely follow-ups:

  • parameterized GitHub live smoke target
  • broader opt-in live smoke coverage
  • continued adapter telemetry hardening
  • design work before any policy-gated writes, generic runtime adapter execution, or domain packs
Loading