Single source of truth

One source of truth for every colleague and every AI

A single source of truth for AI is one place that every tool and every colleague reads, where each fact is linked to what it rests on and kept current. Epic Context is that place for what is not code: brand, users, product, design, decisions.

The old way

Everyone works from their own copy.

The strategy sits in a deck, the personas in a slide, the decisions in a meeting note, the brand in a PDF. People bridged the gaps by hand: they knew which version held, and why.

Now an AI in every tool acts on whichever copy it finds. Search finds documents; it cannot tell which version holds.

Four workplaces, each alone in its own colour, gather into one building joined by stairs. One pulse of colour runs through and lights every screen, and the building draws together into the Epic Context mark.
  1. Everyone works apart.
  2. Joined: one truth on every screen.
  3. One brain.

An illustrationFrom a copy in every workplace to one truth on every screen. Made from our own brain, in the suite's Content app.

What happens

The copies drift, and the why gets lost.

An insight becomes a ticket, a ticket becomes a question. Every hand-over keeps the what and loses the why.

Today

Every tool keeps its own copy

Your specialists brief each one again, by hand.

Your specialists

  • The agencyTone: bold and playfulFrom last year's brief
  • Customer serviceTone: formal and carefulFrom the scripts
  • A colleague's AITone: whatever the prompt saysFrom someone's prompt
  • The website platformTone: warm and directFrom the brand kit

With Epic Context

One source, read by every tool

Your specialists keep it right, once.

Your specialists

One source · yours

Tone: warm and direct

  • A reason
  • An owner
  • Undo
  • The agencyTone: warm and directFrom the source
  • Customer serviceTone: warm and directFrom the source
  • A colleague's AITone: warm and directFrom the source
  • The website platformTone: warm and directFrom the source
An illustrationFour places a company's voice lives, before and after. Not your data.

What's at stake

Staying costs the week. Moving gives the next project a head start.

  • Re-briefing and reconciling eat the week. Specialists spend their time repeating what is true instead of deciding it.
  • Correction eats the speed. AI output comes faster, on a base that drifts.
  • Knowledge leaves. What the company knows ends up in tools it does not own, and goes when a person or a vendor goes.

What changes

The next project starts where the last one ended.

A decision can be traced to what it rests on. An AI starts from what is true instead of from what someone pasted in. People spend their time deciding what holds instead of repeating it.

And the source stays yours: you can export all of it, at any time.

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 relations every new brain starts with, so a decision always has something to rest on.

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.

How it stays true

Relations, a gatekeeper and an undo on every change.

  • Reference, not duplicate. Pages, prompts and tools point at a block instead of keeping their own copy, so a change has nowhere else to go.
  • A schema gatekeeper. Every write, by a person, an AI or an app, is checked against the block's schema; an invalid one does not land.
  • Drift detection. A reference that breaks is flagged, so nobody has to remember to check.
  • A reason and an undo on every change. Every write lands in the changes feed with who, why and from where; one click undoes it, and a whole batch reverts in one action.
  • Locks. A locked block refuses every writer, people and AI alike.
What we claim, and what shows it
What we claimWhat shows itLabel
The way of working holds up in daily useEpic Context is built on its own brain: its features and decisions live in it, each change with a reasonOur own use
AI can write to the truth safelyThe reason, the changes feed and the one-click undo run in productionVerified

Questions

What does single source of truth mean for AI?

It means one place every AI tool and every colleague reads, where each fact is linked to what it rests on and kept current. An AI that reads it starts from what is true, not from whichever copy it found.

How is it different from a data warehouse or a wiki?

A data warehouse holds your data: orders, events, numbers. A wiki holds narrative pages. Epic Context holds what your data and your work mean (the brand, users, product, design and decisions) as typed knowledge with relations. The data stays where it is.

What happens when two sources disagree?

They get linked as contradicting, and a person decides which holds. Nothing resolves a conflict silently: the editors flag it and propose, and the person who holds the block decides.

Can we take it with us?

Yes. You can export the whole brain at any time: a ZIP of markdown files with the links between pages, the messages and the images, or JSON. We do not keep a client by locking their knowledge in.

Where is it stored?

Epic Stories hosts the brain for you, and you can export all of it at any time. Running it on your own server is planned. Your architects get the details in the conversation.

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.