The layer model: who owns what
The MCV ecosystem is organized as layers, and the layer of a thing answers two questions at once: who owns it, and who may build on it. Ownership and consumption are different axes — a venture consumes the substrate without owning any of it — and the layer model keeps the two straight.
The five layers
- L0 — the substrate. The constitutional layer: identity and trust, the data fabric, the intelligence primitives, the kernel, and royalty metering. L0 holds pure contracts and protected core services; everything above depends on it, and it depends on nothing above.
- L1 — the developer platform. Horizontal capability every venture consumes: the agent runtime, the shared UI system, and the integrations hub. L1 turns L0 contracts into usable platforms.
- L2 — the venture clusters. Franchise-grade SaaS for operators — the layer this site's documentation describes. MCV.TECH is an L2 cluster: fitness, dining, capital, property, construction, and counsel workflows on the shared substrate.
- L3 — the convergence hub. The consumer-facing front door where identity, apps, and surfaces converge for end users rather than operators.
- L4 — the ventures tier. A neutral tier of independent, peer venture organizations — each isolated, each mapped to its own entity, none owning the others.
Why dependencies only flow downward
Imports and dependencies point down the stack — L2 builds on L1, L1 on L0 — and never upward. The rule is enforced mechanically: an upward import is a compile-time and CI failure, not a code-review discussion. Three properties follow:
- The substrate cannot capture a venture. Lower layers have no knowledge of what sits above them, so nothing fundamental can silently couple itself to one tenant's needs.
- Consumers receive artifacts, not source. A layer boundary is a publishing boundary: what you build on arrives as a versioned package with a contract, exactly as venture onboarding describes.
- Layers can be replaced underneath their consumers. Because consumers hold contracts rather than internals, an engine inside a layer can be swapped without an ecosystem-wide migration.
Layers versus tenancy: two axes that nest
The layer model is about ownership; the tenant hierarchy is about data. They nest without contradiction: a single L2 venture cluster runs many brands, and each brand's records stay isolated inside it. "Which layer built this" and "whose record is this" are independent questions with independent answers.
The recursive template
The same structural template repeats at any node large enough to be a platform: a core, horizontal capabilities on top of it, and consumers on top of those. A large venture tier instantiates the pattern one level down — its own platform core, its own consumer planes — until the recursion bottoms out at L0 primitives. Recursion is what lets the ecosystem add ventures without inventing a new architecture each time.
Boundary
This page presents the public structural model. Entity mappings, ownership detail, and governance internals are corporate matters, deliberately out of scope for product documentation.