The user-facing documentation tree, organized by audience (maintainer
process docs live outside the repo in docs-local/; criteria in
documentation-governance.md). This tree is the
English canonical and the sole content source of
fulla.dev (Docusaurus, zero copies); the Chinese
translation mirrors it at website/i18n/zh-CN/ and is served at
fulla.dev/zh-CN.
- Architecture Overview — tech stack, module layout, authorization-code flow, storage strategy
- Security Architecture — threat model, token lifecycle, keys & hashes, security headers & rate limiting
- Benchmark comparison (methodology)
C++ SDK (embedded): Integration Guide · Runtime Contract
HTTP API (any language): API Reference (authoritative contract: openapi.yaml) · OIDC Integration · Social Login · RBAC & Access Control
Token Lifecycle · Session Management · Multi-Tenancy · Data & Persistence
Production Deployment · Docker Deployment · Windows / Docker Desktop · Configuration Guide · Observability · Account Lockout · PostgreSQL Major Upgrades · Deployment Verification Checklist
Testing Guide · CI/CD · Versioning & Release · Documentation Governance · Frontend tests: Admin cases · User cases · E2E methodology
docs/adr/ — 13 current architecture decision records (SDK layering, ErrorCatalog, opaque tokens, coroutine exclusion, …) plus three historical archives: the OAuth/OIDC compliance audit (2026-08-07 baseline, all 31 findings fixed), the rename impact analysis, and the repo professionalization audit (the three archives are kept in Chinese with an English note).
Earlier design archives (kiro specs in full, PRD designs) live in git history and maintainer-local storage; the ADRs distill the decisions that still hold.