A knowledge base stores information and waits to be read, so it rots. This puts knowledge to work in everything you make, and finished work offers what it added back to the base, for a person to accept.
The memory of your organization. Everything it knows, captured as sourced facts, structured by a curated taxonomy, and available to everything you make.
Learn next: Strategic Composition · Governance · Asset Library · Collections · Datasets · Signals · Personas
The governed body of what your organization knows, held as sourced facts. It is not a knowledge base that sits and waits to be read. It puts knowledge to work in everything you make, and a finished deck or document offers back what it added, for a person to accept. Facts, positioning, proof, methodology, people, and customer stories all live here with their provenance.

Organizations do not lose knowledge. They lose access to it. Captured once, it is available everywhere, and it stays when people leave. The intelligence base is the foundation; every other capability is a view of it.
Uploads and websites are read as they arrive, scoped to the project or customer they belong to, checked for what you already hold, and turned into sourced facts. Knowledge is organized by a curated taxonomy of more than 300 fields across 15 modules. Every fact carries its source, and citations run both directions, from a claim to its source and from a source to everywhere it is used. Foundation presents it in five groups (your brand, how it looks, how it sounds, your organization, and what you sell), and a per-member team extractor turns people into deduplicated cards.
Each source is read for whose it is. A tender or a client's own document is read as theirs, so their requirements are never claimed as yours, and you can correct the call. A PDF is transcribed in its own language and wording, with any part that cannot be read marked as such, and the text in an uploaded screenshot or scanned table is read too. Each fact from a PDF names the page it is on, counted from the first page of the file. The PDF itself is kept, privately, so you can open the original from its source and check a fact against the page. Uploading the same PDF again reuses the reading already made. A report marked confidential (client confidential, proprietary or not for distribution) keeps its facts restricted by default: only administrators see them, and Gyrium leaves them out of what it writes. That covers the pages read later and the facts of its figures too. It is a choice, made when you upload and changed later by an administrator. A long report, from 15 pages, can be indexed first: Gyrium maps every page and keeps the report's key findings, quoted word for word, as facts, and you read more pages in full when you need them. A web link that leads to a PDF is read the same way as an uploaded PDF, and the source remembers the link it came from. A link to another kind of file (a Word document, a spreadsheet, an image) is named for what it is, so you know to upload it instead.
Every fact is labelled with the language it is written in, whichever way it arrived: read from a source, typed in by hand, or taken from a team profile. A French source can therefore stand behind an English piece, and its facts are still read as French.
Some of what an organization knows should never be written into a communication. Bank details, insurance policies, your discount policy and your data protection contact are held apart: only an administrator can see them, and they are kept out of composition unless an administrator deliberately turns that on.
Some of it must come out word for word. Your approved about-us paragraphs, your legal disclaimer and your copyright line are marked to be reused exactly as written, so the wording your lawyers agreed is the wording that ships.
Specifications come apart into facts you can cite. Each value on a datasheet, a load rating or an operating temperature, becomes its own fact, and a name and its value stay together when they are composed, so a figure never attaches to the wrong product. A number keeps its qualifier too: "not more than 48 hours" is held as an upper limit, a range stays a range, and an approximate figure is never presented as a measurement.
Each customer carries a profile: what they offer, where they operate, their market, who they sell to, the problems they face, their competitors and what they stand for. Every field shows where it came from and when. The profile is read in the customer's own language and grounds every piece you make for that customer, so nobody retypes it into a brief.
A finished deck or document offers back what it added. A claim in it that no fact supports is offered as a candidate new fact, with the words it was quoted from, and it joins the base only when a person accepts it.
A knowledge base stores information and waits to be read, so it rots. This puts knowledge to work in everything you make, and finished work offers what it added back to the base, for a person to accept.
Yes. Each organization is isolated on every request, never composes into another organization's work, and is never used to train shared models.
Their expertise stays, captured as sourced facts, and keeps composing future work.
The cold-start onboarding wizard is partial. Deduplication catches the same fact said two ways, and how close a match has to be is still being tuned. Blueprints are looked after by the people who curate the base. Everyone picks one when they create something; authoring them is a curator's job, and they are built from a few questions or extracted from work you already have.
Get in front of the right audience
Stay useful and top of mind
Build authority and trust
Purpose, positioning, promise, and the personality underneath them.
Documents, research, presentations, your website. The material you already work from.
Everything on a single subject, in one place, without moving any of it.
The people you are writing for, described well enough to write to.
Who they are, what they do, and the expertise the work can draw on.
Foundation, collection, customer, project or campaign, and how to tell which.
A record you can read, and reverse.
Strategy before words. Gyrium sets the objective, the narrative, and the structure before it composes, grounded in your intelligence base.
One source of truth. Sourced, isolated, approved, versioned, exportable, and owned by the customer.
Your images, logos, and graphics, indexed by what they show and scoped to where they belong, ready while you compose.
A collection gathers what your organization knows and says about one topic, such as safety or a law you work under, apart from what you sell, so a piece can be about that topic with or without a product.
A spreadsheet stays a spreadsheet. Gyrium reads it, understands its units, and states what it says, without shredding the grid into loose facts.
What is happening outside your organization, captured beside what you know about it, so external context carries a source.
Who you are talking to, as an audience and the people inside it, held as part of your intelligence so strategy is set against someone real.
The pilot takes a small number of organizations at a time. Bring what you already have.