> 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/paera/1.-introduction-to-paera/scope-of-document.md).

# Scope of Document

This document provides an overview of the digital transformation of government services and is expected to be a key reference for practitioners.

* The first chapter is a traditional introduction where we aim to show how the document is set in context and the larger context of GovStack itself.
* The second chapter is about the basic assumptions that have created the need for such a document.
* The third chapter applies the GovStack approach to national-level digitization efforts. It describes how the GovStack building blocks make the most sense for national digital transformation.
* The fourth chapter defines the reference architecture of a public sector organization from the digital transformation perspective.
* The fifth chapter provides guidelines for practitioners on using this reference architecture.

The document is expected to be a practical and helpful guide for planning national public administration modernization initiatives. The authors intend to incorporate more knowledge and practical case studies over time, so we are interested in readers' feedback.


---

# 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/paera/1.-introduction-to-paera/scope-of-document.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.