Product architecture
DUBSAR architecture: connecting work, decisions and tools
Your team already has agents, workflows and business applications. The questions are where to retain the state of an ongoing mission, where to check permission to act and how to record a useful result after an action.
DUBSAR’s intended architecture divides these responsibilities between a work interface, a decision foundation and connections to existing tools. Cockpit, Core and Gateway describe complementary roles.
In brief
The question and the useful result.
- Question
- Where do state, decisions and evidence sit, and how do they connect to existing tools?
- Useful result
- A division of responsibilities across the Cockpit, the Core and tool connections, and the questions to ask for one end-to-end action.
Product architecture
1. The Cockpit: make the situation and decisions readable
The Cockpit is the proposed interface for people following a mission, reviewing an approval request or taking over a case. It is intended to present the requested work, pending actions, recorded decisions and available evidence.
The view should help the team identify the next decision. A displayed authorisation needs to correspond to a retained decision that applies to the action in question. A label in an interface is not enough to establish that the system executing the action actually checked that authorisation.
Product architecture
2. The Core: maintain a durable basis for decisions
In this division of responsibilities, the Core carries decision logic and authorisations. The foundation is intended to retain the information needed to link a request, its scope, any human decision and what happened next.
Mission state describes progress. Authorisation defines permission to act. Evidence records what was observed after an attempt. These pieces of information support one another without becoming interchangeable.
DUBSAR’s principle is to use models for reasoning while software maintains this framework. An agent may prepare an action or help assess a result; the proposal alone does not give it the authority to carry out the action.
Product architecture
3. Tool connections: apply a decision and report a result
The Gateway is the proposed point of passage for AI traffic explicitly connected to it. It represents one part of the architecture. A connection handling a business action also needs to specify where authorisation is checked and what execution evidence returns to the mission state.
For each operation, the integrator should be able to describe:
- which system receives the request and which one performs the action;
- when the applicable authorisation is checked;
- which response only acknowledges receipt and which establishes the intended result;
- what should happen if the outcome remains uncertain.
A workflow built with n8n or Make can illustrate this discussion, without representing a qualified DUBSAR integration. Exchanges with the foundation need to be examined operation by operation.
Product architecture
4. Follow one action from request to outcome
Consider a reference scenario: an agent prepares a customer notification that requires approval before sending. This illustrates the intended responsibilities, rather than an available connector.
| Stage | What needs to remain linked |
|---|---|
| Prepare | The proposed content, recipient and originating mission. |
| Decide | The designated person’s decision and the specific action it authorises. |
| Execute | The sending attempt and the authorisation checked beforehand. |
| Examine the response | What the service actually confirms, with the action’s reference. |
| Continue | The updated mission state, missing evidence and next decision. |
If the service only acknowledges receiving the request, the record needs to preserve that limited meaning. The Cockpit would help the team understand it; the durable foundation would retain that state; the tool connection would supply the evidence needed to update it.
Product architecture
Frequently asked questions
Does the Gateway cover every action an agent takes?
Its role concerns traffic explicitly connected to it. Coverage of business actions depends on the connections and checks actually implemented and qualified.
Would existing workflows need to be replaced?
DUBSAR aims to provide a shared framework for state, authorisations and evidence alongside existing workflows. The relationship with each workflow needs to be defined; this is not a claim of universal compatibility.
Is the whole architecture available today?
The foundation is still in development. Components and selected workflows have been tested, but full B2B integration and validation are still underway. Pilots are not currently open.
Product architecture
Continue reading
Product architecture
Understand where DUBSAR could fit
Visit the project overview to explore its intended role and current stage of development.