Specialist VC funds today.
All methodology-preserving knowledge work tomorrow.
The substrate architecture is genuinely domain-agnostic at L0. L1 frameworks derive per-domain. L2 instances per-customer. Specialist VC funds are our wedge — and the proof the platform thesis works. Read end-to-end. The audience for this page is the audience for the long-horizon company.
FIG. 00 ── THE WEDGE OPENS · ONE SUBSTRATE · MANY DOMAINS
Why specialist VC funds first.
Specialist VC funds are the cleanest possible wedge for substrate-grade architecture. Three conditions converge — and the convergence is rare enough that almost no other knowledge-work domain has all three at once today.
FIRST — methodology is the value proposition. Generalists average. Specialists compound. The methodology that makes a specialist specialist is the thing that's worth preserving — and it's exactly the thing that lives in partner heads, not in databases.
SECOND — the regulatory environment forces audit-grade discipline. Article 9 SFDR, post-FTX LP scrutiny, 7-year retention requirements — funds need forensic audit infrastructure they haven't built. Substrate is the answer.
THIRD — the economics work. Sub-€500M AUM specialist funds have fundamentally non-scalable operations (the partner is the product). Their only scaling lever is operational substrate. The price they'd pay for methodology preservation is finally below the value they receive from it.
The wedge is sharp because the three converge in the same buyer at the same time. Other domains (law, research, creative, consulting, medical) hit the same architectural problem — but rarely with all three pressures simultaneously yet.
FIG. 01 ── THREE CONDITIONS · ONE CONVERGENCE · THE WEDGE TIP
The wedge is sharp. The market is concrete. The architectural problem is solvable.
Every domain with methodology-preservation needs operates under the same substrate.
The substrate's L0 doctrine is genuinely domain-agnostic. Audit chain by default. L8 architectural floors. Tether-pair discipline. 3-layer ontology. Substrate-mirroring. These five disciplines apply to every knowledge-work domain where methodology preservation matters more than fluency. We've already mapped the framework to five additional domains.
FIG. 02 ── ONE SUBSTRATE HUB · SIX DOMAIN HORIZONS · ONE LIVE WEDGE
Article 9 SFDR · impact · deeptech · healthtech · climate · MentalWellness.
Hexframe-class scoring · NurtureCapital framing · LP voice tiers · IAC workflows.
Matter-management framework · partners + associates + paralegals · multi-matter operations.
Matter-risk scoring · client confidentiality (L8) · UPL architectural cap on AI drafters · billing rigor.
Academic or industrial · PI + postdocs + grad students · multi-project · multi-year cycles.
Evidence-quality scoring · publication-readiness · IRB compliance (L8) · authorship attribution permanence.
Brand strategy + production + client account management · multi-client portfolio.
Brand-fit scoring · creative quality · client-IP isolation (L8) · advertising standards compliance.
Multi-engagement practice · scope-bounded delivery · methodology accumulation.
Engagement-health scoring · cross-client information bleed prevention (L8) · methodology capture per engagement.
Clinical-research site or specialist medical practice · protocol-driven · regulatory-tied operations.
Clinical-evidence scoring · IRB compliance (L8) · medical-ethics constraints · regulatory pathway tracking.
Six worked example domains. Five disciplines that travel unchanged. One framework methodology that derives L1 per domain. The same substrate that proves itself on specialist VC funds extends to every domain where institutional reasoning needs preservation, replay, and inspection.
Three IP boundaries make the platform tractable.
The platform works because IP scope is explicit at three levels. L0 doctrine is genuinely universal (open methodology). L1 framework is operator IP (travels across customers in the same domain). L2 instance is customer IP (stays with the customer, with pattern-migration option).
FIG. 03 ── L0 BASE · L1 FRAMEWORK · L2 CROWN · NARROWING IP SCOPE
Universal substrate doctrine. Five disciplines · tier framework · κ verification · D7 §12 · MAJOR / MINOR / PATCH cycle. Genuinely domain-agnostic.
The framework itself. Methodology, derived from first-principles substrate architecture. Open.
Domain-specific framework. The specialist-VC L1 is one example. Specialist law firm matter management is another. Six worked examples mapped in our framework reference implementation.
Fund AI OS. L1 frameworks travel across customers in the same domain · operator IP · derived from L0 + domain expertise. Cross-domain patterns derive new L1s.
Per-customer instance. Your specific methodology overlay · scoring weights · LP voice tiers · sub-thesis priorities · IAC composition.
The customer. Your overlay is yours. Versioned in git. Portable. Owned. With L2 → L1 pattern migration option (attribution + compensation).
L0 is the framework. L1 is the domain. L2 is yours.
Five disciplines. Domain-agnostic. Non-negotiable.
Whatever the domain — VC, law, research, creative, consulting, medical — these five disciplines hold. They're the substrate-grade primitives that make every L1 framework substrate-grade. Without all five, the result is policy-asserted, not architecturally enforced.
FIG. 04 ── FIVE DISCIPLINES × SIX DOMAINS · GLYPH IS INVARIANT
Audit chain by default
L8 architectural floor
Tether-pair discipline
3-layer ontology
Substrate-mirroring (I15)
Defined canonically on /substrate §03. Operative on every L1 framework derived from the platform.
Patterns travel. With attribution. With compensation.
When a pattern proves cross-cutting across multiple customers in the same L1, it can migrate L2 → L1 — with explicit attribution, compensation, and the original customer's concurrence. The L1 framework gets smarter with every engagement in the cohort. The original customer benefits from downstream contributions.
FIG. 05 ── ORIGIN → CONCURRENCE GATE → L1 → COHORT INHERITANCE
L2 → L1 migration requires the original customer's explicit concurrence. Triple-signed: customer + operator + L1 framework version controller.
The originating customer is named in the L1 commit log. Compensation terms negotiated per-pattern · aligned incentives.
Each new customer in the same L1 inherits prior pattern migrations. The L1 gets smarter. The original customer benefits downstream.
Your overlay is yours. Patterns that prove universal travel to the L1 — with your concurrence, with attribution, with compensation. The substrate compounds across the cohort, not just within one engagement.
Thirteen documents. The bridge IP.
The Universal Substrate Framework v1.0 is the operator-tier IP that makes domain adaptation tractable. Thirteen documents defining the L0 doctrine + the L1 meta-pattern (how to derive a domain-specific framework) + the L2 meta-pattern (how to generate a project-specific instance) + the bootstrap interview protocol + the substrate generation protocol + five worked examples.
FIG. 06 ── 13 DOCS · 5 EXAMPLES · 9 QUESTIONS · 1 BOOTSTRAP PROMPT
L0 universal doctrine + L1 meta-pattern + L2 meta-pattern + interview protocol + generation protocol + worked examples.
Specialist law firm · research lab · creative agency · solo consultant · specialist VC fund (LIVE).
Domain · stakeholders · scale · stakes · deliverable · scoring · L8 floors · agents · phase shape · regulatory context.
The master prompt that interviews any project owner across 4 rounds of structured questions · then generates the L1 + L2 in one sequence.
The framework is not the product. The framework is the bridge — operator IP that makes "Fund AI OS" generalize to "law firm OS" or "research lab OS" tractably. Each L1 framework derived from the v1.0 framework is its own product, sold into its own market.
Where infrastructure companies arrive.
FIG. 07 ── BOLT-ON · VERTICAL SUBSTRATE · HORIZONTAL SUBSTRATE
The bolt-on era.
AI bolted onto existing SaaS workflows. Fragments deeper. Outputs without audit, replay, governance.
The substrate-vertical era.
Substrate-grade systems built vertically for specific industries. Domain-specific moats. But still per-vertical.
The substrate-horizontal era.
The substrate doctrine generalizes across domains. L1 frameworks derive from L0. Network effects compound across L1 cohorts.
Most current substrate-grade companies live in Era 2. The platform thesis is that the same architecture goes horizontal — into every knowledge-work domain.
§ 08 ── PLATFORM THESIS
The substrate is domain-agnostic at L0. Every L1 we derive proves it again.
── FUND AI OS · PLATFORM THESIS
The wedge is specialist VC. The expansion is every knowledge-work domain where methodology preservation matters more than fluency. The bridge between them is the Universal Substrate Framework. Read it as a long-horizon company thesis, not a roadmap.
§ END ── BUILD THE NEXT L1
If your domain isn't specialist VC — but the architectural problem rhymes — talk to us about the L1.