Engagement Squared Government← All of Engagement SquaredSign in →
A county records archive: rows of bound ledgers under skylights, one lamp lit
Interoperability · public preview

Two agencies hold the same person's record and neither will give up ownership. That is not a technical problem, and an export file does not solve it.

See the shared records a citizen can read →← All of Government
The usual answer is an integration: a nightly file, a mapping spreadsheet, and a second copy of the truth that starts drifting the day it is built. Here the record has ONE owner, and the other agency is granted a scoped, revocable channel into it. Nothing is copied, so nothing can drift; revoke the grant and the access ends that second, with the grant and its revocation both on the permanent record.
What the working system does
  • Ownership stays put. The city keeps its business licence, the state keeps its professional licence; neither has to hand over custody to cooperate.
  • Grants are scoped and dated — this agency, these records, from this date, until revoked — and every grant and revocation is a permanent, auditable fact rather than a firewall rule somebody remembers.
  • No export, no batch, no reconciliation job. The partner reads the live record, so “whose copy is right?” stops being a question anybody has to answer.
  • One identity across sovereigns. A person licensed by the state and permitted by the city is one person here, which is what makes cross-agency enforcement possible at all.
  • Joint purchasing falls out of the same shape — agencies buying the same commodity can see each other doing it.
Go and read the real thing — no account

These are working records, rendered live.

Nothing here is a screenshot or a mock-up.

The Town Square

City and state facts about the same identity, shown side by side to the public.

The public business-licence lookup

One search across the sovereigns that licensed the same person.

A real small district's page

Who does what in one actual California community, on one page.

Municipal Service Intelligence

The orchestration layer that uses exactly this kind of channel to route a resident's report to the right department, across systems that were never built to talk to each other.

The console itself is behind a sign-in — and here is why, plainly

Granting and revoking a channel changes who can read another organisation's records, so the console for it is staff-only by design. The public side — what the shared records look like to a citizen — is open and linked above.
Sign in for the working record →✉ Ask for a walk-through
● Where this is early — said out loud
Interoperability is the youngest part of the suite. Channels between organisations inside this instance work today; federated channels between separately hosted instances are designed and not built. No standards-body certification is claimed, and none should be inferred.
Counts and pages on this site are generated from the working records at the moment you load them — this one at 2026-09-14 03:16 UTC.
How we sell it
How we sell it. Engagement Squared is offered to government as a commercial item — commercial computer software under FAR Part 12, on our standard commercial license terms. We do not sell it as custom development, and we do not grant Government Purpose or Unlimited Rights in the software, its schema or its technical data. Development was funded at private expense.
And, second: where AI fits
Everything above is ordinary, traditional software doing ordinary government work: registers, permits, standings, dates, queues, public lookups. None of it needs AI, and none of it stops working when the AI is switched off. Where AI is offered it is optional, it is bring-your-own-key, and it never writes to a record without a person approving the change. For the record: no AI invented this data model — Alex Glaros did, at a drafting table, over years.