Governance and trust

Public-sector AI needs clear rules.

GOV.AI is designed for environments where an incorrect answer, an outdated source or unauthorised access are not minor details. Governance is part of the product.

01

Sources before answers.

Municipal factual information should be supported by defined, traceable sources.

Approved sources

Domains, databases and documents are defined for each use case.

Citations

The interface can show the source used and distinguish the source from its interpretation.

When there is no confirmation

When the evidence is insufficient, the response should acknowledge the limitation and direct users to the official channel.

02

Permissions by context.

Not all internal information is meant for every user.

Residents

Public information and unauthenticated guidance only.

Staff

Authorised internal knowledge, according to role and need.

Sensitive actions

Operations, decisions and personal data require dedicated workflows, appropriate authentication and review.

03

Human review and continuous improvement.

Governance does not end at launch. Questions, failures and changes to sources should inform ongoing maintenance.

01

Monitor

Which questions are being asked and where the AI falls short.

02

Review

Sources, responses and sensitive cases.

03

Correct

Content, rules and integrations.

04

Document

Product changes and decisions.

Need to discuss risks before the demo?

We can start with the architecture for sources, permissions, review and the use case’s limitations.

Discuss governance ↗