> 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/9.-building-block-interactions.md).

# 9. Building Block Interactions

How the Analytics Building Block interacts with other GovStack Building Blocks — upstream dependencies, integration layer, and downstream recipients.

{% hint style="info" %}
🔗 **Seven Building Blocks, one integration fabric.** Most interactions flow through the Information Mediator.
{% endhint %}

The Analytics Building Block interacts with the following GovStack Building Blocks:

| Building Block                  | Interaction Type                | Description                                                                                                                                                                                                                                |
| ------------------------------- | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Identity / Access Management BB | Upstream dependency             | Provides federated SSO authentication tokens validated by the Analytics BB and manages role assignments reflected in the Analytics BB policy engine.                                                                                       |
| Consent BB                      | Upstream dependency (selective) | Manages consent records and status; the Analytics BB reads consent status for PBAC enforcement where personal data is involved. It does not perform PII anonymisation.                                                                     |
| Information Mediator BB         | Integration layer               | Provides the secure inter-BB messaging fabric used to receive data (and, upstream, to pseudonymise PII), and to dispatch workflow-trigger and publication signals downstream.                                                              |
| Digital Registries BB           | Upstream data source            | Authoritative source for transactional entity data; registries deliver harmonised records to the Analytics BB via the Information Mediator. For climate deployments these include climate registries (indicators, GHG inventory, sectors). |
| Scheduler BB                    | Orchestration support           | Triggers time-based pipeline runs and scoring/reconciliation jobs within the Analytics BB.                                                                                                                                                 |
| Workflow BB                     | Downstream recipient            | Receives execution signals from the Analytics BB proactive-trigger module to initiate automated service-delivery or review workflows.                                                                                                      |
| Messaging BB                    | Downstream notification         | Receives notification dispatch requests following proactive-trigger or data-publication events.                                                                                                                                            |

When the Building Block is deployed for a climate use case, upstream data sources reached through the Information Mediator include national GHG-inventory and statistics systems and Earth-observation providers; downstream consumers include NDC-tracking dashboards and transparency-reporting services.


---

# 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/9.-building-block-interactions.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.