2.12 Frontier

Duress-resistant delegation

Testing that a user's grant of authority to an agent is freely given, not coerced: porting the anti-duress safeguards of fiduciary regimes (independent confirmation, a cooling-off window, a pre-named trusted contact, a duress-revocation path) into the digital delegation flow, proportionate to the stakes of the delegated action.

01

The impact of agents

As users delegate more, and more consequential, authority to agents, a delegation that is authentic at the session level but obtained under coercion becomes a growing harm. Elder financial abuse and intimate-partner coercive control both work by making an authentic account-holder act against their own interest, and the standard safeguard (client-initiated nomination through the user's own authenticated session) is defeated exactly here, because the session itself is coerced. For policymakers the difficulty is that the agency cannot tell a free grant from a coerced one at the point it is made, and the authority, once granted, keeps acting out of the agency's sight.

02

What must be verified

For a high-consequence delegation, an agency needs confidence that the grant of authority to an agent is freely given, not obtained by coercion, to a degree proportionate to the stakes. Client-initiation from the user's own authenticated session establishes that a real person authorized the agent, but not that they did so freely. The confidence government needs sits above the declarative level, met structurally rather than by self-report alone, and the agency, or the caseworker or intermediary it designates, must hold that structural confirmation.

03

Protecting access

The cohorts a duress safeguard protects are the same cohorts a clumsy one excludes, so the check must not become the barrier. A person under guardianship or with fluctuating capacity needs the delegation to be makeable by their guardian, in a form the agency recognizes, since they may not be able to pass a free-will test alone. Requiring an independent witness excludes an isolated person who has no one to serve as one. Inserting confirmation ceremony at a moment of crisis deters the person who most needs the help, leaving them denied or redirected to no service at all.

Keep the path open by making the safeguard proportionate to stakes: no ceremony for low-consequence grants. Offer assisted confirmation through a trusted intermediary or a caseworker rather than a private witness the user may not have, and run the duress-revocation path as a service the user can reach without the abuser present.

04

Response surface

Duress Safeguard

The stakes of the delegated action set the ceremony: none for a low-consequence grant, and an independent confirmation, a cooling-off window, and a notified trusted contact for a high-consequence one. A duress-revocation path is available to the user without the other party present.

User granting under pressure
Preview the grant at a different stakes level
Granted · takes effect now

No extra steps are needed for this permission.

System offers exit
Revoke an agent’s authority now

For a delegation you were pressured into. This route doesn’t notify the agent’s holder and doesn’t need the other person’s cooperation.

Agent: FamilyFinance, held by R. OseiDEL-2026-3390
Authority over: superannuation · payments

Revoking here also opens a private conversation with a caseworker, by a channel you choose.

You don’t have to prove you were pressured into this. Your statement here is enough to revoke it.
05

Maturity

  1. Emerging

    For reactive financial controls, where a firm can place a temporary hold on a suspected-exploitation transaction and notify a pre-named contact, running in production under securities rules.

  2. Frontier Headline

    For the delegation flow itself, where no digital identity or authorization system tests whether the grant of authority to an agent is freely given.

06

Precedents

Fiduciary regimes test free will at the point of grant. Enduring powers of attorney require independent witnesses (under Australian regimes, two, none related to the principal or the attorney and none a paid carer) who certify the principal is "acting freely and voluntarily," with the good-practice step of speaking to the principal without the appointee present (ALRC Report 131; QLD OPG witnessing guidelines). The mechanism that transfers is independent confirmation by someone who is not the beneficiary, conducted where the person granting authority can speak unobserved.

Securities rules pause the transaction, not the authorization, on a reasonable-belief trigger. FINRA Rule 2165 lets a firm that reasonably believes financial exploitation "has occurred, is occurring, has been attempted, or will be attempted" place a temporary hold on a disbursement (15 business days, extendable to 25 then 55) and notify all authorized parties and a pre-named trusted contact, excluding any party suspected of the exploitation. Exploitation expressly covers control "through deception, intimidation, or undue influence." The transferable primitives are the reasonable-belief hold and the pre-named trusted contact collected at enrollment (FINRA 2165; CFPB trusted-contacts guidance).

The safe-exit primitive is already named in abuse-design guidance. Australia's eSafety Commissioner calls, in its work on technology-facilitated abuse, for emergency lockouts and safe transfers: a documented way to revoke all access and transfer ownership during separation without contact with the other party. That is a direct design requirement for a duress-revocation path.

Digital delegation systems currently omit all of this. The Australian Digital ID accreditation rules enumerate fraud, protective security, privacy, and accessibility as required control domains; a free-and-voluntary test of the person being represented is not among them, and the delegation systems reviewed elsewhere publish only credential-hygiene guidance. The gap between the paper regimes above and the digital flow is the design space this pattern occupies.

07

What carries over to agent use

The analog anti-coercion mechanisms transfer as four proportionate steps, keyed to the consequence of the delegated action rather than applied uniformly.

  1. Independent confirmation — for a high-consequence grant, a step conducted with the user alone, by a caseworker or recognized intermediary rather than a private witness the isolated user may not have.
  2. A cooling-off window — the authority does not take full effect immediately, and a notified trusted contact can object within it, mirroring the objection period fiduciary regimes impose before registration.
  3. A pre-named trusted contact — collected at enrollment, contacted when a delegated action trips a reasonable-belief threshold, excluding any party suspected of the coercion.
  4. A duress-revocation path — a route to revoke all of an agent's authority that the user can reach without the other party present.

Critical gap: every mechanism above is analog or reactive, and none has been built into a digital delegation flow. The unresolved design problems are the reasonable-belief trigger for an automated grant, the false-positive cost of adding friction to a delegation that is in fact free, and doing all of this without excluding the very cohorts the safeguard exists to protect: those who are isolated, under guardianship, or in crisis. This is why the delegation-flow application is frontier while the reactive financial controls it borrows from are not.

08

Where things go wrong

The failure mode is a delegation that is authentic at every technical layer and still not freely given. An elder pressured by a trusted relative, or a person under coercive control, is made to nominate an agent from their own verified session. The authority it carries is then used to drain a benefit, a superannuation balance, or a payment. The harm lands on the person least able to absorb it and least able to escape the one who arranged it. Client-initiation cannot see this, because the coercion sits behind the session. What catches it is a confirmation step run with the user alone, a cooling-off window in which a notified trusted contact can object, and a revocation path the user can reach without contact with the other party.

09

Sources

6 references AU · US