CMacNamMan

The action layer for a Business DNA Wiki — how strategic knowledge becomes growth plans, workstreams, experiments, and results. Pairs with the Business DNA Wiki (schema) and Business DNA Ops (heartbeat).

Growth Ops

The Business DNA Wiki defines the knowledge base — six domains, thirty-two subdomains, the questions every business needs to answer. Business DNA Ops describes how that knowledge stays alive through ingest, synthesize, and query cycles.

This document defines the action layer: how accumulated knowledge becomes execution. Growth is not a knowledge domain — it doesn't sit alongside Customer, Value, or Market as a thing you understand. It's the layer where you decide what to do about what you understand, commit to specific bets, and measure whether they worked.

The knowledge base answers "what do we know?" Growth answers "what are we going to do about it?"

CMacNamMan

How to keep a Business DNA Wiki alive — three operations, two layers, and an archive. Pairs with the Business DNA Wiki (schema) and Growth Ops (action layer).

Business DNA Ops

How to keep a Business DNA Wiki alive. The Business DNA Wiki defines the schema — six domains, thirty-two subdomains, the questions every business needs to answer. This document defines the operational model: how knowledge gets in, how it stays current, and how raw evidence becomes synthesized understanding.

The system has three operations and two layers. That's it.

Two Layers

CMacNamMan

The fundamental knowledge structure of a business — 6 domains, 32 subdomains, and the questions worth answering. Pairs with Karpathy's LLM Wiki pattern.

Business DNA Wiki

Every business has a finite set of things it needs to understand about itself. Not infinite — finite. Six domains, roughly three dozen subdomains. Whether you're a solo founder or a growth-stage team, the same questions apply. The difference between companies isn't which questions matter — it's how deeply they've answered them, and whether those answers are written down somewhere an LLM can reach.

This document is a schema for that knowledge base. It defines the six strategic domains, their subdomains, and what each one captures. Think of it as the table of contents for everything worth knowing about a business — the stuff that informs positioning, messaging, product decisions, growth strategy, and investor conversations.

The important insight: even if you don't have an answer for a subdomain, that's an answer in its own right. An empt