> 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-09-29.md).

# KlassApp handoff · 2026-09-29

Start with **HANDOFF.md**. It orders all open work (bugs first) into 22 PRs, each with acceptance checks.

* **Designed from:** `main @ a9013f74b384`.
* **Checked at the end:** `main` was 2 commits past that (the Ugandan admission-fields PR). HANDOFF.md lists the drift.
* `specs/`: earlier specs that HANDOFF.md points to rather than restating.
* `concepts/`: open the HTML files directly in a browser. New in Task C: `concepts/task-c/role-lists.html`, `coverage-map.html`, `landing-motion.html`, `landing-background.html`, and `concepts/public-pages/screens/admission.html`.
* `B-emails-code/`: the email shell, previews and Laravel mail theme from Task B.
* `styles.css`, `tokens/`, `styles/`, `assets/`: the design system the concepts load.

Contrast ratios are calculated from hex unless marked "browser-measured". Frame timing under a 4× CPU throttle has **not** been measured; PR 16 requires a trace.


---

# 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-09-29.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.