Public documentation v0.1.0
Software Factory Profiles
Public documentation for the Software Factory v0.1.0 source monorepo and generated Hermes profile distributions.
| Repository | Purpose | Install name |
|---|---|---|
| https://github.com/jack-michaud/software-factory | Source monorepo and public docs | n/a |
| https://github.com/jack-michaud/software-factory-pm-profile | PM role profile | softwarefactorypm |
| https://github.com/jack-michaud/software-factory-builder-profile | Builder role profile | softwarefactorybuilder |
| https://github.com/jack-michaud/software-factory-orchestrator-profile | Orchestrator role profile | softwarefactoryorchestrator |
| https://github.com/jack-michaud/software-factory-reviewer-profile | Reviewer role profile | softwarefactoryreviewer |
| https://github.com/jack-michaud/software-factory-publisher-profile | Publisher role profile | softwarefactorypublisher |
| https://github.com/jack-michaud/software-factory-docs-profile | Docs role profile | softwarefactorydocs |
What it is
Software Factory is a set of Hermes role profiles for running a small, reviewable software-delivery loop: PM plans, builder implements scoped changes, orchestrator routes work, reviewer verifies independently, publisher releases approved artifacts, and docs maintains public documentation from approved handoffs.
Published v0.1.0 repositories
The initial public release includes one source monorepo and six generated profile repositories. The source repository is tagged profiles/v0.1.0; generated profile repositories are tagged v0.1.0.
Source-of-truth model
The source repository contains profile source files, shared skills and snippets, generator scripts, tests, and public docs. Generated profile repositories are installable release artifacts for current Hermes users.
Profile-managed project-specific skills
Published and shared skills stay reusable across Software Factory projects. Project-specific instructions, examples, checklists, routing notes, customer or tenant conventions, and other scoped guidance belong in local profile-managed skills until generalized and approved for publication.
Builder source-update workflow
Builder source-update work now follows a documented source-map and git-flow doctrine: use the PM Source Map, clone or fetch canonical repositories into the task workspace, create a topic branch, edit source-controlled files only, treat installed runtime profile directories as deployment output, avoid unscoped publishing or installs, and leave reviewable repository, branch, commit, diff, validation, and coverage evidence.
PM Source Map requirements
PM-created profile and source-update handoffs now require an explicit Source Map before builder work begins: canonical monorepo, affected source paths, generated or installable role repositories, runtime verification targets, branch naming, publisher/submodule follow-through, reviewer checks, and disposable test-profile validation decision and rationale.
Conditional profile validation
Disposable test-profile validation is conditional: static reviewer checks remain the default for low-risk docs, comment, typo, and static-sufficient changes; behavior-risk changes or explicit human requests use a focused disposable validation chain before rollout.
Progressive-disclosure task specs
PM and Kanban task specs now follow a progressive-disclosure pattern: compact root instructions, context indexes with explicit When X, read Y routing, scoped task bodies, and evidence-linked acceptance criteria that are clear, testable, outcome-focused, measurable where possible, independent, and stakeholder-readable.
License
Software Factory public repositories are released under MPL-2.0.