Behaviour Specs

The coded, plain-language specifications behind the test suite. Each behaviour carries a stable BHV code mapped to at least one tagged test, enforced at 100% by the agentic-test-driven traceability audit — so these pages are not a description of what the code happens to do, they are the contract the tests hold it to, written before the tests and before the implementation. PROOF codes record properties the type system guarantees outright: documented here, deliberately never tested.

📄️Charges-review gate & the Consulta exit (module: chargesreview)

Scope: #58 / PRD-006 SYS-REQ-201, 202. Phase 3/8 (Nota de Culpa, CHARGES_ISSUED). Two halves that

📄️Evidence chain of custody, SHA-256 (module: evidence)

Scope: #51 / PRD-005 SYS-REQ-401, 402, 403 (404 — reading evidence back — is #205, see below). Phase 2/8 (but reused by later evidence phases). Every

📄️Reading evidence back (module: evidenceread)

Status: implemented (#205). Every behaviour below has a passing test in

📄️Service of the Nota de Culpa (module: chargesdelivery)

Scope: #59 / PRD-006 SYS-REQ-301, 302. Phase 3/8 (CHARGES_ISSUED). Recording how and when the

📄️The response window & the arguido's defence (module: resposta)

Scope: #64, epic #63. Phase 5/8. Once the nota de culpa is served (chargesDeliveredAt, #59), the

📄️Case reminders (module: reminder)

Scope a free-text label plus a due