Concepts
Relations
Every block can say what it rests on: a feature points at the persona it serves, research supports a persona, a new decision supersedes an old one. Relations are what make the brain one connected whole instead of a pile of pages.
A single source of truth is not more context; it is context that is connected. When the tone of voice changes, you can see which messaging and content pieces lean on it. When a decision is replaced, the old one stays readable and says what replaced it. Epic Context keeps two kinds of relation.
References: what a block belongs to
Most block types carry reference fields that say where they belong: a messaging framework names its personas (personas_ref), an OGSM points at the vision (vision_ref), an architecture diagram at its tech stack (tech_stack_ref), a page in the information architecture at the features it surfaces (feature_refs). Some of these are required connections for that type, others are recommended.
- The scaffold wires the required references between its stubs, so a new project starts connected.
check_project_healthreports what is missing: orphans, empty or stub anchors, broken references, with a score and the writes that would fix them.detect_driftflags a reference that points at a block that no longer exists, and other rule violations.
Links: how two blocks relate
A link says what a relation means. An AI writes one with link_blocks, with a reason, and a person sees it beside both blocks.
| Type | Means |
|---|---|
supports | is evidence for |
contradicts | says the opposite of |
supersedes | replaces, from now on |
derived_from | was extracted or summarised from |
decides | is the decision about |
implements | is the realisation of |
governs | sets the rules for |
overrides | deviates, deliberately, from |
duplicate_of | says the same as |
mentions | refers to |
Three rules come with them:
- Replace, don't overwrite.
supersedesmarks the older block superseded. It stays readable with its history; it just no longer counts as current. Replacing a link ends the old link instead of editing it. - A derived link is not evidence. Links of class
derived(what an AI extracted or summarised) never count as proof that something is true. - A link is a write. It goes through the same lock rule as any other write, so a locked block cannot be linked from.
Links in the text
Inside a page, a markdown link to a bare block key, such as [our primary persona](primary-persona), resolves to that block's page, first in the project and then in the organisation. Write links this way and they survive a block being renamed or moved between groups.
Seeing the relations
The Map draws the whole graph in 3D from both kinds of relation: references and typed links. Open it from any page and it focuses on that block and its neighbours.
Here it draws the relations every new brain starts with: the references the scaffold wires between its stubs (dark when required, light when only pre-wired) and the typed links it lays between the shared blocks, such as the tone of voice that governs the messaging.

- 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.
The scaffold's own relations, no project's data.
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.
Next
- Lifecycle: stub, assumed, validated, superseded.
- Writes, changes and locks: how a change is recorded.
- MCP tool reference:
link_blocks,get_evidence_forand the rest.
Last updated: