Documentation

The documentation gives the project a public technical spine.

This section gathers the project overview, architecture map, review path, and GitHub links in one place.

Documentation map

What belongs in the docs.

The documentation avoids broad guarantees and records the work in reviewable pieces. Each document has a purpose, a status, and a clear boundary.

  • Threat model and non-goals.
  • Architecture decision records.
  • Prototype notes and test plans.
  • Security review checklist.
  • Contribution guidelines and issue templates.