Public sector
Government work, with officers keeping the decisions.
Fifteen departments mapped — from revenue administration to disaster response — on a platform that runs inside the government boundary and leaves every action defensible after the fact.
Three commitments
What we hold to in every public deployment.
Sovereign by architecture
The engine runs inside the department's own infrastructure. Only two outbound flows exist, and both can be removed. Local-first operation continues when connectivity does not.
Officers keep the decisions
Every action class carries a gate — Auto, Approve or Advise — enforced in policy on the decision path. No agent decides a citizen's entitlement, eligibility or penalty.
Defensible after the fact
Each action is signed by the engine that performed it, and any record can be reconstructed as it stood on a past date — so a review question becomes a query rather than an investigation.
The constraints we design for
Six realities of government, six architectural answers.
| Constraint | Why it binds | How the platform answers |
|---|---|---|
| Data cannot leave the government boundary | Residency rules, classification, sovereign-cloud mandates | The engine runs inside the boundary. Two outbound flows only, both removable; zero-egress mode available. |
| Every action must survive audit | Supreme audit institutions, courts, legislatures | A signed record for every action — signed by the engine that acted; the control plane records but never re-signs. |
| Decisions affecting citizens stay with officers | Entitlements, eligibility, penalties | Authority bounded per action class: Auto, Approve or Advise, enforced on the decision path. |
| Core systems have no modern interface | Legacy hosts, scanned archives, green screens | Hundreds of connectors, including a green-screen connector for terminal-based hosts. |
| Connectivity is intermittent | Remote districts, field offices, disaster zones | Runs on local infrastructure and keeps working when the link does not. |
| Citizens are not all literate or online | Many languages, telephone-first access | Voice is a first-class channel; language coverage is evaluated per deployment before it is committed. |
Authority
Three gates, enforced on the decision path.
Completes within policy
Confined to alerts, reminders, routing and low-risk requests.
Prepares, a person commits
The agent prepares the work; a named officer reviews and commits it.
Analysis and evidence only
No action is taken on the agent's initiative.
Coverage
Fifteen departments, a hundred and thirty-seven outcomes mapped.
Each count below is the number of concrete, named outcomes we have mapped for that department — live patterns, component assemblies, designed builds and companion agents.
Revenue, tax and customs administration
Very large volumes of unstructured filings, legacy processing systems, and an absolute requirement that every decision be defensible on review.
Public finance, procurement and audit
Money that leaves quietly — overcharged invoices, duplicate payments, unexplained variances — in volumes too large for sample-based review.
Personnel and civil-service administration
Decades of service records in paper and scanned form, complex transfer and promotion rules, and obligations that invite litigation when applied inconsistently.
Welfare, tribal and community programmes
Schemes delivered across remote areas with limited connectivity, many languages and uneven digital literacy, where leakage and exclusion are both costly.
Agriculture and farmers' welfare
Settlement delays, episodic beneficiary verification and legacy land and treasury systems that national registries still have to reconcile against.
Land, records and property administration
The same land recorded differently by different departments, generating disputes that surface years later and are expensive to resolve.
Transport
Mature registration, licensing and enforcement systems that operate in isolation, so revenue, enforcement and safety decisions lag behind the data the department already holds.
Certificate and document trust
Licences, certificates and permits presented to people who must decide whether to trust them.
Telecommunications regulation
Spectrum, licensing and security obligations spread across many operators, with compliance still assessed largely through periodic review.
Disaster management and emergency response
Hazards that develop quickly across difficult terrain, with warning depending on sensor data that is rarely brought together in one place.
Forest, wildlife and environment
Large, remote areas monitored by thin field staff, where detection has to be immediate and evidence has to stand up in prosecution or regulatory review.
Public health administration
Delivery spread across many facilities, with stock, staffing and service data arriving late and rarely in one view.
Education administration
Attendance, performance and scheme data held at school level and consolidated too late to support intervention.
Government IT, cyber and service operations
State data centres and departmental IT teams carrying service demand and security obligations with limited specialist capacity.
Secretariat and cross-cutting administration
Common administrative work — files, correspondence, information requests and audit — that consumes capacity in every department alike.
Where to begin
Nine entry points with measurable first value.
| Department | Entry point | Why it works first |
|---|---|---|
| Public finance and procurement | Invoice audit against contracted rates; duplicate payment prevention | Live patterns, measurable in recovered value, and no effect on any citizen. |
| Government IT and service operations | Government IT service-desk triage | A live pattern, internal to government, measured in the desk's own reporting. |
| Forest and environment | Wildfire detection with a ground coordinate | A live detection pipeline, with its operating disclosures stated in advance. |
| Revenue and tax | Indirect-tax return reconciliation | Converts a full-team exercise into an exception list the department can count. |
| Personnel administration | Service-record digitisation and query | Value from existing records, advisory only, with no decision authority. |
| Welfare programmes | Benefit transfer reconciliation | Leakage and exclusion both become visible, with every case approved by an officer. |
| Transport | Vehicle tax and fee leakage | Recovered revenue is measurable in the department's own collections, and every notice is approved by an officer. |
| Telecommunications regulation | Spectrum usage charge reconciliation | A reconciliation the regulator already performs, converted into an exception list with the evidence attached. |
| Agriculture and farmers' welfare | Crop insurance claim adjudication | Measured on a figure the department is already asked to defend — time from loss event to settlement — with contested cases always decided by an officer. |
Deployment
Seven modes, from a district office to an air gap.
Single host
A district office, a field station or a first departmental deployment.
Multi-node
Departmental and state data centres at production volume.
Private or sovereign cloud
Departments operating under a government cloud mandate.
Hybrid
Central processing with sensitive stages retained on premises.
Desktop
Individual analyst and investigator workstations.
Embedded
Inside an existing departmental application.
Air-gapped
Classified and fully isolated environments — proven in continuous integration; field proof is pending, and we say so.
What we decline
Two things we will not build.
Final decisions on citizens
No agent grants, denies or alters an entitlement, eligibility determination or penalty. Agents prepare and evidence; officers decide.
Closed-loop control of safety-critical systems
Alerting on hazards is offered; autonomous control of dams, grids, water treatment or similar infrastructure is not.
And the disclosures we make before you ask
- Detection
- Daytime detection performance is the only performance quoted. Night-time false positives are an open finding, with remediation in progress.
- Prediction
- Initial deployments provide anomaly and rule-based detection. Statistical prediction is introduced only once a department's own history supports it.
- Isolation
- Air-gapped operation is proven in continuous integration, not yet in the field, and uses smaller self-hosted models.
- Languages
- Voice is shipped. Coverage of specific languages and dialects is evaluated for each deployment before it is committed.
- Legacy screens
- Screen automation is brittle by nature. It provides reach where no interface exists; it is a bridge, not a permanent architecture.
- References
- No existing client or deployment site is named without that client's written consent.
How an engagement starts
Four gates before any build.
A named process
One process, not a programme. Broad mandates are narrowed before any scoping begins.
A named owner
An officer who runs the process and will judge whether the outcome was achieved.
A measured baseline
A figure the department already reports — backlog, cycle time, error rate or recovery.
A decided approval gate
Which actions are Auto, which require approval and which are advisory — agreed before the build.
Completion is not a demonstration. It is a captured, re-runnable record of what the system did, on your data, that your own audit function can replay.
Bring us one process
One named process, one named owner, one measured baseline. If it passes the four gates, we will show you what the first ninety days look like.
Keep reading