Extensions
Extend what the understanding is built from.
The Context API and MCP are how an application reads Percidian ACE. Extensions are the other direction: the stores, databases, and individual enterprise systems a business runs on, brought into the same governed understanding — built by the team who knows that system best.
ACEIndexIdentityPurposeMemoryPermissionEvidenceWhy extensions exist
The systems that matter most are the ones nobody else has connected.
These are software extensions, not the use-case and organization-specific layers of a modular ontology. They are code, they run against a source, and they are how information gets in.
Supported connections cover the systems most enterprises share — content, communications, applications, structured data, identity. What they do not cover is the internal store built eleven years ago, the warehouse table that is the only accurate record of a business process, or the one regulated system a supported connector will never reach because only three organizations run it. Those are rarely peripheral. They are usually the reason a question cannot be answered.
An extension is how that system joins the understanding without waiting for a roadmap.
Check you need one first. If what you want is governed delivery to an application you already have, the Percidian Gateway is the shortcut and it is already built — routing evaluated at the edge, provider and model policy, access control per destination, an audit record on every delivery, and the assembled context and permitted tools travelling with the call. Extensions are for the sources it deliversfrom.
What you can build
Four shapes, one destination.
Each contributes to the same governed understanding, so a fact that arrives through an extension is retrieved, permissioned, and cited exactly like one that arrived through a supported connection.
Data stores
Databases
Enterprise connections
Modules
The systems already connected. An extension adds the one that is only yours.
The contract
What every extension has to keep true.
An extension widens what Percidian can understand. It never widens who can see it — the guarantees below are the reason an extension can be trusted with the same questions as everything else.
- Identity travels with the request
- An extension is asked for information on behalf of a person or an agent, never on behalf of itself. A service account that can read everything is not a connection; it is a bypass.
- Permissions resolve at read time
- The source stays authoritative about who may see what. Access is evaluated against it when the question is asked — not captured at indexing and trusted afterwards, which is how a revoked permission keeps answering for months.
- Every fact keeps its source
- What comes back carries the record it came from, so evidence returned through an extension is as checkable as evidence from anywhere else.
- Change propagates
- New records, revisions, moved files, changed access, and deletions update what Percidian can understand and deliver. An extension that only ever adds is a snapshot, and a snapshot goes wrong quietly.
Building one
Start with the system, not the interface.
The extension interfaces are not published. That is deliberate while they are still moving — a signature on a marketing page that no longer matches the code costs a developer more than no page at all.
What we do instead is work through it directly. Tell us the system, how it authorizes a reader, and what a useful answer from it looks like; we will map it to the right shape above, share the current interface, and say plainly whether it is ready for what you want to do with it.
Bring your business into every AI decision
Give every approved AI system the context to do its best work.
Connect the knowledge your organization already has. Preserve what it learns. Apply the permissions it already trusts. Make that understanding available wherever people and agents work.