Public documentation v0.1.0
Install and upgrade Software Factory profiles
Install generated profile repositories with Hermes; use the source repository for docs, issues, and source changes.
| Role | Install command |
|---|---|
| PM | hermes profile install https://github.com/jack-michaud/software-factory-pm-profile.git --name softwarefactorypm |
| Builder | hermes profile install https://github.com/jack-michaud/software-factory-builder-profile.git --name softwarefactorybuilder |
| Orchestrator | hermes profile install https://github.com/jack-michaud/software-factory-orchestrator-profile.git --name softwarefactoryorchestrator |
| Reviewer | hermes profile install https://github.com/jack-michaud/software-factory-reviewer-profile.git --name softwarefactoryreviewer |
| Publisher | hermes profile install https://github.com/jack-michaud/software-factory-publisher-profile.git --name softwarefactorypublisher |
| Docs | hermes profile install https://github.com/jack-michaud/software-factory-docs-profile.git --name softwarefactorydocs |
Requirements
Hermes Agent with hermes profile install and hermes profile update available, network access to GitHub, and any role-specific credentials configured outside the published repositories. The public distributions do not include secrets or local runtime state.
Upgrade an installed profile
Run hermes profile update <profile-name> --yes, replacing <profile-name> with the local profile name you installed.
Optional docs deployment target
PM and docs profile distributions declare SOFTWARE_FACTORY_DOCS_SPRITE_NAME in distribution.yaml as an optional env var for deployed docs work. Set it in each installed profile user-owned .env only when docs publication should target a dedicated docs sprite. The current non-secret example value is SOFTWARE_FACTORY_DOCS_SPRITE_NAME=hermes-sf-docs. Distribution installs and updates must not overwrite .env.
PM and docs publication behavior
PM profiles create deployed-docs tasks only when a target is available and include that non-secret target or variable contract in the handoff. Docs profiles publish only to the explicit handoff target or the sprite named by SOFTWARE_FACTORY_DOCS_SPRITE_NAME; if no target is available for a deployed-docs request, they block or skip publication instead of guessing.
Pinning v0.1.0
Generated profile repositories are tagged v0.1.0. The source monorepo release tag for the same publication is profiles/v0.1.0.
Updating from local prototype installs
If you previously installed a Software Factory profile from a local prototype directory, install the matching public generated repository under the canonical name, verify the profile list, and prune disposable prototype installs after experiments.