> 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/architecture/4-interoperability-architecture/4.4-architecture-scope.md).

# 4.4 Architecture Scope

Defines the three layers of architecture that GovStack distinguishes and clarifies where this specification applies and where to look for broader governance guidance.

The GovStack Architecture Specification with its Principles and Cross-Functional Requirements are applicable to what is commonly referred to as system and component architecture to support digital government interoperability. GovStack differentiates between:

* **Government Architecture** describes structure, behaviour, and views of the whole of government on governance, legal and digital layers. GovStack has published PAERA (Public Administration Ecosystem Reference Architecture) that covers these aspects and it is a highly recommended reading for leaders of government IT. More: [PAERA](https://paera.govstack.global/)
* **System Architecture** describes structure, behaviour, and views of the technology, data and application layer across multiple entities or within one entity of a government. In GovStack, this usually refers to the interaction between multiple Building Blocks, service applications, micro services or other components. The [C4 system context diagram](https://c4model.com/diagrams/system-context) or [C4 container diagram](https://c4model.com/diagrams/container) can be used for visualization.
* **Component Architecture** describes structure, behaviour and views of one system component. In GovStack, this usually refers to the inner architecture of one Building Block, service application or a microservice. The [C4 component view](https://c4model.com/diagrams/component) can be used for visualization.


---

# 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://specs.govstack.global/architecture/4-interoperability-architecture/4.4-architecture-scope.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.