Skip to content

Concepts

Groups and entities

The brain has a fixed shape: eight groups, each answering one question, and thirty-four kinds of knowledge (entities) inside them. Every project has the same structure, so people and AI always know where a thing lives.

A wiki grows by adding pages; the brain grows inside a shape that is decided once. That shape is what lets an AI find the tone of voice, the primary persona or the decision behind the architecture without searching, and what lets two projects be compared.

The eight groups

GroupThe question it answersEntities
BrandHow do we show up?Vision, Positioning, Tone of voice, Messaging
StrategyWhere are we going?Product strategy, Business model, OGSM, Roadmap, Business case
UsersWho for and why?Persona, Jobs to be done, Journey map, Customer insight, Competitor, Research
ProductWhat is it?Overview, Feature, Glossary, Information architecture, Content
DesignHow does it look and feel?Design system
BuildHow does it work?Tech stack, Architecture, Infrastructure, Decision, Legal, Finance
MarketingHow do we grow?Marketing strategy, Campaign, Channel, Content piece
PerformanceIs it working?Analytics, KPI, Feedback

That is 4 + 5 + 6 + 5 + 1 + 6 + 4 + 3 = thirty-four entities. The set is deliberate: a new kind of knowledge is a change to the model, not something a project adds on its own.

Blocks, block types and entities

The unit you read and write is a block: one page of the book, with a key (primary-persona), a name, a markdown body and some structured fields. Each block has a block type, and each block type belongs to one entity. Several types can share an entity when they are different forms of the same knowledge:

EntityBlock types
Positioningbrand_positioning
Business casebusiness_case, swot_analysis, porters_five_forces, strategic_group_map, obeya_board
Information architectureia_tree, taxonomy
Architecturearchitecture_diagram, data_model, data_schema, api_endpoint, api_spec
Design systembrand_visual_identity, brand_asset, component_spec, design_application, figma_embed, storybook_link and more
KPIkpi, north_star

You rarely need the type names. An AI uses them when it creates a block; the MCP tools and the API return the schema for each type, and the schema gatekeeper refuses a value that does not fit it.

A new project starts complete, as stubs

Creating a project scaffolds one block for every entity, filled with sensible defaults and marked stub. The tone of voice starts as "professional, direct, warm"; other stubs carry the sections to fill in and the bar a page must meet before it counts as written. Nothing is missing on day one; what is not yet specific to you says so. Running the scaffold again (scaffold_v3_project) only adds what is not there yet. See Lifecycle for how a stub becomes assumed and validated.

The stubs also start connected: the scaffold lays the relations between them, so no block floats. This is that first shape, drawn the way the Map draws a brain: the thirty-four entities in their eight groups.

The relations every new brain starts with, in 3D: 34 kinds of knowledge as spheres in 8 coloured group clouds (Brand, Strategy, Users, Product, Design, Build, Marketing, Performance), joined by 59 threads. The largest spheres are Persona, Overview, Feature and Positioning.
  • Brand
  • Strategy
  • Users
  • Product
  • Design
  • Build
  • Marketing
  • Performance

How to read it. Every sphere is one kind of knowledge a new brain starts with, in its group's colour. Every thread is a relation laid before anyone writes a word: a dark one is required, a light one is pre-wired and may go. The bigger the sphere, the more relations run through it.

Vision is the root
Strategy, positioning and the overview point straight at it. Everything else reaches it through them.
Persona is the second hub
Jobs, journeys, research, messaging and marketing all say who they are for.
Feature carries the product
Business cases, content, analytics and feedback all hang from a feature.
Tech stack carries the build
Architecture and infrastructure hang from the tech stack. Cost hangs from the overview, and a KPI from the OGSM.

A new project's brain before anyone writes a word.

Every relation, in words

Brand How do we show up?

  • Vision Holds Positioning, Product Strategy, Business Model, OGSM, Overview.
  • Positioning hangs from Vision, Persona (a typed link). It holds Tone of Voice, Messaging, Design System, Glossary (pre-wired), Marketing Strategy (pre-wired).
  • Tone of Voice hangs from Positioning, Messaging (a typed link), Glossary (a typed link). It holds Content Piece (pre-wired), Design System (a typed link).
  • Messaging hangs from Positioning, Persona. It holds Marketing Strategy, Content Piece (pre-wired), Tone of Voice (a typed link), Glossary (a typed link), Legal (a typed link).

Strategy Where are we going?

  • Product Strategy hangs from Vision, Overview (pre-wired). It holds Competitor, KPI, Roadmap (pre-wired), Marketing Strategy.
  • Business Model hangs from Vision.
  • OGSM hangs from Vision. It holds Roadmap (pre-wired).
  • Roadmap hangs from Product Strategy (pre-wired), OGSM (pre-wired).
  • Business Case hangs from Persona, Feature.

Users Who for and why?

  • Persona Holds Messaging, Jobs to Be Done, Journey Map, Research, Business Case, Customer Insight, Marketing Strategy, Campaign (pre-wired), Channel, Positioning (a typed link).
  • Jobs to Be Done hangs from Persona.
  • Journey Map hangs from Persona, Content (pre-wired).
  • Customer Insight hangs from Feature (pre-wired), Persona.
  • Competitor hangs from Product Strategy, Feature (pre-wired).
  • Research hangs from Persona.

Product What is it?

  • Overview hangs from Vision. It holds Feature, Information Architecture, Glossary, Tech Stack, Legal, Finance, Product Strategy (pre-wired).
  • Feature hangs from Overview. It holds Business Case, Customer Insight (pre-wired), Content, Analytics, KPI (pre-wired), Feedback, Competitor (pre-wired).
  • Glossary hangs from Overview, Positioning (pre-wired), Messaging (a typed link). It holds Tone of Voice (a typed link).
  • Information Architecture hangs from Overview.
  • Content hangs from Feature. It holds Journey Map (pre-wired).

Design How does it look and feel?

  • Design System hangs from Positioning, Tone of Voice (a typed link).

Build How does it work?

  • Tech Stack hangs from Overview. It holds Architecture, Infrastructure, Finance (pre-wired), Decision (pre-wired).
  • Architecture hangs from Tech Stack.
  • Infrastructure hangs from Tech Stack.
  • Decision hangs from Tech Stack (pre-wired). It holds Legal (pre-wired).
  • Legal hangs from Overview, Decision (pre-wired), Messaging (a typed link).
  • Finance hangs from Overview, Tech Stack (pre-wired).

Marketing How do we grow?

  • Marketing Strategy hangs from Product Strategy, Messaging, Persona, Positioning (pre-wired). It holds Campaign, Channel (pre-wired).
  • Campaign hangs from Marketing Strategy, Channel, KPI (pre-wired), Persona (pre-wired). It holds Content Piece.
  • Channel hangs from Persona, Marketing Strategy (pre-wired). It holds Campaign, Content Piece.
  • Content Piece hangs from Campaign, Channel, Tone of Voice (pre-wired), Messaging (pre-wired).

Performance Is it working?

  • Analytics hangs from Feature.
  • KPI hangs from Feature (pre-wired), Product Strategy. It holds Campaign (pre-wired).
  • Feedback hangs from Feature.

The same shape for other kinds of work

The model is the same for a digital product, a physical product, a service, a programme or a department. A project's kind of work changes the words people read, which entities rest and what a stub asks, never the thirty-four entities themselves. An organisation and a project can also set their own words for groups and entities (Settings › Brain › Words), so the book speaks the team's language while the AI still sees the canonical names.

Outside the thirty-four

The brain also holds things that are not entities: documents you upload, the rules and learnings agents save with save_rule and log_learning, meeting notes, reports (one_pager) and development work (epic, user_story, task, kanban_board). They link into the graph but do not count towards a group.

What it does not hold

Code. The repository stays the source of truth for how the product is built; the brain holds why, for whom and to what standard. An agent that builds UI reads the design system and the page from the brain and writes the code in the repo.

Next

Last updated: