Prototype

A proposed Know-Your-Agent assurance framework, shown on synthetic data. No supervisor requires this today; no real firm, bank or account appears anywhere.

The bank checks every instruction

Agent 247 signs each payment instruction and presents its passport. Northgate's bank (demo) runs nine checks in order and answers ALLOW, ESCALATE or DENY with the rule, a reason and an authority-signed receipt. A redirected invoice, an oversized payment, a structured run of payments, a copied passport or a revoked assurance all stop here.

Passport
Assurance
Mandate
Payments executed0
Vouch rail
30-day totals per supplier account

What the bank sees on the passport

Permission and keys, not personal data. Three signatures, checked against three published keys. Status is read from the authority's registry at the moment of the instruction.

Passport
none issued yet

Proposed instructions

Run them in order for the demo. Repeated ones keep going until the bank refuses.

    Lifecycle beat: in Review & issue, suspend the passport and rerun instruction 8 (DENY R.2), reinstate (ALLOW), revoke (DENY R.2, and the vouch rail refuses too).

    gateway · POST /api/verifyrefusals · payments-2026.09
    1. Waiting for an instruction.
    Ordered rule evaluation (deny by default)