Modular systems
Build multi-service stacks from the terminal: stable spine, attachable modules, less ceremony. init → add → up yields a runnable shape teams can extend.
Problem
Every new stack reinvents compose, env, auth wiring, and service boilerplate. Snowflake setups do not scale across products or teams. Cost shows up as delayed demos, fragile onboarding, and platform decisions re-litigated per repo.
Model
- CLI — init spine, add modules, up, health
- Spine — gateway, identity defaults, observability hooks
- Modules — domain service ± UI remote ± package surface
- Idempotent apply — re-run configure to converge
- Escape hatches — generated files until marked customized
What you get out
A running multi-service system with a known cut map: remotes talk through the gateway; services own their data; shared packages keep error and auth-header contracts aligned. Domain modules (auth, billing, catalog, vault, …) plug into that spine.
Ceremony drops when scaffolding is productized. The next service should not require re-deriving how auth and the gateway fit together.