Public documentation v0.1.0
Builder source-update workflow
Source Map and git-flow expectations for Builder source-update work.
What changed
The Builder profile now directly documents the source-map and git-flow expectations for source-update work. The doctrine is installed for the production Builder profile softwarefactorybuilder and the meta Builder profile metasoftwarefactorybuilder.
Builder expectations
For source-update work, Builders use the PM-provided Source Map as the authority for public repositories and files in scope, clone or fetch the canonical source repositories into the task workspace before editing, create a topic branch for the work, and edit source-controlled files only.
Runtime profile boundary
Installed runtime profile directories are deployment output, not canonical source. Builders avoid publishing, pushing, installing, or mutating runtime targets unless the task explicitly scopes that authority.
Evidence for review and publication
Builder handoffs should include repository URLs, branch names, commit hashes, changed files, diff or diff-stat summaries, validation output, target-profile coverage, and any superproject submodule or shared-guidance changes. Builders should block on missing Source Map entries, missing repository access, or unclear canonical source coordinates rather than guessing.
Published artifacts
The public Builder profile doctrine is published in https://github.com/jack-michaud/software-factory-builder-profile on main at commit bd52a6e1fc30ade000acd9a1134ebe32a422f0ca. The Software Factory source monorepo at https://github.com/jack-michaud/software-factory on main at commit 42e4259c9e542e042538455b2547db7f3c90d766 points profiles/builder at that Builder profile commit and includes the shared Kanban profile workflow evidence gates.
Verification summary
Reviewer, publisher, and installer verification all passed. The release chain verified source-only edits, direct Builder doctrine coverage, public repository refs, the monorepo Builder submodule pointer, validation and tests, and rollout into both Builder profile installations with Source Map, clone/fetch, topic-branch, source-only edit, scoped-mutation, and evidence requirements present.
Public/private boundary
This note includes only public repository coordinates, commit identifiers, target profile names, changed public paths, and summarized verification outcomes. It omits credentials, raw runtime profile state, board databases, sessions, logs, memories, private workspace paths, tokens, and private operational metadata.