Skip to content

v0.0.2 — POC baseline (alpha)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@benvdbergh benvdbergh released this 13 Apr 22:31
· 71 commits to master since this release
v0.0.2
8f93d9b

v0.0.2 — 2026-04-14

Summary

This tag marks the POC baseline for the Agent Workflow Protocol proof-of-concept: the repository contract (RFCs, schema, examples), the @agent-workflow/engine package on npm, deterministic conformance coverage, MCP stdio hosting, and the lighthouse demo workflow. This is an alpha cut for evaluators and integrators, not a production readiness statement.

Features (POC scope)

  • POC execution contract and artifacts: RFC-aligned workflow definition schema, golden fixtures under examples/, and docs/poc-scope.md as the authoritative POC surface.
  • Core durable execution engine: validation entrypoint, append-only command/event history, linear runner, and full POC walker behavior aligned with the subset.
  • Deterministic replay and checkpoints: replay-oriented execution semantics for the POC engine milestone.
  • MCP stdio integration surface: workflows-engine-mcp for MCP-capable hosts; see docs/architecture/mcp-stdio-host-smoke.md and the lighthouse MCP walkthrough.
  • Conformance harness and CI gate: npm run conformance with deterministic vectors; CI validation for workflow fixtures.
  • Lighthouse demo workflow: reference customer-routing workflow and companion traces for demos.
  • Alpha release readiness: versioning policy, release notes, and governed npm publish workflow (manual dispatch).

npm package

Published as @agent-workflow/engine@0.0.2. For installs that follow the documented operator path, prefer an explicit version or the alpha dist-tag (see docs/releases/alpha-release-notes.md for npx -p examples with workflows-engine / workflows-engine-mcp).

Known limitations

  • POC node types remain intentionally narrow (start, end, step, llm_call, tool_call, switch, interrupt). Types such as parallel, agent_delegate, subworkflow, wait, and set_state are out of scope for this milestone.
  • Trace companion files under examples/ are narrative companions and are not schema-validated executable inputs.
  • Contracts and naming are pre-1.0; see docs/releases/alpha-versioning-and-release-commit-flow.md for SemVer and tagging conventions.

Upgrade notes

  • Align local verification with CI: npm run validate-workflows and npm run conformance from the repository root.
  • Node: engine declares engines.node >=22.5.0; repository CI currently exercises Node.js 24 on GitHub Actions.
  • Use canonical JSON as execution input; YAML is fine for authoring if normalized to JSON before validation or run.

Links

Assets 2
Loading