Public documentation v0.1.0
Profile matrix and role boundaries
Least-privilege responsibilities for the Software Factory roles.
| Profile | Public repository | Primary responsibility | Default boundary |
|---|---|---|---|
softwarefactorypm | https://github.com/jack-michaud/software-factory-pm-profile | Turn product intent into plans, acceptance criteria, risk notes, and follow-up tasks. | Does not mutate sprites, production systems, or profile distributions. |
softwarefactorybuilder | https://github.com/jack-michaud/software-factory-builder-profile | Implement approved local changes and perform explicitly scoped infrastructure work. | Infrastructure mutation must be task-authorized and should use backup/checkpoint discipline. |
softwarefactoryorchestrator | https://github.com/jack-michaud/software-factory-orchestrator-profile | Decompose work across specialist profiles and maintain board-level flow. | Routes work instead of executing specialist implementation itself. |
softwarefactoryreviewer | https://github.com/jack-michaud/software-factory-reviewer-profile | Independently verify readiness, public-safety boundaries, and release outputs. | Reviews evidence and reports findings; does not publish or mutate infrastructure by default. |
softwarefactorypublisher | https://github.com/jack-michaud/software-factory-publisher-profile | Generate, validate, tag, release, and publish approved profile artifacts. | Publication requires explicit approval and scoped credentials. |
softwarefactorydocs | https://github.com/jack-michaud/software-factory-docs-profile | Maintain public docs and release notes from approved handoffs. | Docs updates only; production or infrastructure mutation requires explicit task scope. |
Working model
PM frames the work, orchestrator splits it into role-specific tasks when needed, builder implements approved changes, reviewer verifies behavior and safety, publisher publishes approved artifacts, and docs updates public docs and release notes from release evidence.
Current v0.1.0 limitations
Branch protection and mandatory PR-review policy are deferred for the initial publication. Repository descriptions and topics may be updated in a later settings pass.