Architecture & trust · conceptual production model

Designed to connect. Designed to be governed.

The expensive part of a national platform is not the dashboard. It is the operating model underneath it: who can see what, where evidence comes from, how systems connect, how AI is constrained and how the service remains accountable.

Core layers6User to trust architecture
Prototype programmes31One shared operating model
Public boundarySeparatePublishable information only
AI decision rightsHumanNo autonomous high-impact action
Interactive system model

Understand each layer, then the whole system.

Select a layer to see what belongs there and what must be true before a production pilot can rely on it.

What users see

Experience layer

A connected set of operating experiences, all using the same programme, province, sector, decision and evidence records rather than separate dashboard data.

Connected
Command CentreNational pulse, exceptions, decisions and upcoming gates.
LeadershipMorning briefing, movement, ranked decisions and 30-day outlook.
Delivery & RegionsPortfolio filters, programme detail and place-based comparison.
Knowledge & PublicStructured understanding plus a separate publication boundary.
The same programme record should be recognisable from national summary through executive briefing, province, sector, assistant answer and public-safe publication.
Access model

Roles do not receive the same operating picture.

This matrix is conceptual, but it demonstrates the design principle: access follows role, responsibility and information classification.

RoleOperational programmeInternal risksEvidencePublic publication
ExecutiveYesYesSummaryNo
Programme leadAssignedAssignedAssignedNo
Regional leadRegionalRegionalRegionalNo
AnalystAuthorisedAuthorisedAuthorisedNo
AdministratorConfigLimitedAuditNo
Public viewerNoNoNoPublished only
Governance outcomes

Trust must remain visible in the product.

Users should understand freshness, source, classification and decision ownership at the point they act, rather than opening a separate governance manual.

IdentityKnow who is acting.

Verified identity, MFA, role lifecycle and privileged administration.

EvidenceKnow what supports the status.

Visible provenance, freshness, confidence and source ownership.

AIKnow what the assistant used.

Source-aware retrieval, inherited permissions and human accountability.

AuditKnow what changed.

Traceable record updates, access events and controlled administration.

ResilienceKnow how service recovers.

Backups, incident management, monitored integrations and recovery plans.

PublicationKnow what is safe to publish.

A deliberate public-safe layer instead of exposing internal operating context.

Architecture shown here is a product and governance model, not a claim that live government infrastructure, identity services or restricted datasets are connected. Production design would be validated with authorised security, data and service owners.
See the 90-day pilot Explore governance knowledge