Public documentation v0
Kanban workflow
How Software Factory tasks move from scope to verified output.
Lifecycle
The standard flow is: PM scopes the work, builder implements only the scoped change, reviewer verifies independently, publisher packages public artifacts after gates, docs updates public pages from release-ready evidence, and the human makes credential, DNS, or product-judgment decisions.
Evidence contract
Implementation handoffs should include changed public artifacts, commands and checks run, intentionally public URLs, checkpoint identifiers retained in private handoff records, known limitations, residual risks, and a reviewer verdict.
Release-to-docs handoff
A release-ready documentation packet should include a release label, public summary, user-visible changes, profile changes, public artifacts, summarized verification evidence, migration notes, known issues, docs pages updated, and a security/privacy review statement.
Review gates
Reviewers verify output against acceptance criteria and public safety boundaries before work is treated as complete or released.