Context Central reads every change to your code, gathers the story behind it from the tools your team already uses, and keeps onboarding guides, product docs and API references accurate - automatically.
auth: require 2FA for admin sign-in
Admins sign in with their work email and password, then land on the dashboard.
auth/signIn.ts:13 · SEC-212
PA Review requested
The problem
Every merged change makes some page a little more wrong. Nobody notices until a new hire follows outdated steps, a customer reads a stale guide, or support answers from last quarter’s version.
Once people find one wrong page, they stop reading all of them.
Hours go into rewriting docs instead of building product.
Code vs. documentation, over a quarter
Your code Your docs
Docs only change when someone finds time. The gap keeps growing.Docs update alongside every change — reviewed, approved and published.
How it works
Like a healthy tree, good documentation grows from strong roots.
Code is the only thing that’s always true about how your product works. Context Central connects to your git provider and maps your codebase into a knowledge graph: every service, function, API and how they depend on each other.
AI agents watch that graph. When a change is merged, they know exactly which parts of the system moved — and which pages describe them.
Code tells you what changed. Tickets, specs and planning docs tell you why. Context Central links each change to the conversations behind it, so docs explain intent — not just mechanics.
API specs, READMEs and design files fill in the details people actually look for: endpoints, setup steps, screens and flows. Only what’s relevant to the change is pulled in.
You decide what good documentation looks like: the audience, structure, tone and rules for each doc. Context Central uses that inference layer to write and maintain every page — then routes updates for approval before anything is published.
Every change, end to end
No one has to remember to update the docs. Here’s the path a single merged change takes.
A developer merges a change, like any other day.
The code graph pinpoints which docs are now out of date.
Linked tickets, specs and designs explain the why.
Agents rewrite only the affected sections, in your style.
The right owner approves, edits or sends it back.
↺ or back to redraftEveryone sees the accurate version, with sources attached.
Connectors
No migration, no new habits. Connect your sources once and Context Central keeps listening — so knowledge scattered across a dozen tools ends up in one accurate place.
…and more connectors growing every month.
Docs you get
The same living context becomes different documents for different readers — each one written the way that audience needs it.
Governance
AI does the heavy lifting. People stay in charge of what gets published and who gets to see it.
Roles at the organisation and project level decide who can see, edit and approve each document.
Organisation
Project · Payments API
RM Extra permissions for Editor granted by an admin
Every AI-drafted change waits for the right person to sign off. Nothing goes live by surprise.
Who can approve
Who it’s for
Faster onboarding and fewer “how does this work?” interruptions.
Ship code. The docs follow without a separate chore.
Product docs that match what actually shipped this week.
Answer customers confidently from pages you can trust.
FAQ
Instead of writing docs once and letting them age, documentation is updated continuously as your product changes. Each time code is merged, Context Central works out what that means for your docs and drafts the update for review.
Tickets get closed, specs get outdated and meeting notes get lost — but the code is what actually runs. Context Central starts from the code (its “code context”) and adds business and external context on top, so documentation never contradicts how the product really behaves.
It’s your set of instructions for each document: who it’s for, how it should be structured, what tone to use and what to include or leave out. You provide it once; Context Central follows it every time it writes or updates that doc.
Only if you want it to. Approval workflows let you require sign-off from an admin, or from any member who has been given approval rights, before an update goes live.
No. Developers keep using their usual git provider, tickets and docs. Context Central connects to those tools and works in the background.
You do. You choose which repositories and sources to connect, and role-based access control decides who can view, edit or approve each organisation, project and document.
Connect your code and tools in minutes. See your first always-accurate document the same day.