Agent1000

Use cases

Looking for the everyday desks: leave, the morning brief, a reply, a project status? Those are on the front page.

  • VulnWatch

    Code repositories · Dependency registries

    01

    Know what needs patching before anyone else finds it. The patch waits for an administrator.

    Patch the citizen portal

    Finding is safe. Fixing is not.

    Scanning and reporting run on standing approval, because they change nothing. The patch is a change, so it stops and waits for an administrator. Same agent, two different permissions, which is what makes standing approval safe to give.

  • ContentDesk

    Website CMS

    02

    An emailed statement becomes a staged page. It goes live when the officer says so.

    Publish a media statement

    Nothing is published by a machine

    The page existed, finished, before anyone approved it. That is deliberate: the officer reviews the real thing rather than a description of it, and their approval is the act that puts it online.

Governance

What an official is actually agreeing to

The part that has to survive an audit, not a demo.

  • It signs in as itself

    Its own account, its own permissions, in the systems you already run. You can see what it touched and take the account away in an afternoon.

  • It stops before it binds

    Capturing leave, sending a letter, publishing a page. The agent prepares; a named official decides. That order is not configurable.

  • The record names a person

    Every approval is logged against the official who gave it, not the agent. When someone asks who authorised this, there is an answer.

  • RecordsDesk

    Document management system · Shared mailboxes

    03

    Every letter filed against the right case, and the ambiguous one held back for the clerk.

    File this morning's registry mail

    It says when it does not know

    An agent that guesses on the ambiguous one is worse than no agent, because you can no longer tell which filings to trust. This one files what is certain and hands over what is not, which is the only version a registry can actually use.

  • ReportPack

    Reporting database · Spreadsheet templates

    04

    The same pack from the same sources every month. Assembled, flagged, never submitted.

    Assemble the monthly pack

    The same way, every month

    The value here is not speed. It is that the pack is assembled identically each month from identical sources, so when a number moves, the number moved, and not the method.

  • SiteWatch

    Public websites · Certificate authorities

    05

    A certificate expiring, or a page changed overnight. You hear it at 05:00, not from the public.

    Check the public sites

    You hear it first

    A lapsed certificate or an altered contact number is found either at five in the morning by an agent, or at nine by a member of the public. Both are notifications. Only one of them is a good morning.

Browse every agent: what each one connects to, and who approves what.