Give AI agents reliable knowledge when they're trusted with enterprise work. Amorfs Knowledge Packs deliver exact records, with identity, relationships, time and source already attached.
Companies want agents that can answer, explain and act on validated internal data.
Questions like:
Which asset is installed where?
Who controls an entity?
What was true on a given date?
Which source supports the answer?
These aren't just questions about finding information. They are questions about getting the record right.
For an agent that is only generating text, a relevant passage may be enough.
For an agent that is making a decision, preparing an audit response, investigating an issue or taking an action, the wrong record can lead to the wrong outcome.
Trustworthy answers need to consider identity, relationships, time and source.
That matters because agents are moving beyond generating text. They're being used to investigate, make decisions and take actions.
The usual options still leave the agent with the hard part:
API — gives the agent access to live systems, but leaves it to choose what to retrieve.
RAG — gives the agent relevant passages, but doesn't guarantee the complete record.
SQL — gives the agent query power, but leaves it responsible for understanding the schema and constructing the right joins.
In each case, the agent still has to reconstruct the record.
A Knowledge Pack is a versioned, immutable snapshot that an agent can query directly. There is no query language to invent, no embedding service and no live connection to production. Nothing leaves your environment.
The difference
Facts, not clues.
Agents shouldn't have to rebuild identity, relationships, time and source before they can answer. In a Knowledge Pack, those facts live in the record.
The agent has to reconstruct the answer from fragments.
Find the subsidiary
Identify the owner
Join the ownership history
Interpret as-of dates
Establish provenance
Reconstruct the record
Six reconstruction steps. Each is another opportunity to get the entity, relationship, date or source wrong.
With Amorfs:2 steps
The record is already structured.
1
Choose the structure
named entity
ownership relationship
valid on 15 March 2024
source filing
2
Ask for the record
The record comes back together with the owner, date and source. The agent doesn't have to reconstruct the context.
Why packs
Access isn't knowledge.
System access lets the agent reach source data. It still has to work out what the data means, how it connects, what was true when, and where it was sourced.
App connectors
Gmail or Drive give an agent access to documents and messages. They don't turn that information into a bounded, queryable record of facts.
API wrappers
Add a tool for every endpoint, and choosing the right tool is where agents slip.
Search
Returns relevant passages, with no guarantee that nothing is missing.
Databases
Have full query power, but the schema doesn't explain itself.
Knowledge Packs work differently
Every pack uses the same small set of tools, so adding new knowledge doesn't add new tools. The pack describes itself: what it holds, how records link, and starter queries that show how and where to find records. Records come back structured, with time and source on every link. If anything was cut, the answer says so.
Packs complement Gmail and Drive; they don't replace them.
Data access vs Knowledge Pack
Attribute
Data access
Knowledge Pack
What comes back
Passages or rows
Complete records
Structure
Undocumented schema
Self-describing
Time and source
Assembled afterwards
On every link
Context
Reconstructed by the agent
Built into the record
Completeness
Unknown
Stated
Tools
One per endpoint
Same small set
How it works
Three steps. No reconstruction.
Open the pack → Read the map → Ask for the record
A standard MCP connector provides agent access across all the major AI platforms.
knowledge-pack/Local folder · read-only
Opened
01
Open the pack
A local, read-only file or folder. It is not a live database connection.
Record counts
Distributions
Samples
Starter questions
02
Read the map
One read tells the agent what the pack holds, how records link and how to ask. The agent needs no prior training on the dataset.
IDidentity
as of15 Mar 2024
sourceerp
name*
03
Ask for the record
Describe the record you need and the pack returns it. Follow-up questions stay within the same record.
No query language to write. No search results to piece together.
Properties
Complete records with their context.
Everything the agent needs to know is stored in the record, so it never has to reconstruct identity, relationships, time or source. When an agent is going to make decisions or take actions, getting the record right matters more than finding relevant text.
The specified record, not a similar match.
The agent gets the entity it asked for, rather than having to choose between similar results.
The date is included.
Historical questions can be answered against what was true at the time.
The source comes with it.
Evidence travels with the record rather than being reconstructed afterwards.
Only what the task needs.
The agent receives the relevant records, not an unrestricted dump of source data.
If something's missing, it says so.
The agent can distinguish incomplete results from complete ones.
Diagnostics.
The pack provides hints about where to look next.
Achievements
One knowledge model. Very different data.
We've built Knowledge Packs across industrial assets, legal records, corporate entities, geography, venture funding and pharma — from thousands to tens of millions of facts.
Industrial assets
258kfacts
Venture funding
21mfacts
Corporate entities
86mfacts
Geographic knowledge
111kfacts
Pharma
6mfacts
The point isn't the size of any individual pack. It's that the same structure and agent interface works across fundamentally different domains.Now we need to prove it on your data.
The next test: your data.
Demo packs show the model works across domains. They don't show it works on messy production data in your environment. That's what the four-week evaluation is for.
Agents that make decisions and take actions need knowledge they can rely on. Finding fragments of text and guessing what they mean isn't good enough for business. So I built Amorfs.
Pete has spent more than 30 years working at the intersection of enterprise technology, architecture, data and complex business systems, including senior technology roles, at EY, Capgemini, Accenture, UBS and Barclays.
At EY, he spent a decade as Asia Pacific Technology Director for Enterprise Architecture.
He built Amorfs from a simple observation: enterprise systems contain enormous amounts of structured knowledge, but today's AI systems are largely designed to retrieve text rather than reliably reason from the records themselves.
First Cognition Pty Ltd is a privately funded company. We build Amorfs, knowledge infrastructure for AI agents. Amorfs Knowledge Packs put enterprise data directly into an AI agent's hands.
Evaluation
Test it against what you use today.
Prove the difference on your own data. A four-week evaluation against 20 real questions, measured against your current approach. This is a paid evaluation.
Step 1 · 20 minDemo
Step 2 · 4 weeksEvaluation
Step 3 · ReportScorecard
The result shows whether Amorfs makes a measurable difference on your real questions, with the evidence and context required to trust the answer.
You decide whether the difference is worth taking further.
What we measure
Correctness: is the answer exactly right?
Consistency: does the same question against the same pack give the same answer later?
Evidence: can the agent show the record it used?
Provenance: where did that record come from?
Validity: was it true on the date that matters?
Size: how much did the agent need to read?
You agree the questions and answers before anything is scored, so the result doesn't rest on our word.
Is getting the record right important to your agent?
Amorfs is a fit when an agent needs to work with connected enterprise records and the consequences of getting the facts wrong matter.
You have connected enterprise records
Your agents need exact answers
Identity, relationships and time matter
You already have a current approach to compare
You can define 20 questions with known answers
You can provide a masked extract
You want to test this without changing production systems
If you lead a plant or asset data team, MDM or data governance, compliance or financial crime, legal operations, or another agent programme where getting connected records right matters, start with a twenty-minute demo on the synthetic unit.
Do not send extracts to this website. If we proceed, the extract is versioned in your environment under a signed evaluation agreement.
Facts, not clues. See the difference.
Run Amorfs against your current approach on a masked extract that never leaves your environment. No production credentials, no cloud ingest, no new platform.