Mission data routes
Where does an AI mission’s data go?
An agent’s mission may involve reading a client file, sending extracts to a model and preparing an action in a business application. These exchanges may follow different routes and leave different records.
For an integrator, the practical question is which data goes to which recipient, for what purpose and under which authorisation. The useful result is a record of those routes, separating verified information, providers’ stated terms and unresolved questions.
In brief
The question and the useful result.
- Question
- Where does an AI mission’s data go, who can access it and which copies remain after each exchange?
- Useful result
- A route record separating the governance system, model provider, business applications and evidence storage, with the source and limits of each finding.
Mission data routes
Separate four places where data is processed or kept
The location of the governance system does not describe the entire data journey. Examine these four areas separately, even when one provider supplies several of them.
| Area | Data to identify | Question to resolve |
|---|---|---|
| Governance system | The mission’s state, authorisations, decisions and associated references. | What is actually recorded, where is it kept and who can access it? |
| Model provider | Instructions, supplied extracts and the generated response. | Which service handles this call, under which retention and access terms? |
| Business systems | Source documents, information read and the content of a requested change. | Which reads and actions are authorised in each system? |
| Evidence storage | References, decisions, attempts, acknowledgements and available confirmations. | Where can the records be retrieved, for how long and by whom? |
If a model is also used to analyse a governance record, document that call separately from those within the client’s workflow. Its recipient and the data it receives should be identifiable.
Mission data routes
Give each route a verifiable description
For every exchange, record:
- Its source and the specific information that needs to leave it.
- The actual recipient: service, endpoint and region where relevant.
- Its purpose, applicable authorisation and the person who can review that authorisation.
- Possible copies in logs, backups and monitoring tools.
- The information source, the date checked and anything still unknown.
Provider documentation describes a service’s terms. Configuration shows the intended route. Available observations help establish the route actually used. Keep those distinctions instead of treating an intended route as an observed fact.
Approval to use a model provider does not authorise sending any content or changing a business system. The guide to models, data and actions explains these separate decisions.
Mission data routes
Example: preparing and sending a client response
This example is illustrative. It does not describe a qualified DUBSAR connector.
An agent is asked to draft a response using a quotation and a CRM record. The team identifies the extracts the model needs, without assuming an automatic mechanism will remove everything else. It also checks the receiving service’s terms.
The request to prepare a response does not itself authorise sending it. That authorisation concerns a particular version of the message and a specific recipient. If sending is attempted, distinguish the service’s acknowledgement from evidence confirming the outcome. A missing confirmation remains unresolved.
Using the available observations, the route record separates what is established about transmissions to the model and messaging system, the records retained and the information still missing. The model’s generated text alone cannot establish that a business action took effect.
Mission data routes
Assess location and retention separately
A governance system hosted in France does not establish that every part of a mission is processed there. Location alone does not guarantee security or compliance. For personal data, the EDPB’s guidance on international transfers explains that transfer conditions apply alongside the other requirements for processing.
Likewise, a model provider’s retention commitment does not describe copies kept by the workflow or business applications. Decide which records are needed, who can access them and how long they should be retained. The guide to execution evidence helps clarify what each record can establish.
Mission data routes
Resources for checking a provider
If you are assessing Scaleway Generative APIs, consult the service’s data policy and model catalogue. These documents help you check the proposed service’s terms; they do not establish that a DUBSAR integration is available. Sources consulted on 17 October 2026.
Mission data routes
Frequently asked questions
Should the mission record contain every source document?
Not as a default. Identify what is needed to understand the decision and verify the outcome. A reference can be useful if authorised people can still retrieve the correct version of the underlying document.
Does an approved provider cover every use case?
No. Approval should specify the service, data and purpose it covers. A change to the route, content or use case calls for a review of the accepted scope.
Does DUBSAR already detect and redact sensitive data?
No general capability for detection, anonymisation or redaction is claimed here. Data selection and any transformations must be defined, carried out and verified within the workflow concerned.
Mission data routes
Where DUBSAR fits
DUBSAR is developing a governance foundation that connects durable mission state, explicit authorisations, human decisions and available evidence. For integrators, the aim is to retain useful context about the exchanges within scope, including the limits of that coverage.
Selected workflows have been tested; full B2B integration and validation are still underway. Pilots are not currently open.