the work
Four projects, one method.
The point is not the projects, it is that the same method produced all of them. A solo operator ran four very different efforts, and each was stood up with the identical scaffold: a project orchestrator, a bench of specialists bound by the two-way ownership contract, project-local settings, and a validator enforcing the contract and the bloat caps. What differs is which patterns each exercised. No project name, domain detail, or stack is disclosed, by design.
a travel app
full launch team, up front
Instead of a minimal cut, this project received a complete launch crew mapped to agents: planning, design, copy, growth, quality, analytics, compliance, plus project-specific depth. The reasoning was that a solo operator’s real bottleneck is context-switching cost, so having every specialist ready beats adding them piecemeal. It also runs the paired code-side and knowledge-side teams, coordinated through the background-session dispatch pattern. Speculative capabilities were documented with gating conditions and left dormant rather than built on speculation.
a market-intelligence platform
deadline scope exception, then gap-fill and standardize
Two recorded patterns in sequence. First a deadline-driven exception: a code-writing role added with a deliberately broad path scope across the whole repository, a conscious, documented deviation from the narrow-scope default for launch-critical work, with the conditions for revisiting it noted. Later a gap-fill pivot: an inventory found a sizable set of specialists authored earlier but undocumented and orphaned from routing, so the session built only the missing roles, wired the orphans in, and fixed a validator-blocking drift, catching a near-duplication mid-session.
a local-services site
minimal footprint
A single-specialist project. It did not need a full bench, and the method does not force one. In the autonomy migration it was brought under the uniform topology with a thin orchestrator, so even a one-specialist project is routable from the top through the same one-touch front door as the larger teams. The scaffold scales down as cleanly as it scales up.
an original video game
minimal footprint
A second single-specialist project, retrofitted with a thin orchestrator in the consolidation so it joins the uniform "orchestrator plus specialists" shape. Two single-specialist projects beside two fuller paired projects is the clearest evidence that the method is a template applied at the right size for each effort, not a fixed team imposed on every one.
One scaffold, four sizes.
Two paired projects with fuller benches, two single-specialist projects, all on the identical contract and validator. The method is the constant; the team size is the variable. Deviations from the defaults, the broad-scope exception and the gap-fill pivot, are preserved with their rationale, so a future session learns why a project diverged instead of guessing. The same discipline crosses every one: verify before acting, narrow scope by default, and a human on the irreversible step.