Agency Engine is the shared application core for product teams building AI apps, so that each new app starts with approvals, records and permissions already in place.
Preserve shared contracts and the declared protected control set.
Versioned kernel and compatibility contracts.
Preserve shared contracts and the declared protected control set.
Versioned kernel and compatibility contracts.
Policy, evidence, approvals, model access, disclosure and custody.
Product configuration cannot remove the protected control responsibilities.
Validate the declaration and select domain services and interface vocabulary.
Versioned service and interface selection.
Protected and replaceable seams.
Selected reviewed version; earlier work retains earlier lineage.
Validate the declaration and select domain services and interface vocabulary.
Configured, refused and unknown states.
Selected product services, shell and versions.
An invalid or unsupported declaration remains refused or unknown.
Supply organization records and restrictions independently from reusable product identity.
Selected organization records and roles.
Inherited limits that local context cannot widen.
Supply organization records and restrictions independently from reusable product identity.
Roles, relationships and current operational records.
Installation, organization and workspace may narrow inherited authority.
Local configuration may narrow inherited authority; it does not create a broader grant.
Translate proposed work into typed steps, dependencies, budgets and available routes.
Current work context and effective restrictions.
Typed intended work and output.
Completed prefix and unresolved work for the next plan.
Translate proposed work into typed steps, dependencies, budgets and available routes.
Declared work/output contracts.
Cycles, missing routes and budget/policy diagnostics.
Missing routes, cycles and budget or policy conflicts remain visible diagnostics.
Perform the selected domain method through its eligible execution ports.
Valid product composition.
Eligible typed steps and declared execution ports.
Perform the selected domain method through its eligible execution ports.
The selected commercial or organizational method.
Draft/result, explicit wait or unavailable integration.
An unavailable integration remains unavailable; a draft is not an external delivery.
Reconstruct work from transitions and keep replaced methods/agents identifiable.
Actual result, wait or indeterminate transition under its work identity.
Reviewed method/agent replacement with a new version.
Reconstruct work from transitions and keep replaced methods/agents identifiable.
Completed results, pending obligations and anomalies.
Earlier versions remain; restoration creates a new version.
A replacement or restoration retains earlier versions and pending obligations.
Versioned kernel and compatibility contracts.
Preserve shared contracts and the declared protected control set.
Versioned kernel and compatibility contracts.
Policy, evidence, approvals, model access, disclosure and custody.
Product configuration cannot remove the protected control responsibilities.
Versioned service and interface selection.
Protected and replaceable seams.
Selected reviewed version; earlier work retains earlier lineage.
Validate the declaration and select domain services and interface vocabulary.
Configured, refused and unknown states.
Selected product services, shell and versions.
An invalid or unsupported declaration remains refused or unknown.
Selected organization records and roles.
Inherited limits that local context cannot widen.
Supply organization records and restrictions independently from reusable product identity.
Roles, relationships and current operational records.
Installation, organization and workspace may narrow inherited authority.
Local configuration may narrow inherited authority; it does not create a broader grant.
Current work context and effective restrictions.
Typed intended work and output.
Completed prefix and unresolved work for the next plan.
Translate proposed work into typed steps, dependencies, budgets and available routes.
Declared work/output contracts.
Cycles, missing routes and budget/policy diagnostics.
Missing routes, cycles and budget or policy conflicts remain visible diagnostics.
Valid product composition.
Eligible typed steps and declared execution ports.
Perform the selected domain method through its eligible execution ports.
The selected commercial or organizational method.
Draft/result, explicit wait or unavailable integration.
An unavailable integration remains unavailable; a draft is not an external delivery.
Actual result, wait or indeterminate transition under its work identity.
Reviewed method/agent replacement with a new version.
Reconstruct work from transitions and keep replaced methods/agents identifiable.
Completed results, pending obligations and anomalies.
Earlier versions remain; restoration creates a new version.
A replacement or restoration retains earlier versions and pending obligations.
An illustrative process for composing product services and retaining organization work.
Additional mechanisms are described in the technical reference.
A versioned foundation supports product composition and organization context. Together they shape a bounded plan, contracted service work and a durable record of the result.
Keep gates, ledger, capabilities, approvals and inference admission in the sealed governance set.
Validate the product declaration and select its domain services and interface vocabulary.
Apply organization restrictions while assembling the work context. Compile typed steps, perform the selected method and retain its transitions.
One foundation. Products with a life of their own.
Discuss a product foundationA new AI application needs its own workflows, language and interface. Rebuilding the shared controls for every product can leave each application with a different approach to permissions, evidence and recovery.
Use Agency Engine when you need a distinct product or an organization-specific installation on a shared application foundation. Begin with the product’s work objects and operating responsibilities, then compose its services around the protected controls.
SuperSell, built on the engine, organizes commercial conversations; a vertical installation for a law firm or a logistics operator would look nothing like it. Their users encounter distinct products on one governed core.
Shared contracts and controls establish the common operating basis.
Durable work objects, process transitions and execution ports carry the selected product into operation. Replaying recorded transitions reconstructs state without a new reasoning call.
Selected services, interface composition and domain methods give an application its own behavior and vocabulary.
People, client relationships, mandates and operational records belong to the organization using the product.
A resolved product declaration travels from tooling through the backend to the frontend.
The application consumes that composition at runtime. Invalid configuration has a refused state rather than silently exposing the whole engine. Replaceable services use contracts around a protected set of policy, evidence, approvals, model access, disclosure and custody controls.
The decision model can apply default denial, overriding prohibitions, principal-bound approval and recipient constraints. Coverage is defined for specific startup and execution paths; an application still needs its own threat model.
The product lead decides each release; the shared core supplies approvals, records and permissions. Illustrative.
What the research says
Business units control 81% of SaaS spend, and the share of EU enterprises using AI rose from 13.5% to 20% in one year. New AI apps will keep arriving from the business side, each needing approvals, records and permissions. Agency Engine supplies those once, so a product lead spends the launch on the product itself.12
Illustrative situations, connected to the mechanisms that make them possible.
Product organizations
A new application needs its own workflow, language and interface.
Enterprises
A common application must reflect local permissions and operating context.
Software teams
A product discovers a mechanism that another product could use.
The selected orchestration design connects adaptive planning to a typed plan, durable execution and a workspace where people can inspect progress.
Translate proposed work into typed steps and declared execution ports.
A durable process record supports replay of recorded transitions and recovery.
Promotion, retention and forgetting have explicit rules. Recurrence can suggest a useful lesson; evaluation determines whether that lesson improves future work.
The studio makes a created agent an inspectable product object, with a template, bounded settings and a recorded history.
Strict templates and independent cases define the behavior expected from the configured agent. Injection canaries examine selected failure conditions.
Replacing an agent retains the previous version. Restoring an earlier configuration creates a new version, preserving the intervening record.
Creating and testing an agent does not itself deploy it remotely. The target environment and its authority require their own release decision.
Product composition selects the services and interface that serve its domain. Shared governance and compatibility contracts define how that specialization can operate.
The architecture separates reusable product identity from each organization’s people and records. Deployment, data isolation and available workflows are scoped for the intended release.
The technical choices that give Agency Engine its particular behavior.
Agency Engine separates a shared kernel, service and interface composition, product identity and organization context. Distinct applications can specialize their experience around common controls and versioned contracts.
The kernel. Shared contracts and controls establish the common operating basis.
The product. Selected services, interface composition and domain methods give an application its own behavior and vocabulary.
The organization. People, client relationships, mandates and operational records belong to the organization using the product.
An illustrative custom-development journey from a recurring operational problem to handover.
Follow the storyWhich app would your product lead launch next if approvals, records and permissions were already done?
Discuss a product foundation