Resources
Everything else worth reading.
The writing, the company behind it, and the fastest way to reach a person.
Resources
Three places to go.
Writing
Blog
Working notes on governed knowledge, the standards that apply to it, and what a reviewer actually asks for. 5 pieces so far.
Explore →The company
About
Who is building Cognatum, what problem it was built to solve, and the position it takes on governed knowledge.
Explore →Talk to us
Contact
Reach the team directly, or ask for a walkthrough on your own content in your own environment.
Explore →Why we write
Written to be checked.
An AI system does not go live until a review board signs it off. The people on that board do not start at a vendor site.
They start where the answer is authoritative, and each of them starts somewhere different:
- A governance lead reads the primary text first: the EU AI Act, the NIST framework, the ISO guidance.
- An architect reads the integration and permission documentation, and will not book a call to get it.
- A proposal lead reads practitioner writing on keeping an answer library current, not writing on AI governance.
- An AI leader asks peer AI leaders, analysts, and increasingly ChatGPT and Claude directly.
So what is published here cites its primary sources and links to them, in the vocabulary each of those readers already uses. It is written to be checked rather than believed.
None of it is a compliance opinion, and none of it is advice. It describes obligations that fall on your organization and the evidence a governed knowledge system can produce toward them. Where a standard is named, it is named as its issuer names it.
Knowledge governed. Intelligence everywhere.
See it on your own content, in your own environment.