> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/design/system/klassapp-handoff-2026-10-01-documents.md).

# Formal document template: handoff, 2026-10-01

* `HANDOFF.md`: the full spec for page, type, colours, first page, running header and footer, tables, the draft state, the five document types, signature blocks, a `.dotx` build checklist, and acceptance checks.
* `template/FormalDocument.dc.html`: the HTML/PDF template, a 3-page DPA sample. Open it in a browser; its paper (A4 or Letter) and draft state can be switched in the editor. `_ds_bundle.js` isn't included, and the template doesn't need it.
* `concepts/dpa-accept.html`: the in-app click-to-accept page for the data processing agreement, with five states: read and accept, errors, accepted, not the main admin, and new version. Shown at 1280 and 375.
* **Signed PDF:** turn on `signed` in the template to see the acceptance block that replaces the signature lines (HANDOFF section 12).
* `template/assets/`: the stacked light logo (first page) and the icon mark (running header). **For Word, export the logo as a 600 dpi PNG.**
* `design-system/`: the token stylesheets.

**Brand rule:** KlassApp is global, for schools from nursery to secondary, with no country-only framing. The founding-schools offer has no stated limit.

Contrast ratios are calculated from hex. Page fit was designed for both A4 and Letter; check it in your PDF export.


---

# 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://klassdocs.gitbook.io/klassapp-documentation/design/system/klassapp-handoff-2026-10-01-documents.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.