Domain objects
The customers, accounts, cases, claims, deliverables, decisions, or workflows your product is actually about.
Build on Penumbra
Describe the objects, rules, workflows, and standards your product needs. Penumbra turns that domain model into tools, APIs, extraction, memory, guardrails, and provenance your agents can use.
What the domain model gives you
The customers, accounts, cases, claims, deliverables, decisions, or workflows your product is actually about.
Tools generated around the domain model, so agents can act on real business objects instead of loose text.
Typed interfaces over the domain model, so your app and agents work from the same definition of the domain.
Documents, calls, tickets, and systems hydrate the domain model directly instead of producing another blob of text.
Work leaves behind structured state agents can reuse, not just transcripts someone has to search later.
Rules, review standards, and permissions travel with the domain model instead of living in scattered prompts.
Every output can show what source, rule, domain object, or prior decision shaped it.
Agents get the relevant domain context and state at runtime without carrying the whole company in the prompt.
The problem
The vector store knows documents. The workflow engine knows steps. The database knows tables. The agent knows prompts. None of them knows the domain the way your product needs it.
Penumbra gives the stack one domain model. Agents can use it to find context, call tools, follow rules, remember work, and explain where outputs came from.
How to adopt it
Map one workflow, agent, product surface, or corpus. You do not need an enterprise-wide modeling program to start.
Without a shared domain model, every tool in the stack invents its own version of the domain. Penumbra gives them one source.
Agents need tools, memory, rules, and provenance. Penumbra turns the domain model into the pieces they need to do work.
Each workflow adds more structure. The company brain emerges from connected useful pieces, not one giant upfront schema.
The simple version
A prompt can explain a task. A domain model lets the system keep working after the first answer: with tools, memory, rules, and provenance.
Bring us a workflow →