Government

What the entity is asking for

A case arrives with its attachments, two years of correspondence and three circulars that changed the rule since the last decision of its kind. An officer has to read all of it before the decision package can be written, every case is different, and the deadline is the same for all of them.

• Assemble a decision package from the case, its correspondence and the policy that applies today.
• Say which circular changed a requirement, when it changed, and what the requirement was before.
• Check a procurement package against the approved policy and list what is missing from it.
• Explain a service interruption on the entity’s own servers, with the evidence behind the explanation.

How the work is done

An agent is a model, a set of approved skills, tools and a policy, applied to a scope.

Agents answer from your own regulations, documents and records, with the source attached.

Agents reach your systems through approved connectors — APIs, databases, applications — each with its own permissions.

Changes wait for human approval before they run.

The case system, the correspondence archive and the public services all run on servers the entity already operates. Those servers are where an agent starts, and the IT questions are the ones it answers first.

Read-only execution policy is the default on every enrolled host; the full policy is an explicit, per-host choice.

Every answer shows the exact commands that ran, their exit codes and output, per host.

A host joins the fleet with one install command and an enrollment token; revoking the host unpairs it.

Sign in with your own identity provider (OIDC with PKCE); no shipped default administrator password.

The whole stack self-hosts with one command; an air-gap bundle ships every image.