For regional and national bodies
The evidence exists at neighbourhood level. Your statistics stop at the province.
A programme designed at regional scale is allocated at municipal scale and experienced at street scale. The statistical apparatus reports at the first of those three, annually, and everything below it is inference.
How this works today
We deliver regional work as a hands-on engagement, and the productised version is being built alongside live municipal pilots. Early partners shape what ships next and keep the methodology either way.
The moment
Two situations bring a regional body to a platform like this.
- 01
A national or regional programme requires evidence at sub-regional resolution that the existing statistical apparatus cannot produce.
- 02
A policy is being designed and nobody can model its effect before implementation.
The capability at regional scale
What the platform does that a statistical series does not.
Not faster statistics. A different unit of analysis, carrying its own provenance, that can be aggregated to the geography a programme reports on without losing the level a programme is delivered at.
Independent review
We send the method out for review before we run it on anyone.
A public body adopting a method has to defend it in front of people who did not build it. So the method is a document before it is software, reviewed before it runs and re-reviewed on a cycle, and you receive the document rather than a summary of it.
Reviewed before it runs
The method goes out for review before it touches anyone’s data.
Index design, baseline construction, and simulation parameters are written as documents and reviewed by a research group that works on that subject. The method is separable from the software on purpose, so it can be evaluated by people who did not build either. An output produced by a method that has not been through this says so on its face.Re-reviewed on a cycle
Annually, and whenever the method changes materially.
Not per client and not per delivery. An engagement runs a version of a method that was already reviewed, and anything an engagement adds goes into the next cycle rather than holding up the work. The version that produced a given output is recorded on it.What we learn goes back
Findings, method changes, and failures return to the research group.
A review is worth something to a research group only if the deployment feeds it. Anonymised findings and the record of what did not work go back, for further research and for the policy questions that research exists to answer. This is the half of the arrangement that makes it a collaboration rather than a favour.
Built for the DPO
Compliance is the doorway, not the disclaimer.
A regional deployment concentrates more data in one place than a municipal one, so the questions get harder rather than easier. These are the same six answers, and the documentation pack goes to your Data Protection Officer before anything is agreed.
Anonymisation at ingestion
No individual-level data reaches the AI layer.
No individual-level data enters the AI processing layer. Analysis runs on aggregated and pseudonymised data, and the rule is enforced at the pipeline boundary rather than by convention.EU data residency
EU infrastructure, Catalan residency for Catalan deployments.
Infrastructure in EU jurisdiction, with Catalan data residency for Catalan deployments. The sub-processor list is published and versioned.Per-module EU AI Act classification
Classified per module, before deployment, because they differ.
The classification is documented per module before deployment, because the modules are not equivalent. Employment-related matching is treated under the high-risk obligations. The civic analysis modules are advisory decision-support for institutions.A human decides
The platform ranks and explains. A person decides.
The platform ranks, explains, and projects. A qualified human makes every hiring and every policy decision, and the decision is logged against their identity.DPA before ingestion
Signed, and your DPO briefed, before a record moves.
A signed Data Processing Agreement and a briefed Data Protection Officer before a single record moves. The system refuses to create a data source without a recorded DPA reference.Exportable audit trail
Every output keeps what produced it, and exports.
Every match, alert, and projection persists its inputs, model version, driving features, and confidence value. Exportable for labour inspection and public audit.
Start with the method.
Ask for the methodology documentation and the compliance pack, and evaluate them before any commercial conversation. Regional work is procurement-led, so pricing is set against a tender rather than published here.