The founding bet: a 2-person firm can match the variety of the AI-transformation market (Ashby/Beer sense) by building amplifiers — ~20 tool repos acting as variety attenuators and amplifiers around the founders. If this holds, the suite is the firm's viability mechanism, not overhead. Every repo must therefore justify itself as an organ in the VSM reading, not as a side project.

Clients buying AI transformation will accept — and prefer — a 2-person firm whose delivery is visibly instrumented (live graphs, scored diagnostics, generated artifacts) over a body-shop consultancy. The tooling is itself the credibility signal: "we run on this, so can you." Unproven at scale; Dr Max is the single supporting data point.

Every tool is built multi-tenant-capable (engagement_id on every entity, no hardcoded client) but deployed single-tenant per engagement by default. This keeps client-data isolation trivial to argue, makes migration to client-owned infrastructure a data export rather than a re-architecture, and defers real multi-tenancy cost until engagement volume forces it.