Prove it.
Evidence on every answer; a tamper-evident record of every decision and its reason.
A statement of intent. CiviQ is accountable, sovereign, and open — built for correctness and trust, not engagement. Focused on local government first. What follows is what we believe, what we refuse to build, and what is true today.
The moment
It was nine o'clock on a Sunday when I tried to book a bulky-waste collection — an old sofa, a bed and a mattress. It should have taken two minutes. It took closer to thirty: clicking between PDFs and website pages, second-guessing every step, nearly giving up to phone a line that wasn't open.
Every fact I needed was published somewhere on the council's site. What didn't exist was a way to actually get helped — a straight, trustworthy answer, at the moment I needed it.
That gap, between information existing and a resident being helped, is the whole reason CiviQ exists.
The diagnosis
Wire a frontier model to a council website and you inherit everything that model was built for — and none of it fits a public service. The defaults are engagement-optimised, cloud-egressing, black-box, metered per message, and locked in.
A public institution's requirements run the other way. The sector doesn't need a more talkative model. It needs a more accountable system.
What the default optimises for — vs what the sector needs
What we believe
Correct or honestly silent.
Better to refuse than to guess. A wrong answer from a public service costs more than no answer.
The institution sets the policy, not the model.
What CiviQ may answer, refuse, or escalate is your decision — configured, versioned, and editable.
Show your work — glass-box by default.
Every answer carries its sources and checks. Nothing is asserted without evidence.
Data stays home.
Sovereignty is non-negotiable. Resident data does not leave the institution's infrastructure.
Never a dead end.
When CiviQ can't help, it hands over to a named human, with the conversation's context attached.
Memory is organisational, never personal.
It learns what content to improve — never who asked. Privacy by construction, not by promise.
Capability is a system property, not a model property.
Retrieval, grounding, refusal, self-checking and auditing are where capability lives.
Open by default.
Apache-2.0, self-hostable, no lock-in. You can read it, run it, fork it, and leave.
Measure, don't assert.
Refusal correctness, groundedness, and quality are evaluated — claims are backed by a green gate.
Accountability is a feature, not paperwork.
A tamper-evident record built for the Ombudsman, IG, and FOI is part of the product, not an add-on.
The redefinition
"Chatbot" describes the surface and misses the substance. The work isn't the conversation; it's the governed system that decides whether to speak, proves where every answer came from, and records the decision.
The category CiviQ is actually in: an accountable, sovereign citizen-support system for councils and public bodies.
The USP
The model is interchangeable. The value is in the layers around it.
Evidence on every answer; a tamper-evident record of every decision and its reason.
A policy the institution sets and versions, running before the system engages at all.
Every question and refusal becomes a ranked backlog of what to fix, write, and automate next.
The anti-roadmap
Some things we will not ship, not because we can't, but because they're wrong for a public institution.
Benefits, housing, safeguarding — CiviQ informs and hands over. It does not act on a resident's behalf where the stakes are high.
It learns about content, never about people. No profiles, no targeting, no behavioural dossiers.
Success is a resolved question, not time on page.
Data stays on your infrastructure unless you explicitly choose otherwise.
If it can't show its sources, it doesn't say it.
Status
CiviQ is an open-source foundation: 228 automated tests, a green accuracy/refusal eval gate on the representative set, and the core capabilities described above are implemented. The next step is a design-partner council running on real content and real traffic.
A project about accountability has to be accountable about itself.
The bigger picture
As AI moves into the institutions that serve everyone, the question isn't whether they'll use it — it's whether they'll govern it, or be governed by a vendor's defaults. Digital sovereignty means a public body can run capable AI on its own terms: its data, its policy, its infrastructure, its right to leave.
An open, sovereign, accountable layer is how that future stays public.
If you run a council, let's run a pilot.
CiviQ is open and self-hostable today. A design-partner council turns a tested foundation into a proven one and shapes what gets built next.