START WITH ONE WORKFLOW — GIVE AI THE CONTEXT IT IS MISSING
    Penumbra

    For builders

    Build agents with a real domain model.

    Describe the objects, rules, workflows, and standards your product depends on. Penumbra turns that domain model into the types, tools, APIs, SDKs, extraction, memory, governance, provenance, and runtime context your agents need.

    See the platformMap a workflow →

    What becomes possible

    Different products. Same underlying domain.

    Builder pattern

    Vertical AI products

    Define the domain model once. Turn it into the typed resources, MCP tools, extraction pipeline, and per-customer context your product needs.

    Domain pieces

    Domain entityClient environmentDecision ruleCompliance gate

    Turns into

    • Typed resources
    • Agent tools
    • Tenant memory
    • Review gates

    Builder pattern

    Agent systems with shared meaning

    Give every agent a common type system and domain model. Agents can specialize without inventing incompatible meanings.

    Domain pieces

    TaskObservationDecisionAgent role

    Turns into

    • Per-agent MCP toolkits
    • Shared graph
    • Cross-agent reconciliation
    • Provenance

    Builder pattern

    Cognitive ETL

    The domain model becomes extraction targets, confidence rules, entity resolution logic, and quality checks. Documents hydrate the domain model directly.

    Domain pieces

    Source documentExtracted entityRelationshipConfidence signal

    Turns into

    • Extraction rules
    • Entity resolution
    • Structured API
    • Quality scoring

    Builder pattern

    Workflow operating systems

    Map how work actually moves through a domain. The workflow, tools, memory, and handoffs come from the same domain model.

    Domain pieces

    Work itemStateActorHandoff rule

    Turns into

    • Workflow runtime
    • Tool permissions
    • State memory
    • Audit trail

    Builder pattern

    Integration layers

    Partners define the same world differently. Keep those views separate where needed and reconcilable where the platform needs coherence.

    Domain pieces

    Partner schemaCanonical entityMapping ruleReconciliation

    Turns into

    • Adapters
    • Reconciliation engine
    • Interface contracts
    • Delta review

    Builder pattern

    Company brain infrastructure

    Build the company brain as governed domain context, not a pile of embeddings. The domain model becomes inspectable, extensible, and executable.

    Domain pieces

    InsightDecisionPolicySource

    Turns into

    • Search
    • Capture tools
    • Memory graph
    • Permissioned context

    The builder wedge

    Stop making agents relearn the domain at every layer.

    If your domain model is the source of truth, agents can do more than answer questions. They can call tools, remember state, follow rules, and explain where outputs came from.

    Map the domain →