> 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/gis/5-cross-cutting-requirements.md).

# 5 Cross-Cutting Requirements

This section will highlight important requirements or describe any additional cross-cutting requirements that apply to this Building Block.

The Cross-cutting requirements described in this section are an extension (adds on) to the cross-cutting requirements defined in the architecture specification document.

## 5.1 Personal Data Privacy (REQUIRED)

* Safeguard personal data and share only as authorized.
* Adhere to GovStack architecture's privacy principles.

## 5.2 All transactions must be Audit Logged (RECOMMENDED)

* Log transactions with timestamps, user information, and affiliations.
* Protect logs from tampering.
* Comply with Govstack's data policy and audit logging rules.

## 5.3 Interoperability (REQUIRED)

* Align with OGC and ISO/TC 211 geospatial standards for data sharing.
* Seamlessly integrate with other GovStack components.

## 5.4 Exception Handling (REQUIRED):

* Implement effective mechanisms and procedures to handle exceptions and errors.
* Ensure that errors don't lead to system crashes or data loss.

## 5.5 Incorporation of Relevant Open GIS Standards and APIs (REQUIRED)

* [OGC APIs](https://ogcapi.ogc.org/)
* [OGC Schemas](https://schemas.opengis.net/)
* [OGC Service Standards](https://www.ogc.org/standards/)
* [GDAL Documentation](https://gdal.org/index.html)
* [ISO/TC 211 - Geographic information/Geomatics](https://www.iso.org/committee/54904.html)


---

# 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/gis/5-cross-cutting-requirements.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.