> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics/technical-specifications.md).

# Technical Specifications

A GovStack-aligned specification for turning raw government data into governed, reconciled, decision-ready intelligence — covering scope, requirements, data structures, standards, and the API surface,

The Analytics Building Block turns harmonised government data into trustworthy, decision-ready intelligence: a governed data lakehouse, multi-source reconciliation with human oversight, dual-engine querying, and AI-assisted insight generation — all built to interoperate with the rest of the GovStack Building Block ecosystem.

> 🎯 **In one line.** Turn harmonised government data into decisions you can defend — reconciled transparently, governed by humans, delivered through open APIs.

This specification (v0.2) sets out what a conformant Analytics Building Block must do, across thirteen sections. Each has its own page, so you can jump straight to what you need. Throughout, <mark style="color:$danger;">**REQUIRED**</mark> and <mark style="color:$info;">**RECOMMENDED**</mark> tags distinguish baseline conformance from good practice.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-compass" style="color:$primary;">:compass:</i></h3></td><td><strong>Description</strong></td><td>What this Building Block is and where it sits in GovStack</td><td><a href="/experience-digital-transformation/analytics/technical-specifications/2.-description.md">2. Description</a></td></tr><tr><td><h3><i class="fa-puzzle-piece" style="color:$primary;">:puzzle-piece:</i></h3></td><td><strong>Key Digital Functionalities</strong></td><td>The twelve capabilities every deployment provides</td><td><a href="/experience-digital-transformation/analytics/technical-specifications/4.-key-digital-functionalities.md">4. Key Digital Functionalities</a></td></tr><tr><td><h3><i class="fa-code" style="color:$primary;">:code:</i></h3></td><td><strong>OpenAPI Specification</strong></td><td>Illustrative endpoint definitions</td><td><a href="/experience-digital-transformation/analytics/technical-specifications/13.-openapi-3.0-specification-appendix.md">13. OpenAPI 3.0 Specification (Appendix)</a></td></tr></tbody></table>

### 🧱 Foundations

1. [Version History](/experience-digital-transformation/analytics/technical-specifications/1.-version-history.md) — how this specification has evolved
2. [Description](/experience-digital-transformation/analytics/technical-specifications/2.-description.md) — scope, principles, and where it sits in GovStack
3. [Terminology](/experience-digital-transformation/analytics/technical-specifications/3.-terminology.md) — the vocabulary used throughout

### ⚙️ Capabilities and requirements

4. [Key Digital Functionalities](/experience-digital-transformation/analytics/technical-specifications/4.-key-digital-functionalities.md) — what every deployment must provide
5. [Cross-Cutting Requirements](/experience-digital-transformation/analytics/technical-specifications/5.-cross-cutting-requirements.md) — the non-functional baseline: privacy, governance, security, resilience
6. [Functional Requirements](/experience-digital-transformation/analytics/technical-specifications/6.-functional-requirements.md) — detailed, testable requirements, each tagged REQUIRED or RECOMMENDED

### 🗄️ Data, standards, and integration

7. [Data Structures](/experience-digital-transformation/analytics/technical-specifications/7.-data-structures.md) — the key data objects and their attributes
8. [Standards](/experience-digital-transformation/analytics/technical-specifications/8.-standards.md) — the open standards this Building Block complies with
9. [Building Block Interactions](/experience-digital-transformation/analytics/technical-specifications/9.-building-block-interactions.md) — how it fits with the rest of GovStack
10. [Other Resources](/experience-digital-transformation/analytics/technical-specifications/10.-other-resources.md) — key decisions, future directions, related specifications

### 📎 Appendices

11. [Internal Workflows and Data Lifecycle](/experience-digital-transformation/analytics/technical-specifications/11.-internal-workflows-and-data-lifecycle-appendix.md) — the ingestion-to-insight pipeline, step by step
12. [Reference Use Cases](/experience-digital-transformation/analytics/technical-specifications/12.-reference-use-cases-appendix.md) — proactive social support, SME risk, and climate NDC tracking
13. [OpenAPI 3.0 Specification](/experience-digital-transformation/analytics/technical-specifications/13.-openapi-3.0-specification-appendix.md) — illustrative endpoint definitions

***

Built to be domain-agnostic: the same capabilities that power a household-welfare use case apply, unchanged, to a climate NDC-tracking deployment. This specification is part of the wider [GovStack](https://specs.govstack.global/) Building Block catalogue.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/analytics/technical-specifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.