diff --git a/docs/BACKLOG.md b/docs/BACKLOG.md index d9638e3c19..29b34fa117 100644 --- a/docs/BACKLOG.md +++ b/docs/BACKLOG.md @@ -359,6 +359,7 @@ are closed (status: closed in frontmatter)._ - [ ] **[B-0732](backlog/P1/B-0732-runbook-as-executable-reality-leverage-class-safety-substrate-engineering-target-mika-feels-the-weight-aaron-play-doh-design-property-2026-05-25.md)** Runbook-as-executable-reality is a NEW LEVERAGE CLASS — safety substrate engineering target; existing destructive-tool contract operates at script scope, runbook leverage operates at system-direction scope (Mika feels the weight; Aaron's Play-Doh design property) - [ ] **[B-0765](backlog/P1/B-0765-service-titan-route-plug-into-existing-control-interfaces-not-new-ones-ontology-negotiation-at-standards-layer-aaron-2026-05-25.md)** ServiceTitan route — plug into existing control interfaces/structures (not new ones); ontology negotiation at the standards layer - [ ] **[B-0767](backlog/P1/B-0767-zeta-native-scheduler-first-deterministic-simulation-and-ai-aware-cluster-management-aaron-2026-05-25.md)** Zeta-native scheduler first (Wave 1 of B-0766) — deterministic simulation + AI-aware cluster management +- [ ] **[B-0769](backlog/P1/B-0769-vc-meta-playbook-control-structure-injection-around-capital-in-verticals-substrate-honest-variant-aaron-2026-05-25.md)** VC meta-playbook (control-structure injection around capital flow in verticals) — substrate-honest variant for Zeta ## P2 — research-grade diff --git a/docs/backlog/P1/B-0769-vc-meta-playbook-control-structure-injection-around-capital-in-verticals-substrate-honest-variant-aaron-2026-05-25.md b/docs/backlog/P1/B-0769-vc-meta-playbook-control-structure-injection-around-capital-in-verticals-substrate-honest-variant-aaron-2026-05-25.md new file mode 100644 index 0000000000..608964b561 --- /dev/null +++ b/docs/backlog/P1/B-0769-vc-meta-playbook-control-structure-injection-around-capital-in-verticals-substrate-honest-variant-aaron-2026-05-25.md @@ -0,0 +1,353 @@ +--- +id: B-0769 +priority: P1 +status: open +title: VC meta-playbook (control-structure injection around capital flow in verticals) — substrate-honest variant for Zeta +effort: L +ask: aaron 2026-05-25 +created: 2026-05-25 +last_updated: 2026-05-25 +depends_on: + - B-0765 +composes_with: + - B-0741 + - B-0754 + - B-0759 + - B-0761 + - B-0762 + - B-0763 + - B-0764 + - B-0766 + - B-0767 + - B-0768 +tags: [strategy, vc-meta-playbook, control-structure, capital-flow, vertical-saas, ethical-floor, non-extractive] +--- + +## Problem + +Aaron 2026-05-25 mid-iteration-2-wait, naming the third strategic +anchor under B-0765 ServiceTitan-route + B-0768 Itron-co-creation: +*"Also ST is based on VC meta playbook around control structrue +injection around capitol in different virticles."* + +The VC meta-playbook that produced ServiceTitan + a generation of +verticalized-SaaS unicorns: + +1. **Pick a vertical** (a specific industry/business-category + with established workflows + meaningful capital flow) +2. **Identify the control structures** that already exist in + that vertical (dispatch, billing, customer mgmt, payroll, + inventory, etc.) +3. **Build software that becomes the CONTROL LAYER** — operators + in the vertical adopt it because it makes their existing + workflows better +4. **Inject around capital flow** — every transaction in the + vertical eventually routes through your software; you have + leverage (rake, data, ecosystem expansion) +5. **Compound** — capital-flow gate position becomes the + substrate for adjacent product expansions (payments, + lending, insurance, marketplace, vendor-management, etc.) + +Empirical instances (all VC-funded; all became unicorns or +larger): + +| Vertical | Control structure | Capital flow gated | +|---|---|---| +| Trades services (HVAC / plumbing / electrical) | ServiceTitan | Dispatch + billing + customer comms | +| Restaurants | Toast | Payments + payroll + POS + supplier | +| Construction | Procore | Project mgmt + bidding + change orders | +| Ecommerce | Shopify | Storefronts + payments + shipping + capital | +| Hospitality | Mews / Cloudbeds | Reservations + payments + housekeeping | +| Legal practice | Clio | Time tracking + billing + trust accounts | +| Real estate | Compass / Side / Lone Wolf | CRM + transaction mgmt + commissions | +| Healthcare practice | Athena / Epic | EHR + claims + scheduling | +| Childcare | brightwheel | Parent comms + billing + enrollment | +| Auto dealerships | Reynolds + Reynolds / CDK | DMS + F&I + parts + service | +| Delivery / rideshare | DoorDash / Uber | Order routing + payments + driver mgmt | + +ServiceTitan is one empirical anchor in a well-documented meta- +playbook pattern. Aaron 2026-05-25 sharpening (per B-0768 ST +provenance): *"ST was two guys in a garage i saw both"* — Aaron +watched ST execute this playbook from inception. The pattern is +direct lived experience, not theoretical case-study. + +## Target + +Apply the VC meta-playbook to Zeta's vertical, in the +substrate-honest variant that preserves operator-in-the- +negotiation-high-seat (per B-0763 / B-0765 / B-0768) and does +NOT execute the extractive failure mode the standard VC meta- +playbook converges on. + +### Zeta's vertical positioning + +| VC-playbook component | Zeta's instantiation | +|---|---| +| **Vertical** | AI cluster infrastructure (specifically the AI-cluster substrate where Zeta is pioneer — modern declarative AI clusters with GPU + storage + scheduling + observability + identity + repair-tool semantics) | +| **Existing control structures** | k8s control plane, GitOps reconciliation (ArgoCD/Flux), CNCF ecosystem (KEDA/DAPR/OPA/Crossplane/etc.), cloud-provider APIs (AWS/GCP/Azure/Cloudflare/etc.), hardware vendor SDKs (NVIDIA/AMD/Intel) | +| **Control layer Zeta builds** | Operator-facing interfaces + reference architecture + zero-typing install (B-0754) + USB-as-repair-tool (B-0760) + telemetry flywheel (B-0762) + Zeta-native scheduler (B-0767) + binary-compatible Zeta-native k8s impls (B-0766) | +| **Capital flows the control layer gates** | Compute spend (GPU $/hour), storage spend, network egress, model-API calls, identity/auth costs, observability SaaS spend, support contracts, training/inference spot/reserved purchases, multi-region orchestration | +| **Compound expansions** | Once operator runs Zeta cluster substrate, adjacent product surfaces: managed AI-workload marketplace, optimization advisor (B-0762 telemetry-driven), vendor-cost arbitrage (B-0763 swap mechanism), DST replay services, model-locality-aware CDN, compliance/governance automation | + +## Substrate-honest variant — the failure mode this row protects against + +The standard VC meta-playbook converges on EXTRACTION: + +| Extractive pattern | Standard VC outcome | Zeta substrate-honest alternative | +|---|---|---| +| Take rent on every transaction | Marketplace fee, payment-processing margin, capital-as-a-service spread | Open reference (B-0761); operator can swap vendors per B-0763 → competitive pricing pressure underneath | +| Lock vendors out | Exclusive marketplace contracts; preferred-vendor positioning | Vendor-swap preserved per B-0763 + binary-compat per B-0766 → every vendor competes | +| Lock operators in | Switching cost = rewrite-application; data export crippled | Standards-first per B-0765 (uses k8s CRDs + Helm + OCI everyone already speaks); switching cost ≈ 0 | +| Hoard data asymmetrically | Operator's data becomes vendor's strategic asset | Telemetry is opt-in per B-0762; collected data published openly; no asymmetry | +| Capture upside; socialize downside | Vendor takes growth; operators absorb risk + failure cost | Failure-tolerance built in (B-0760 USB-as-repair-tool); operator carries upside via lower TCO | +| Hide pricing | Quote-based; opaque rate cards; sales-touch required | Cost-comparison surface mandated per B-0763 acceptance | +| Build moat via lock-in | Switching cost moat | Moat via composition coherence + open reference + telemetry flywheel + AI-trainable substrate | + +The substrate-honest variant: **same control-structure position; +opposite value-flow direction**. Standard VC playbook extracts up +(vendor captures rent + data + lock-in). Zeta's variant lets +operators keep the value (cluster runs better; operator pays +less; data stays operator's; vendor competition kept healthy). + +The framework guards this variant via existing rules: + +- `.claude/rules/non-coercion-invariant.md` (HC-8) — no + coercion of operators into Zeta-specific lock-in +- `.claude/rules/additive-not-zero-sum.md` — Zeta substrate is + additive to operator value, not zero-sum extraction +- `.claude/rules/glass-halo-bidirectional.md` — transparency + about substrate-honest control-structure position +- `.claude/rules/m-acc-multi-oracle-end-user-moral-invariants.md` + — operator chooses their own invariants; multi-oracle + substrate prevents single-vendor-truth-imposition +- `.claude/rules/methodology-hard-limits.md` — HARD LIMITS + apply to control-structure injection scope too + +## Financial-engineering layer — adjusted EBITDA for specific investor profiles + +Aaron 2026-05-25 sharpening: *"with adjusted ebita for specific +investor profiles"*. The VC meta-playbook executes through a +specific financial-engineering vocabulary that translates +business performance into metrics each investor profile +evaluates against: + +| Investor profile | Primary metric | Typical adjustments | What they're solving for | +|---|---|---|---| +| **Seed / Series A growth** | ARR growth rate + net-revenue retention | Stock comp; one-time costs; new-product R&D | Path-to-product-market-fit + revenue compounding | +| **Series B-D growth equity** | Rule-of-40 (growth% + adj EBITDA margin%); LTV:CAC | Stock comp; M&A integration costs; new-market entry | Sustainable growth with improving unit economics | +| **Late-stage / pre-IPO** | Adj EBITDA margin ≥30%; FCF conversion; ARR durability | Stock comp; restructuring; one-time IPO-prep costs | Predictable EBITDA growth quarter-over-quarter | +| **PE roll-up** | Stable adj EBITDA + multiple-arbitrage spread | "Run-rate" synergies; "normalized" management comp; PE-removed costs | Buy-at-low-multiple → operate → sell-at-high-multiple | +| **Strategic acquirer** | Strategic-fit + synergy-justified post-integration EBITDA | Acquirer-synergy add-backs; redundant-function elimination | Accretion to acquirer's own valuation + capability fill | +| **Public markets** | Quarterly EPS + adj EBITDA + guidance accuracy | SBC; restructuring; M&A; one-times; impairments | Predictable beat-and-raise pattern + survives audit | + +ServiceTitan empirical anchor (per B-0768 provenance + Aaron's +direct lived experience): IPO'd Dec 2024; navigated multiple +investor-profile transitions (early-stage growth → late-stage +growth → pre-IPO → public markets) each requiring different adj +EBITDA shaping; survived each transition because the underlying +business performance + control-structure-position was real +(not just financial-engineering). + +### Substrate-honest variant of the financial-engineering layer + +Same shape; different ethical floor: + +| Failure mode (standard VC playbook drift) | Substrate-honest discipline (Zeta) | +|---|---| +| Adjustments inflate EBITDA via misclassification (e.g., R&D as "one-time"; recurring SBC as "non-cash") | Adjustments are TRUE adjustments (genuine one-times; non-cash properly disclosed); auditor-survivable; investor-survivable when scrutinized | +| Pick the investor profile whose metric flatters us now | Pick the investor profile whose evaluation horizon matches our actual substrate-engineering horizon; don't optimize for short-term metric at long-term cost | +| Different metric for different audiences with no reconciliation | Single reconciled GAAP→non-GAAP bridge published for every adjustment; every investor sees the same bridge | +| Defer recognition / accelerate revenue / smooth quarters | Recognize per GAAP discipline; volatility in quarters is honest if substrate is genuinely investment-mode | +| Pre-IPO clean-up = quietly retire embarrassing programs | If a program retires, retire substrate-honestly with public reasoning; don't hide failure modes from acquirers or public-market investors | +| Synergy assumptions in strategic-acquirer pitches that don't survive integration | Synergy assumptions reviewable + grounded; if Zeta is the acquirer, audit acquired companies' synergy claims for the same discipline | + +The substrate-honest variant doesn't reject adjusted EBITDA as a +metric (it IS the vocabulary VC + public market evaluators use; +refusing the vocabulary = refusing investor engagement). It +operates the vocabulary with discipline. ServiceTitan's +empirical success demonstrates this can be done — Aaron's +provenance from inside is the substrate-honest grounding. + +### When this layer becomes active for Zeta + +- **Today (pre-revenue, garage-equivalent)**: financial- + engineering layer is dormant. Aaron's compensation + cost- + basis are operator-side; no investor metric reporting yet. + Substrate just exists as future-Otto cold-boot guidance. +- **First external revenue**: ARR growth + net-revenue + retention become operative metrics; seed/A-stage VC + evaluation if fundraising +- **Series B+**: rule-of-40 + LTV:CAC operative +- **Pre-IPO (if pursued)**: full adj EBITDA discipline; auditor + engagement; SEC-survivable reporting +- **Public markets (if pursued)**: quarterly cadence; beat-and- + raise discipline; substrate-honest reconciliation bridges + in every 10-K + 10-Q + +The point of naming this NOW (pre-revenue, garage-equivalent +stage) is: future Zeta corporate-development decisions inherit +the substrate-honest discipline at cold-boot instead of +reinventing it under fundraising pressure. The financial- +engineering decisions made under pressure are the highest-risk +for drift; substrate-engineering them in advance is the +bandwidth-engineering payoff. + +## Acceptance + +- [ ] Document the dual-framing explicitly in + `docs/strategic-substrate.md` (compose with B-0765 + + B-0768): VC meta-playbook IS what Zeta executes; + substrate-honest variant IS what makes Zeta different +- [ ] Per-extractive-pattern audit: for every Zeta substrate + decision, check the failure-mode table above. Is the + decision extracting (failure mode) or composing + (substrate-honest)? +- [ ] Capital-flow mapping: explicit `docs/capital-flow-map.md` + naming WHERE money moves in AI cluster ops + WHICH + Zeta substrate gates each flow + HOW the substrate-honest + variant operates per flow +- [ ] Compound-expansion roadmap: which adjacent product + surfaces become viable once Zeta cluster substrate has + adoption, sequenced + scoped per substrate-honest filter +- [ ] Counterweight substrate: identify which existing rules + + substrate explicitly protect against the extractive + failure mode; ensure each is reachable from this row's + composes-with +- [ ] Marketing surface: README + landing-page explicit about + "we run the VC meta-playbook substrate-honestly" — + operators understand what they're adopting +- [ ] Stress-test the substrate-honest variant against + VC-funded scenarios: if Zeta takes VC capital later, + how do the substrate-honest invariants survive + board-pressure for extractive expansion? (Pre-commit + contracts; non-coercion-invariant at corporate-governance + scope; etc.) + +## Composition with the strategic substrate cluster (B-0765 + B-0766 + B-0767 + B-0768) + +The composed strategic substrate from this session: + +| Layer | Row | Role | +|---|---|---| +| Meta-strategy (this row) | B-0769 | The VC meta-playbook Zeta executes; substrate-honest variant | +| Tactical playbook A | B-0765 P1 | ServiceTitan up-and-comer mode: plug into existing standards | +| Tactical playbook B | B-0768 P1 | Itron incumbent-with-incumbent mode: co-create standards | +| Implementation roadmap | B-0766 P1 | Slow-replace dependencies with binary-compatible Zeta-native impls | +| First implementation wave | B-0767 P1 | Zeta-native scheduler first (DST + AI-aware) | +| Adoption mechanism | B-0762 P2 | Auto-submit-back telemetry flywheel → adoption cost → 0 | +| Vendor-relationship contract | B-0763 P2 | Operator-in-the-negotiation-high-seat via interface ownership | +| Ecosystem leverage | B-0764 P2 | CNCF projects as force multipliers behind interfaces | +| Reference target | B-0761 P2 | Open AI-trainable cluster reference + ARC-AGI benchmark | +| UX bar | B-0759 P2 | First-time-CLI-user persona + 3-node prod-ready inflection | +| Substrate primitive | B-0754 P2 | Zero-typing cluster install (iteration N in progress) | +| Operational resilience | B-0760 P2 | USB as universal repair tool; zero-disruption at 3+ nodes | +| Edge-case coverage | B-0758 P3 | unRAID-style USB-persistent-OS / zero-disk | + +This row is the **load-bearing strategic context** that explains +WHY the rest of the cluster fits together as one coherent +substrate. Without naming the VC meta-playbook explicitly, the +rest reads as engineering decisions that happen to compose. +With the meta-playbook named, the rest reads as one coherent +substrate-honest execution of a well-tested commercial pattern. + +## Composes with + +- B-0741 — ontology negotiation (at standards layer per + ServiceTitan + Itron; substrate-honest because every operator + using any standard benefits) +- B-0754 — zero-typing first-boot (the operator-facing control + layer entry point) +- B-0759 — first-time-CLI-user persona (the adoption bet that + makes the VC meta-playbook work at scale) +- B-0761 — open reference architecture (the substrate-honest + variant of "compound expansion" — open vs proprietary + reference) +- B-0762 — auto-submit-back telemetry (the substrate-honest + variant of "hoard data" — opt-in + open data) +- B-0763 — cloud-native plugins fit Zeta interfaces (the + substrate-honest variant of "lock vendors out" — vendor + competition preserved) +- B-0764 — CNCF ecosystem force multipliers (the + substrate-honest variant of "build moat via lock-in" — moat + via composition coherence, not lock-in) +- B-0765 P1 — ServiceTitan route (the tactical playbook A this + row's meta-strategy informs) +- B-0766 P1 — slow-replace k8s binary-compat (the implementation + roadmap that gives Zeta ownership over time without breaking + vendor competition) +- B-0767 P1 — Zeta-native scheduler first (the first + implementation wave that delivers AI-cluster-substrate value + the meta-playbook depends on) +- B-0768 P1 — Itron incumbent-with-incumbent strategy (the + tactical playbook B this row's meta-strategy also informs) +- `.claude/rules/non-coercion-invariant.md` (HC-8) — the floor + that protects against extractive failure mode +- `.claude/rules/additive-not-zero-sum.md` — the disposition + that ensures substrate-honest value flow +- `.claude/rules/m-acc-multi-oracle-end-user-moral-invariants.md` + — the architectural structure that prevents single-vendor- + truth-imposition + +## What this preserves vs prevents + +**Preserves**: the strategic positioning that the VC meta-playbook +proves works (control-structure injection around capital flow in +a vertical = sustainable business with leverage + compound +expansion potential). + +**Prevents**: the extractive failure mode that VC-funded vertical +SaaS typically converges on (rent extraction, lock-in, data +asymmetry, opacity). Zeta keeps the strategic substrate + +operates it substrate-honestly per existing framework rules. + +## Why P1 priority + +- This is the strategic context that explains why the rest of + the cluster substrate fits together; without it, the rest + reads as ad-hoc engineering +- Future substrate-engineering decisions need this filter + available at cold-boot +- The substrate-honest variant requires active discipline; if + not named explicitly, drift toward extractive failure mode + is the default trajectory under outside pressure (VCs, + growth metrics, board mandates, etc.) +- Aaron's empirical-provenance lived experience (per B-0768 + "ST was two guys in a garage i saw both") gives this row + unusually strong grounding — not theoretical + +## Out of scope + +- VC fundraising strategy (when/whether Zeta takes VC capital + + on what terms) — separate scope; this row's substrate- + honest invariants must survive whatever fundraising path is + taken later +- Specific vertical-SaaS competitive analysis per existing + unicorn (ST / Toast / Procore / etc.) — out of scope; the + meta-playbook pattern is what matters +- Anti-trust / regulatory implications of capital-flow-gating + position — separate scope; the substrate-honest variant + ALREADY operates within consent-floor + non-coercion-floor +- Public marketing of "we're not extractive" claims — + premature; ship working substrate first; the substrate-honest + variant is observable from operator outcomes over time, not + from marketing claims + +## Origin + +Aaron 2026-05-25 mid-iteration-2-wait, naming the third strategic +anchor: VC meta-playbook (control-structure injection around +capital flow in verticals) IS the playbook that produced +ServiceTitan. Per B-0768 empirical-provenance: Aaron watched ST +execute this playbook from two-guys-in-a-garage inception. +Direct lived experience, not theoretical case-study. + +This row makes the meta-playbook explicit as substrate so +future-Otto cold-boots inherit: +(1) what the playbook is, (2) why Zeta executes it, (3) what +the substrate-honest variant looks like, (4) what the +extractive failure mode looks like, (5) which existing +framework rules protect against the failure mode. + +Together with B-0765 + B-0766 + B-0767 + B-0768 + the rest +of the cluster-install substrate cluster, this completes the +strategic-substrate composition for the Zeta cluster vertical.