Knowledge is used by regulated organizations building AI applications and agents that automate processes with rule-driven decisions. The product is horizontal ; the sections below are three ways to enter the same thesis.
Build with Knowledge
The horizontal use case Knowledge is designed for.
| Page | Framing |
|---|---|
| AI-powered applications & agents | You (or your integrator) are building agents or AI-powered workflows that make rule-driven decisions. Knowledge is the policy authority those agents consult, so business rules do not have to live inside the model. |
For your team
Different parts of a regulated organization interact with rule-governed decisions differently. These pages frame Knowledge from each perspective.
| Persona | Framing |
|---|---|
| AI & Automation teams | You build the agent. Integration, APIs, progressive context, how Knowledge fits your architecture from a two-person team to an internal AI factory. |
| Compliance & Risk | You own the rules. Edit them directly, watch them fire, reconstruct any decision, without engineering as a gatekeeper. |
| Security & Platform | You review security and architecture. The trust model, keys inventory, deployment shapes, honest compliance posture. |
Operations & Business teams — the process owners and business SMEs — is a perspective we surface in customer conversations rather than as a standalone persona page yet. If that is you, start on the AI & Automation teams page for context and reach out on Contact with your process.
Knowledge in practice
Concrete applications of the same horizontal product. Each is a class of decisions Knowledge handles ; the moteur is generic.
| Application | Status |
|---|---|
| Wealth suitability | Reference implementation — structured-product distribution decisions : eligibility, suitability, cross-border, concentration. |
| KYC / KYB admission | Example application — composite onboarding and admission decisions across regulated verticals. |
| Healthcare authorization | Example application — coverage, authorization and administrative decisions in policy-driven healthcare workflows. |