Repository navigation
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. Genericproceedandcontinue
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.