Trust
Built for decisions that need to be explained.
Public decisions are questioned later, sometimes years later, sometimes by an auditor and sometimes by a journalist. A platform that supports those decisions has to be designed for the moment it is asked to justify one.
Stated plainly
TwinGov holds no security or compliance certification at the time of writing. Nothing on this site displays a certification badge, government endorsement, award, customer name or usage figure, because none of those has been earned yet. What follows is how the product is built and where its limits currently sit.
01 / Principle
Evidence and sources
Answers are tied to the data they came from.
TwinGov answers from a model built out of the institution's own connected sources, not from general knowledge about cities. That constraint is what makes a citation meaningful: the platform can point at the document, dataset, layer or indicator behind a claim because that is where the claim came from.
- Citations attach to the claims they support
- Measured, derived and assumed values stay labelled apart
- The refresh frequency of each source is visible
- An answer outside the connected model is refused, not improvised
02 / Principle
Data ownership
The institution keeps control of what it supplies.
Data provided by the institution remains under the institution's control, on the terms set in the agreement rather than by the platform. The resulting model can be exported in open formats, so a decision to stop using TwinGov does not strand the work that went into it.
- Institutional data stays under institutional control
- The model exports as JSON against a published schema
- Geographic layers export as standard GeoJSON
- Workspaces are private and are not publicly indexed
The limit
Third-party layers licensed to us, such as commercial traffic feeds, satellite imagery or terrain tiles, cannot be transferred with the model. Layers derived from OpenStreetMap carry the ODbL licence and its attribution requirement.
03 / Principle
Open standards
Portable where the format allows it.
TwinGov sits above the geographic systems an institution already runs rather than replacing them. Existing services are connected as sources, and model layers can be served back out to the tools your teams already use.
- GeoJSON in and out, readable in any GIS
- JSON model against a published schema
- WFS service for model layers where the deployment supports it
- Programmatic access to the same structured model the interface reads
04 / Principle
AI transparency
What the AI does, and what it does not.
A generative model is used to interpret the question and to compose the answer from material retrieved out of the connected model. It is not used to invent values, and it is not the authority on whether a statement is true: the source is. Where the retrieved material does not support an answer, the platform reports that instead of producing a plausible one.
- The AI composes from retrieved material, it does not supply facts
- Every substantive claim resolves to a connected source
- Confidence is reported with the reason behind it
- Where sources conflict, the conflict is surfaced rather than averaged
The limit
Language models can still misread a document or misattribute a figure. This is why the citation is shown next to the claim: so a reader can check it in the time it takes to click, rather than having to trust the summary.
05 / Principle
Human decision making
The platform supports the decision. A person makes it.
TwinGov produces analysis and comparison. It does not approve investments, allocate budget, issue permits or substitute for a statutory process, and it does not rank options as a recommendation the institution is expected to adopt.
- Comparisons report differences, not verdicts
- Professional judgement stays with the professionals
- Analyses record who produced them and on what inputs
- Public accountability for the decision is unchanged
06 / Principle
Security
Principles we work to, stated without borrowed credibility.
Each institution works in a separated workspace, access is governed by roles, and institutional workspaces are private and excluded from indexing. Hosting region can be set to what the customer's rules require.
- Separated workspace per institution
- Role-based access within the workspace
- Private by default, excluded from public indexing
- Hosting region set to the customer's requirement
The limit
TwinGov holds no security or compliance certification at the time of writing, and this page claims none. If your procurement requires formal attestation, tell us early and we will tell you plainly what exists and what does not.
07 / Principle
Data limitations
A gap is a finding, not an embarrassment.
Coverage, refresh frequency and declared gaps are visible in the interface and travel into the exported report. The reason is practical rather than moral: a decision taken on data that turns out to have been incomplete is a decision that gets reopened, and the cheapest moment to discover the gap is before the vote.
- Model coverage shown as a figure, not asserted in prose
- Declared gaps are fields in the model, inherited by every answer
- Gaps appear before conclusions in an exported report
- Where a series is too sparse to rank on, the platform says so
Procurement
The questions a CIO asks first.
Short answers, given before they are asked, so an evaluation team can decide early whether to spend time on this.
- Does this replace our GIS?
- No. Existing geographic services are connected as sources and model layers can be served back out. TwinGov becomes an additional reader of your geography, not a second copy of it to maintain.
- What happens to our data if we stop?
- The model exports as JSON against a published schema and the geographic layers as standard GeoJSON, on the terms set in the agreement. Third-party layers licensed to us cannot travel with it.
- Can we see why it said that?
- Yes. Substantive claims carry the source they came from, and measured values stay distinguishable from derived values and assumptions all the way into the exported document.
- What if the data is bad?
- Then the platform should say so rather than produce a confident answer. Coverage is measured and displayed, and gaps are declared fields in the model rather than notes someone remembered to add.
- Do you hold certifications?
- Not at the time of writing, and nothing on this site claims otherwise. If a formal attestation is a procurement requirement, raise it early so nobody wastes a cycle.
- Where does it run?
- Hosting region is set to what the customer's rules require. Tell us the constraint and we will confirm in writing whether we can meet it before anything is signed.
What could TwinGov reveal about your community?
Start with the data you already have. We can build an initial model from available public and institutional sources and show where TwinGov can create immediate decision value.