Civic design intelligence system
MVP Limited to few service areas as a current worked example. The model is intended to be reusable across public services.

Build a shared understanding of public-service needs

Open knowledge infrastructure for public-service needs, evidence, pain, capabilities, outcomes and decisions.

View the repository Read the strategic vision
Illustration showing a central civic knowledge map connected to evidence, lived experience, public contributions and decisions.

What this system is for

The repository turns fragmented research, lived experience, public reports and operational knowledge into traceable civic knowledge objects that can support better service, policy, operational, outcome and AI-assisted decisions.

Preserve what is known

Capture evidence, user needs, civic needs, capabilities, behaviours, pain points, insights and value dimensions as persistent, linkable knowledge objects.

Make decisions traceable

Help design histories, policy records and operational decisions reference stable knowledge objects instead of rewriting them.

Expose gaps and risk

Show where evidence is missing, where pain blocks value, and where public-service outcomes are unsupported or based on weak problem framing.

Why it matters

Public services need better outcomes, not just better documentation. Civic design intelligence helps teams connect evidence, lived experience, capabilities and operational knowledge to the outcomes they are trying to improve, and to see when learning about needs should change the problem framing or outcome strategy.

  • See where needs are unsupported.
  • Find where pain blocks public value.
  • Challenge decisions made without enough evidence.
  • Spot when delivery reality challenges the stated outcome.

Repository snapshot

These figures are generated from repository folders and object metadata where available. Missing metadata is counted explicitly rather than inferred as reviewed or validated.

-Loading stats

Object maturity

The page treats missing metadata as an operational signal. It does not promote objects to reviewed or validated status.

How AI can support it

AI makes this approach practical. Public-service knowledge is usually spread across research reports, lived experience, complaints, policy documents and operational data.

AI can help structure, connect and query that material at pace, while the repository keeps the work governed, traceable and reviewable.

This matters for civic AI and simulation because models need structured knowledge about needs, capabilities, constraints and outcomes, not only service data or process metrics.

Responsible by design

  • AI helps with structure and connection.
  • Knowledge objects keep evidence and uncertainty visible.
  • People remain responsible for interpretation, validation and decisions.

How the system works

1. Evidence and contribution layer

Research, public reports, inspections, complaints, operational data, professional knowledge and lived experience.

2. Canonical knowledge layer

Status-labelled user needs, civic needs, behaviours, pain points, insights, outcomes, value dimensions and opportunities.

3. Decision and history layer

Design histories, policy records and service decisions that reference stable knowledge objects.