v0.2.0

v0.2.0

Agent Workflows v0.2.0 adds explicit role, handoff, validation, and publication
guidance. It remains a pre-1.0 library of reusable operational artifacts.

Changes since v0.1.3

• Roles remain active until explicit project/user reassignment or an authorized,
  instantiated handoff transfers responsibility. Generic proceed and continue
  remain within the current role, authority, and completion boundary.
• When responsibility moves, the current role returns a ready-to-use handoff.
  Planning does not silently become Implementation, and Independent Review does
  not mutate candidates; corrections go to authorized Implementation.
• Implementation owns required local and hosted validation through a final
  result. Review readiness requires final success on the exact candidate.
  Pending, cancelled, unexpectedly skipped, unresolved, or failed checks leave
  the candidate incomplete; an open PR is not completion evidence.
• Exact approved-source content must be verified against its declared
  authoritative state before dependent mutation. Candidate labels alone are
  insufficient evidence of correspondence.
• Publication and Release Integrity (PRI), edition 1.0, is added as a governing
  source pinned to Standards Templates commit
  debd50926ea45c371a7b10237ef9aba1b3b04304. Existing source pins are unchanged.
• Publication guidance covers authorized-source correspondence, identity
  binding, verification of resulting state, and evidence-bounded claims.
  Observable state, including possible failed, interrupted, or premature
  exposure, is accounted for before replacing, retrying, withdrawing, correcting,
  or claiming completion. Source-derived PRI guidance remains distinct from
  workflow-local mechanics.
• Publication handoffs now carry authorized source state, publication identities
  and surfaces, correspondence, completion verification, and prior-exposure
  assessment. Return-of-control handoffs add a next-role instruction field.
• The README includes a latest-release badge.

Consumer impact and compatibility

No incompatible change to the documented authority or role model was found.
These compatible additions warrant a pre-1.0 MINOR increment under MAINTAINING.md.
Consumers using copied handoffs or integrations tied to table labels should
review the expanded publication fields and the replaced
Reviewed-to-publication correspondence label. Such integrations were not tested.

Update deliberately from an identified revision, preserve legitimate local
adaptations, and map the source references to actual project authority and scope.
Existing instantiated work does not update automatically. This release does not
propagate to consumers, adopt organizational standards, grant execution or
publication authority, or require four separate actors. It does not claim v1.0
maturity.

Source and validation

Release target: d288d778685de43aab306f4609773c460acbef32, the published canonical
commit. Its tree is identical to reviewed PR #12 candidate
5bd3e9fcf639f8d212d9b476226e5b0118777d3a:
b7d8aa46f977804cda870aafc8d901139f8fc8ed.

Changes since v0.1.3 comprise exactly:

• 2d571bd7073752e2681b1d25201f42c714ffbd9b: README latest-release badge (PR #10).
• d288d778685de43aab306f4609773c460acbef32: role, handoff, validation, source
  verification, and PRI integration (PR #12, including accepted F-1/F-2 corrections).

Canonical hosted validation succeeded in
run 36380581528.
Local release qualification results are retained in the separate preparation record.

Full comparison

v0.1.3

Pre-1.0 PATCH release clarifying governing-source records without changing workflow requirements.

• Replaced the general-purpose PROVENANCE.md with the purpose-specific GOVERNING-SOURCES.md. The new registry preserves all five live Standards Templates governing-source dependencies through immutable source pins and template editions.
• Governing-source links now use stable Standards Templates template IDs. The former project-repository-responsibility registry anchor is now project-repository-model.
• Repo-template alignment and history are no longer maintained as permanent provenance state. Creation authority lives in AGENTS.md, and reconciliation guidance lives in MAINTAINING.md.

Governing-source pins were not advanced: all five remain at Standards Templates revision df73ad31cdbb15210ad9670d669d3c567a79a1d3 and edition 1.0.

Workflow requirement meaning and strength did not change. Consumer authority semantics did not change: actual project authority controls instantiated workflows, and source references do not adopt standards for consumers. Previously instantiated handoffs remain valid against their recorded immutable Agent Workflows revision.

Consumers directly referencing library paths or fragments should account for PROVENANCE.md → GOVERNING-SOURCES.md and #project-repository-responsibility → #project-repository-model when deliberately updating to this release. Existing immutable references remain valid; no automatic consumer update is implied.

Included change: #9

v0.1.2

Correct stale release and source-reference documentation following the release-title update.

• Reconcile the design/governance baseline to standards-templates v1.1.1 at df73ad31cdbb15210ad9670d669d3c567a79a1d3; update all five immutable source links while preserving original derivation history. All five standards remain edition 1.0 with unchanged normative text.
• Reconcile the generic foundation to repo-template v1.2.1 at de0fd9206cf0448d50e0dd0f58f858eea46697ad, including required-check/host alignment guidance. All 21 exact-copy files match that basis.
• Replace stale future-first-release wording with current release discovery and retain the existing pre-1.0 policy.

No workflow semantics, validator implementations, live settings, or consumer authority change. This is a compatible documentation correction; no behavioral migration is required. Consumers can deliberately select this release for updated documentation. Existing tags and releases remain unchanged.

Validation: full repository checks, five local artifact regression tests, zero npm vulnerabilities, exact-copy comparison, unchanged source-text comparison, and live protection correspondence. See PR #7 for review and publication evidence.

v0.1.1

This PATCH release adopts the version-only GitHub Release title convention (v0.1.1) from repo-template v1.2.1 at de0fd9206cf0448d50e0dd0f58f858eea46697ad.

Maintenance instructions, the publication command example, title read-back verification, and the selective source-adoption record now agree. Pre-1.0 version semantics, release qualification, immutable annotated tags, and publication safeguards remain unchanged.

No canonical role profiles, handoff templates, workflow compositions, validator behavior, or governing-source references changed since v0.1.0. All 21 exact-copy files retain their original declared baseline. No consumer artifact updates are required. Historical tags and releases remain untouched.

agent-workflows v0.1.0

Initial pre-1.0 release of Agent Workflows: a library of reusable operational artifacts for bounded agent-assisted work.

• Four role profiles: Planning, Implementation, Independent Review, and Publication.
• Five handoff templates covering implementation, review, correction, publication, and return of control.
• A reviewed-change workflow composition that preserves responsibility, authority, evidence, and return-of-control boundaries.
• Explicit separation of source-derived guidance from workflow-local practice, with immutable source identities and exact/adapted/local provenance classifications.
• Repository qualification support: pinned validation tools, Markdown and link checks, regression tests, narrow local artifact checks, and CI; plus repository-local release-maintenance guidance.

This release is intended for deliberate use and feedback while the operational model is pressure-tested. Select an immutable revision, map the referenced sources to your actual project authority, and retain filled handoffs and execution evidence with the consuming project. Referencing these sources does not adopt standards for an organization.

The library is not an agent runtime, orchestration engine, or universal workflow-governance framework. The documented evidence gate for v1.0.0 remains in effect, including experience with a structurally different workflow composition.

License: CC0-1.0.

Release commit: 4f716ece97bd5a5ffe56facf1e42f449e28bfa45.