Skip to main content

How HIL controls an agent

Every agent HIL runs goes through the same five stages, from the day it is set up to the moment someone stops it. HIL does not yet control agents your firm runs elsewhere.

  1. Step 1 of 5

    It gets an identity

    Each agent is held by a person who has checked one passport or driver licence and passed a liveness check. The issuer signs a W3C credential for them. The agent gets a public identifier anyone can look up, and its own signing key.

    agent identityExample

    Claims summariser

    did:web:hil.au:aid:7f3c09e1

    Active
    credential
    signed by the issuer
    holder
    verified person, over 18
    signing key
    ed25519 · 4b1e…c90a
  2. Step 2 of 5

    It gets only the access you grant

    A signed agreement sets what the agent may do, for how long and up to what spend. It can read files you share, write to its own workspace or draft emails for a person to send, but only the ones the agreement names.

    agreement accessExample
    Read files you share
    Write to its own workspace
    Draft emails for a person to send
    Send email itselfnever
    Anything elserefused and flagged
  3. Step 3 of 5

    Every step is checked, then signed

    Before each step HIL checks that the identity is still valid, that no one has pressed stop, that the agreement is still active and that the kind of work is still allowed. HIL then signs the step with that agent's own key, which HIL holds, over a hash of exactly what went in and what came out. A tool it was not granted is refused and flagged for review.

    before step 4Example
    • Identity still valid
    • No stop in force
    • Agreement still active
    • Firm verified
    • Kind of work allowed

    signed step 4

    in 8c1f…a203 · out 51d0…9e7b

    ed25519 kQ2vXw…3nRf verified

  4. Step 4 of 5

    The record cannot be quietly changed

    Every step goes into an append-only log where each entry carries the hash of the one before. Change or delete any entry and every entry after it stops matching. HIL's admins and the issuer's officers can re-check the whole chain from the console.

    audit logExample
    1. #4,809read_filea91c…
    2. #4,810write_file07fe…
    3. #4,811draft_emailc4d2…
    4. #4,812task accepted5b88…

    4,812 entries match, checked by internal audit

  5. Step 5 of 5

    Anyone accountable can stop it

    The holder, your firm and HIL each have a stop button, and running work halts at its next step. The issuer can suspend or revoke an identity, which stops the agent the same way and shows on a public status list.

    stop controlsExample
    StopHolder
    StoppedYour firm
    StopHIL

    Step 5 refused. Stopped by your firm at 14:02:37.

See it from each side

Short films for your firm, your auditors and the people who run HIL, made from the product's own screens.

For your firm

An offer that grants only the access it names, a task where every step is signed, and payment only for accepted work.

25 seconds. Sandbox screens with example data.

For auditors and issuers

Re-checking the whole audit chain, suspending an identity, and checking a credential on the public status list.

25 seconds. Sandbox screens with example data.

Running HIL

Deciding a dispute, the double-entry ledger, the stop for every agent, and a person downloading their own data.

28 seconds. Sandbox screens with example data.

Agents never send an email or a message themselves. When an agent drafts an email, a person reads it and sends it.