Skip to content

~95% on SimpleQA (e.g. Qwen3.6-27B on a 3090). Supports all local and cloud LLMs (llama.cpp, Ollama, Google, ...). 10+ search engines - arXiv, PubMed, your private documents. Everything Local & Encrypted.

2.1 KB
Raw Blame

Migration documentation: authority and scope

PR #3299 produced durable migration decisions and executable guardians. These artifacts answer different questions and have different maintenance rules.

Which source answers which question

Question Authoritative source Kind
How should a WSGI-to-ASGI migration be planned? wsgi-to-asgi-playbook.md Generic playbook
How should a broad, long-lived branch be reviewed? ADR-0008 Durable decision
How was removed test coverage accounted for? ADR-0010 Durable decision and executable invariants
How were removed source symbols accounted for? ADR-0011 Durable decision and executable invariant
What changes for an operator upgrading? ../release_notes/ Operator-facing release contract

Reading rules

  1. Use code and executable tests for current behavior. ADRs explain a decision; they do not replace verification at the revision being released.
  2. Treat ADR measurements as historical evidence. Their exact revisions and counts describe the reviewed PR snapshot, not current product or security status. Raw working ledgers are intentionally not published as a current inventory.
  3. Use status-bearing systems for current work. Non-sensitive follow-ups belong in GitHub issues. Potential current security concerns follow SECURITY.md.
  4. Keep the guardians executable. If a deliberate rename or removal breaks a maintained invariant, update its rationale and guardian together; do not disable or delete the check.
  5. Use release notes for operator impact. They own upgrade actions and rollback instructions for the release that carries the migration.