> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/implementation-playbook/0.9.0/govstack-implementation-playbook/adopt-govstack/reference-architecture.md).

# Reference architecture

Reference architecture is the blueprint used to put the pieces of the organizational & systems puzzle together. Digital teams use reference architecture to promote the reuse of common assets and identify capability gaps. It:&#x20;

* Defines a common language for consistent communication within the organization&#x20;
* Outlines all capabilities needed to achieve the best outcome&#x20;
* Provides the ability of systems or software to exchange and make use of information &#x20;
* Establishes standard systems, and a common way to exchange information

<figure><img src="/files/z6XyGvyZlqBUjDhxxskw" alt=""><figcaption><p>Example: Enterprise Architecture from Abu Dabhi, Finalist of GovStack WSIS Special Prize 2023</p></figcaption></figure>

<figure><img src="/files/ifQq1fv46MyxeFINyqAH" alt=""><figcaption><p>Government Ecosystem Reference Architecture (GERA)</p></figcaption></figure>

{% tabs %}
{% tab title="Activities" %}

* Develop the systems/software/platform catalog to identify reusable software components/Building Blocks that can support the digitization of services.
* Identify additional Building Blocks/ reusable software components that are critical in building a national stack that can facilitate the development of prioritized citizen-centric digital services.&#x20;
* Define the approach to adding new/updated Building Blocks within the national stack, either through tendering, developing indigenously, or re-using existing Building Blocks. [GovExchange ](https://exchange.dial.global/)provides a catalog of digital public goods that can be used as a reference.

**Examples of Reference Architectures:**

* In Australia, their [reference architecture document](https://www.architecture.dta.gov.au/sp_aga2?id=aga2_how_to_use) provides digital teams the guidance they need to align current and emerging tech into a sound orchestration of solutions to enable digital government service design and delivery

<figure><img src="/files/bnPwCYoYz6RtYwXDXb4x" alt=""><figcaption><p>Source: Australian <a href="https://architecture.digital.gov.au/sites/default/files/2023-07/22-0109%20Australian%20Government%20Architecture_v11.pdf">Reference Architecture</a></p></figcaption></figure>

{% embed url="<https://youtu.be/NSBtgW09mHo>" %}
Australian Whole of Government Architecture &#x20;
{% endembed %}

* [GovStack Architecture and non-functional requirements](https://govstack.gitbook.io/specification/architecture-and-nonfunctional-requirements)
* [GovStack Ecosystem Reference Architecture and Business Guide for Public Digital Platforms](https://docs.google.com/document/d/1Qa31kAy_Kz9MsphXunS0UqRJpoQ2i8HV/edit?usp=sharing\&ouid=107531587157017296326\&rtpof=true\&sd=true),  [The Open Group Standard](https://www.opengroup.org/)
  {% endtab %}

{% tab title="Responsabilities" %}
Who does what:

* Chief government architects - Coordinate the work around the reference architecture&#x20;
* [Solutions architects](https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/4D3oEcPGpYoKnwkQmCzJ/~/changes/389/govstack-implementation-playbook/sample-digital-team-composition/govstack-user-profiles-taxonomy#solution-architect) from government entities - Actively participate in the co-design of the document, the reference architecture working group, and the training program&#x20;
* [Service designers](https://specs.govstack.global/workflow/workflow-development/) - Actively participate in co-design sessions, the reference architecture working groups, and the training program&#x20;
  {% endtab %}

{% tab title="Deliverables" %}

* Government Enterprise Architecture
* Implementation guidelines
* e-learning courses for stakeholders (public servants and ICT service providers)
  {% endtab %}
  {% endtabs %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://specs.govstack.global/implementation-playbook/0.9.0/govstack-implementation-playbook/adopt-govstack/reference-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
