Governance rules

Permission to use a model does not authorise a business action

Your team has chosen a model to summarise customer conversations. That choice does not by itself determine which data may be sent to it, which CRM fields an agent may change or what evidence will establish that the task is complete.

Separate these questions when designing the mission. You can then connect them in a record of the work: what was requested, what was permitted and what actually completed.

In brief

The question and the useful result.

Question
What exactly do we authorise when an agent uses a model and changes a business system?
Useful result
A matrix of model, data, action and expected result, applied to a CRM record.

Governance rules

A proposed update involves several decisions

Consider an agent that reads a meeting summary and proposes replacing the primary contact on a customer record. Before any update, the team needs to define the permitted model service, the information it may use and the scope of the CRM change.

If the update requires approval, the human decision concerns the specific record and proposed change. Sending the request and establishing its outcome are two further events to distinguish.

This example is a way to examine a workflow. It does not establish that DUBSAR has an available CRM integration.

Governance rules

A decision framework for the action

QuestionDecision to make explicitInformation to keep
Which model may be used?The service or provider, selected model and task for which it is permitted.The applicable workflow decision and a reference to the service actually called.
What data may be sent?Information needed for the task, permitted sources and the intended recipient.The intended scope and records that allow the data sent to be checked.
What action is authorised?The record involved, editable fields, conditions and any required human approval.The authorisation for this operation and the human decision when required.
What result must be confirmed?The observation needed to establish that the update completed.A documented system response or a verification tied to the relevant operation.

Permission to analyse a meeting summary should therefore not be reused as permission to write to every customer record. Equally, finding that a record has changed does not by itself establish that the change was authorised.

Governance rules

Decide what will update the mission's state

Durable state lets a team recover that a proposal awaits a decision, a request has been sent or a check remains open. It connects those events to their supporting records.

Before taking the action, agree on what will establish completion in the business system. An acknowledgement confirms that a request was received; it may establish nothing beyond that. If the customer record update remains unconfirmed, keep the outcome uncertain and state which check is needed.

Governance rules

Define the role of each tool

Your workflow coordinates steps and calls business systems. Its design should identify where an action is authorised, which component enforces that decision and how the result returns to the mission's state.

DUBSAR is developing a governance foundation intended to connect that state with authorisations, human decisions and evidence. It is designed to work alongside existing tools within an explicitly connected scope. A written rule does not establish that every possible operation follows it; integration checks need to examine where the rule is actually applied.

Governance rules

Frequently asked questions

Can the model decide which actions it is authorised to take?

It can propose an action as part of its assigned reasoning task. Authorisation needs to come from the workflow's defined rules and a human decision where those rules require one. The model's proposal does not expand its permissions.

What should we review when the model or data scope changes?

Revisit the affected rows in the framework and their consequences for the task. Then check whether the proposed action remains within the authorised scope. Changing a model provider grants no additional rights in the business system.

Is this a personal data detection system?

The framework helps a team decide what data to use and share. It assumes no automatic detection or anonymisation capability in DUBSAR. Those capabilities need to be checked in the tools that actually provide them.

Governance rules

Current project status

DUBSAR is in development. Selected workflows have been tested; end-to-end validation for B2B use is still underway. Pilots are not currently open.