Public operator, client and plugin documentation lives in website/docs/. This directory contains internal planning, assessments and design records.
| Document | Purpose |
|---|---|
| Backlog | Implementation priorities; some older entries need status reconciliation. |
| Testing backlog | Test and CI gaps; older blocked entries are not a fresh audit of current behavior. |
| Release readiness | Release gates and historical rehearsal evidence; not release signoff. |
| Security assessment | Findings, remediation, trust decisions and independent review history. |
| Security evidence | Retained DBB probe and captured results for the latest assessment. |
| Document | Status |
|---|---|
| Authentication and enrollment | Requirements, HLD and eleven-PR implementation plan stamped after actual DBB and SWE reviews. Next is operator authority/local control implementation; no code slice has started. |
| IMAP folder policy | Much of the policy is implemented; the proposed client policy-check surface remains design work. |
| Discovery surface | Mixes implemented discovery with proposed diagnostics. Public references describe current behavior. |
| Transport and identity | Future identity direction; its earlier HTTP transport proposal is superseded by native HTTPS. |
archive/ holds superseded drafts. Archiving a draft does not mean that every proposal in it was implemented, approved or cancelled. Use the public references for the shipped contract and the active planning documents for remaining work.