Beyond the wiki

A wiki adds pages. A brain adds relations.

A wiki is good at narrative and bad at telling an AI which version holds. Epic Context starts every brain connected (thirty-four kinds of knowledge in eight groups, with their relations laid), so an answer comes with what it rests on. Keep your wiki for the story; let the brain hold what is true.

Searching pages

Search through pages returns versions, not the truth.

A wiki made sense: people write pages, people read pages, and a person knows which one is current. It is good at narrative and at explaining why.

An AI acts on pages differently. It finds three versions of the same decision, quotes last quarter's, and cannot tell which one holds. More pages make that worse, not better.

Start from relations

Every new brain starts connected.

Epic Context starts from relations instead of pages: thirty-four kinds of knowledge in eight groups, with their relations laid before you write a word. You fill it in; the shape is ready.

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.

The brain every new organisation and project starts as, drawn the way the context map draws it.

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.

A head start

Don't rethink what has already been thought through.

Every new organisation and project starts with the structure and its standard connections, each kind of knowledge as a stub that hangs from something. Nothing begins empty, and nothing floats.

Each block then grows from stub to assumed to validated, and a glance at the book shows how proven each part is.

Side by side

A wiki and a brain do different jobs.

This is not a takedown. A wiki such as Notion or Confluence keeps narrative documents; Epic Context keeps the typed graph. Here is what each does well.

A wiki and Epic Context, side by side
A wikiEpic Context
StructurePages in a tree you designEight groups and thirty-four kinds of knowledge, the same in every project
RelationsLinks you add by handTyped relations, the required ones laid from the start; drift detection flags one that breaks
What holdsThe newest page, if someone updated itOne block per fact, with its state: stub, assumed or validated
ChangesA page historyA reason, a source and an owner on every change, and a one-click undo
AISearch over pagesA briefing per task over MCP, and writes with a reason
Good forNarrative, meeting notes, how-tosWhat is true, and how it connects

Together

Keep the wiki, and link to it.

They work together. Keep the wiki for the story, the meeting notes and the how-tos; let the brain hold what is true, and link from one to the other.

Questions

Is Epic Context a Confluence or Notion alternative?

For what is true and connected, yes: the brand, users, product, design and decisions your people and AI work from. For narrative documents and meeting notes, keep your wiki. The two do different jobs and link to each other.

Can we bring in what the wiki holds?

Yes, as text with a source. A document, a transcript or a page can be read in; what it finds lands as writes with a reason, and a whole run can be reverted in one action. We plan what to bring in with you, and we do not promise a migration.

Why not just search our wiki with AI?

Search finds pages that look like the question; it cannot tell which version holds or what a fact rests on. That works for finding a how-to. It does not work when an AI acts on the answer.

What stays in the wiki?

Narrative: the story behind a project, meeting notes, how-tos and long explanations. Epic Context keeps the typed knowledge those pages talk about, and the two link to each other.

Start with one real project

Epic Stories installs Epic Context with your team, on your own work, and then steps back. Tell us where you would start.