Human authority

When the decision is sensitive, a responsible person takes over

Useful automation should not ask for approval at every step. It should know which cases need human responsibility: contradictions, sensitive actions, policy exceptions or insufficient evidence.

Current DUBSAR status

Human review exists in the private journey

A Human Gate is present in the private test journey. Extending it to real business-action authorisation through the Gateway remains part of the product roadmap.

Human authority

Human oversight should not become a bottleneck

Approving everything removes the value of automation. Approving nothing turns sensitive judgement into an implicit machine behaviour.

DUBSAR's target model lets predictable low-risk cases follow policy while ambiguous or consequential cases wait for an authorised reviewer.

  • Conflicting sources or policies
  • Externally visible or sensitive actions
  • Insufficient evidence
  • Exceptions to a normally applied rule

Human authority

An approval needs context

A useful approval is more than a yes button. The reviewer needs to know what is being approved, why intervention was requested, which evidence is available and what remains uncertain.

The record should bind the context, observed facts, applicable policy, human decision and resulting action so the choice can be reviewed later.

Human authority

Human in the loop does not mean human alone

Agents and automations may collect, compare, flag and recommend. They should not validate themselves on a critical decision.

The system applies a method and keeps the trace; the responsible person remains the authority when policy requires human judgement.

Frequently asked questions

What to know before going further.

Does the Human Gate stop every automation?

No. It is intended for cases defined as sensitive, ambiguous or insufficiently evidenced. The threshold depends on the organisation's policy.

Can one approval be reused for another action?

The target design binds approval to a specific context and validity period. Non-replayable business-action authorisation still needs to be proven in later product stages.