Torus Multibuild
A governed system for building and coordinating multiple companies without losing order, context, or architectural discipline.
Now Establishing the Founder Code MultiBuild Operating System as the shared branch, worktree, and versioning standard across every active company build.
Overview
- What it is
- The portfolio coordination layer for every Founder Code product — tracking which products exist, which repositories back them, what state each is in, and the shared development standard every repository follows. It holds the Founder Code MultiBuild Operating System, the canonical manual for branch, worktree, documentation, and versioning conventions across active company builds.
- Problem
- Building several companies at once scatters code, decisions, and lessons across repositories, conversations, and memory, with no shared standard for how work is branched, tracked, or versioned.
- Approach
- One governed portfolio registry and operating manual — tracking every product's repository, branch, worktree, and version state, and defining the shared standard every repository follows.
Capabilities
- Portfolio-wide product and repository registry
- Movement-based versioning standard (vMAJOR.MINOR.PATCH)
- Branch and worktree governance
- Portfolio development ledger
- Shared documentation standard across repositories
Activity
Version 1.9.0 released
Torus Multibuild released version 1.9.0 of its registry.
Version 1.3.0 released
Torus Multibuild released version 1.3.0 of its registry.
Founder Code MultiBuild Operating System reaches v1.1.0
Established the permanent operating manual for branch, worktree, documentation, and versioning conventions used across active Founder Code company builds.
Observed from a governed source, and attested by Kevin · Private governed source. Facts only — the reasoning behind them lives in Founder Notes.