> 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/docs/roadmap.md).

# Roadmap

Honest public direction for KlassApp. Sourced from real shipped work and the **Future Initiatives** logged in maintainer notes — not from speculative product fiction.

Last curated: September 2026.

## Shipped (recent)

| Area                               | What landed                                                                                                                                               |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Four-surface design**            | Coordinated production cutover of landing/auth/errors, admin dashboards, onboarding wizard, and Toshi panel (design-system kit + clay chrome).            |
| **Security hardening**             | Cross-school access-control fixes on teacher student surfaces; secrets removed from the tree (env-only LLM keys); staging MySQL isolated from production. |
| **Community health**               | Code of Conduct, Contributing, Security, issue/PR templates; Docsify theme aligned to the design system; docs map + archive banner for stale `docs/dev/`. |
| **Class teacher invite (Phase 1)** | Admin can invite a teacher as class teacher by email (optional path; admin-driven setup remains).                                                         |

Live product: [klassapp.xyz](https://klassapp.xyz). Staging demo access: <community@klassapp.xyz>.

## In progress

| Area                     | Notes                                                                                                                                                     |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Docs structure**       | Architecture bridge + public roadmap + Docsify brand theme shipped; community Docsify content refreshed to match shipped product (see community Docsify). |
| **Kabale Junior School** | Real production school (ongoing ops and onboarding follow-through — not a speculative pilot).                                                             |

## Future (logged initiatives)

These are real backlog items from maintainer Future Initiatives — scoped or deferred, not invented here:

| Initiative                          | Status                                                                                                                                        |
| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Public status page (Instatus)**   | Deferred until after the UI design phase.                                                                                                     |
| **CT invite Phase 2**               | Wizard nudge to invite a class teacher after a class is created (Phase 1 already shipped).                                                    |
| **CT invite magic link**            | Replace temp-password email with a tokenized accept link.                                                                                     |
| **GeGoK12 → KlassApp UI migration** | Phased migration off inherited UI toward the formal design system — not yet scoped.                                                           |
| **Security & trust**                | Break-glass superadmin access; staff business IDs; self-hosted hash-chained tamper-evident student records; optional governance voting later. |
| **Security maturity ladder**        | Growing test coverage → professional pentest before wide launch → bug bounty only after that.                                                 |
| **Toshi as an MCP server**          | Let external AI clients call into KlassApp via Laravel MCP — buildable, not started.                                                          |
| **Toshi free-form chat**            | Guided flows work today; open-ended LLM chat stays gated until a funded key is activated.                                                     |
| **Go-to-market plan**               | Formal GTM as its own discovery-then-build track — not started.                                                                               |
| **After UI phase**                  | Broader name-lookup sweeps; WhatsApp OAuth for parent linking; more wizard/Toshi parity.                                                      |

## Out of scope here

Do **not** treat the old community Docsify roadmap file as current. It mixed unconfirmed product ideas and incorrect pricing. That file is deprecated — see the note on [`community/roadmap.md`](/klassapp-documentation/docs/community/roadmap.md).


---

# 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/docs/roadmap.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.