Unified data infrastructure
GitHub Let's talk

Government

Legacy systems and public records behind one access path.

Public data carries obligations: who may see it, where it may be held, and how a decision can be explained years later.

See Data Infrastructure All of Public & Sovereign

A decision that can be explained years later, from the record that produced it.

The story

A decision that can be explained years later, from the record that produced it.

Where it starts

Registers and case records

Citizens, entities, cases, permits and statuses. It is the first of 4 workloads running in Government.

The question it raises

Explainable decisions

A decision resolves to the record, the submission and the events that produced it.

Why one question is hard

From Register to Account

Government data moves through 4 stages — Register → Deliver → Document → Account. The shapes in play are SQL, JSON / documents, Objects, Events, and answering one question means reading across all of them.

What PLOMID contributes

Public data is held under rules. These are the parts of the layer that speak to them.

  • Control over operation Who runs the system, and where it runs, is part of the first conversation rather than a tier on a pricing page.
  • Deployment is a decision Self-hosted, edge and managed topologies are design destinations of the deployment fabric, and the fabric is specified as its own part of the platform.
  • Documents beside rows Fields that keep changing shape stay queryable instead of being exported into a separate document store.
The environment

Registers, case files, service events and reporting obligations.

Registers and case records are structured, correspondence and submissions are documents, and service delivery produces events. PLOMID holds the record and the events in one layer, so an accountability question reads from the same source the service used.

Deployment & residency

Where this data is allowed to run.

Residency and operational control are requirements rather than preferences, so placement is designed around them.

Deployment, residency and control
The data journey

How government data reaches one layer.

Walk the path the data takes, from the environment that produces it to the questions it answers. Select a station, or a shape, to read each step.

A decision that can be explained years later, from the record that produced it.

Environment

The register

Citizens, entities, cases and permits as records with status.

SQL

One environment · many workloads

What runs against government data.

4 workload families over one set of shapes. Choose one to see what it moves and where it lands.

Citizens, entities, cases, permits and statuses.

  • Planned once against the layer, not once per store
  • Read beside the records it shares a key with
  • Persisted under one storage contract
Where the data goes to work

Questions asked inside the boundary.

Each one is answered where the environment allows, from the same layer rather than a copy that drifted.

Explainable decisions

A decision resolves to the record, the submission and the events that produced it.

  • SQL

Accountability without a project

Reporting reads the same records the service writes, rather than a compiled extract.

  • Events
  • SQL

Documents that stay findable

Submissions and correspondence keep queryable metadata attached to the case.

  • JSON / documents
  • Objects

Control over placement

Where public data may be held is a governance question the system has to answer, so placement is treated as a property of the deployment.

  • SQL
Data models in play

The shapes, in one layer.

4 shapes carry this domain. Choose a stage to read the operation, or a shape to see every stage that handles it.

PLOMID · Government register · deliver · document · account Select a stage
Stage

Register

Entities, cases and status records

SQL

Workload map Government workload map. Every shape on it is a surface of the layer, and each stage names the part of the operation it carries.
  • SQL Records, keys and joins
  • JSON / documents Documents and nested objects
  • Objects Large assets with queryable metadata
  • Events Operational events as they happen
Workload architecture

The boundary, then the path.

The environments set what the architecture may do — then the work, the shapes and the path a request takes.

Government · workload architecture
Workloads

What runs against this data.

  • Registers and case records
  • Service events
  • Documents and submissions
  • Reporting obligations
Data models

The shapes those workloads read and write.

  • SQL
  • JSON / documents
  • Objects
  • Events
The layer

One path from a request to the data it names.

  • Planning Predicates narrow the work before it runs
  • Execution Records, fields and windows answered together
  • Transactions Readers and writers do not block each other
Surfaces

How the work reaches the layer.

  • SQL surface The query language the layer is documented in
  • Applications Services and jobs writing and reading as they run
  • Analytics & AI clients The same layer, the same access path
What you build next

Data Infrastructure

One layer for records, documents and time-ordered data, instead of one system per shape.

If Explainable decisions is your question, start here.

See Data Infrastructure Every solution
Next

Where to go next

Solutions The workload answers this industry leans on, with their models and status. Platform The data models in the product today, and the ones extending the layer. Architecture How a request is planned, executed and persisted once it reaches the layer.