> For the complete documentation index, see [llms.txt](https://www.thecpsf.org/prod/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.thecpsf.org/prod/overview/readme.md).

# Welcome

## Introduction

The Common Policy and Standard Framework (CSPF) aims to establish a community-developed set of policies and standards. In doing this, it seeks to reduce duplicative efforts, efficiently allocate resources, leverage community knowledge, and ensure alignment with industry frameworks.&#x20;

## Usage

To adopt the CPSF, users must remove statements that are not applicable and replace variables with the appropriate values.&#x20;

> Users are required to immediately report security events and suspicious activity to <mark style="color:purple;">{incident\_contact\_information}</mark>.

## Contributions

Elementum pulvinar etiam non quam lacus suspendisse faucibus interdum posuere. Risus at ultrices mi tempus imperdiet nulla malesuada pellentesque. Scelerisque varius morbi enim nunc faucibus a. Neque egestas congue quisque egestas diam in arcu. Egestas integer eget aliquet nibh.

## License

This content is openly licensed via CreativeCommons [BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).


---

# 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://www.thecpsf.org/prod/overview/readme.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.
