Resources / About
The knowledge engine was always the product.
We spent thirty years helping companies manage their most valuable asset: their company knowledge and helping them to put it to work. We know what it means to turn information into assets companies can use.
Where the work already happens
Cognatum, the governed layer
approved · versioned · permissioned
Who asks
Who asks
Cognatum, the governed layer
approved · versioned · permissioned
Where the work already happens
The origin
Thirty years, one question.
Every proposal, every security questionnaire, every bid RocketDocs sent came out of a library where someone had already answered it and put their name to it.
Customers bought the proposal software. What made it dependable was the layer underneath, which nobody saw.
That history matters because an RFP answer is a governed answer at its most expensive. Send a prospect a claim nobody approved and the cost lands the same week.
Questions in
One questionnaire
- Where is customer data stored?
- Do you encrypt data at rest?
- Who reviews access quarterly?
- Name your sub-processors.
Already approved
Returned with its source
-
Data residency
Security · approved 2026-06-02
-
Encryption at rest
Security · approved 2026-05-18
-
Access review cadence
Risk · approved 2026-07-09
Not answered yet
Ranked, with an owner
-
Sub-processor list
Legal · due in 3 days
The product
The engine, made the product.
Your company's knowledge isn't missing. It just isn't usable. Cognatum changes that.
Cognatum is that engine rebuilt and sold on its own. AI does the maintenance work on the whole body of knowledge: it captures what the company knows, structures it, cleans it, and keeps it current. A named person holds the gate. Every live entry carries an approver, a date, and the source it came from.
We productized it now because the question buyers ask has changed. It used to be which answer is approved. Now it is whether the AI used that one, and whether you can show that it did.
Corpus health
71
| Item | Type | Health | Reach | Band | Why |
|---|---|---|---|---|---|
| Applying a legal hold to a retention schedule | Procedure | 74 ↗ was 67 | 38 answers | Healthy | cited by 38 answers · reviewed this quarter |
| Which regions are approved for data residency? | Answer | 52 ↘ was 61 | 24 answers | At risk | source changed · no owner confirmed |
| Standardize retention schedules on the records policy | Decision | 68 → was 68 | 17 answers | Healthy | stable since approval · owner active |
| How long are supervisory review records kept? | Answer | 59 ↗ was 51 | 12 answers | At risk | awaiting approval · one open conflict |
| Retention questions raised in the Q3 examination | Note | 31 ↘ was 44 | 6 answers | Critical | no approved source · superseded twice |
Why now
What buyers ask has changed.
An AI system does not go live until a review board signs off on it.
Regulated enterprises are deploying AI assistants and agents they cannot prove are answering correctly, and their AI initiatives are stalling at governance review because of it.
The question
Which retention period applies to client trade communications?
Today, without a governed home
- A slide deck from two years ago says five years.
- A policy PDF on a shared drive says six.
- A chat thread says it depends, and links nothing.
- Nobody knows which one is current.
With one approved entry
Six years, the first two in an accessible place, on non-rewriteable media.
The name
Where the name comes from.
Cognatum comes from the Latin cognatus: related by shared descent, from a common root. Knowledge inside a company should work the same way. Every approved answer comes from a source, every source can be traced, and the whole body of it hangs together instead of scattering.
Common roots. Collective intelligence.
The lineage
What we found afterwards.
Knowledge-centered service
Other people mapped this ground
We built the technology first, out of thirty years inside the proposal-response problem. Only afterwards did we find that other people had been mapping the same ground for decades.
Cognatum is informed by industry practice in knowledge-centered service, including the work of the Consortium for Service Innovation. It differs in kind. That practice is a method for people, who write down what they know as they solve a problem. Cognatum is a system plus the technology that runs it: AI does the maintenance continuously, people concentrate at the approval gate, and both people and AI systems read the result.
ISO 30401
And the same with the standard
ISO 30401:2018 sets requirements for how an organization manages what it knows. An organization can be certified to it, the way it can for quality or information security. We did not design Cognatum from the standard, and we claim no certification against it: certification assesses an organization, not software.
What we found when we read it was a clause-level match for the loop we had already built. Cognatum operationalizes the standard's knowledge development requirements, is designed to align with them, and supports a customer pursuing conformity. The full crosswalk is on the standards page.
The team
The people building it.
Cognatum is built by the team behind RocketDocs: people who have spent their careers inside proposal response, security questionnaires, and the approved-answer libraries underneath them.
Common questions
What people ask us.
Where does Sovrinty fit?
Sovrinty is a separate product from the same company, and it is the control layer. It lets you run the knowledge base on your own hardware, move it to another country, and decide which vendors and models connect to it. It works on knowledge that already lives in Cognatum, because control needs something real to hold.
Do we have to be a RocketDocs customer?
No. Cognatum is sold on its own to companies that have never used RocketDocs. A RocketDocs customer can make the knowledge base they already have a Cognatum one with no data migration, and staying a RocketDocs user and nothing else is a fine answer too.
Are you ISO 30401 certified?
No, and no software product can be. Certification assesses an organization and its management system. Cognatum operationalizes the standard's requirements and supports a customer pursuing conformity.
Knowledge governed. Intelligence everywhere.
See it on your own content, in your own environment.
KCS® is a service mark of the Consortium for Service Innovation. Cognatum is an independent product and makes no claim of conformance to, affiliation with, or endorsement by the Consortium.