From b8ad9da784aecf5c84747a7b0234ffbd542dd6d5 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 2 Nov 2026 19:21:51 +0100 Subject: [PATCH] Design 55: the review section uses the word the operator chose, architectural domain --- 03-DESIGN/01-to-be/55-the-knowledge-base.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/03-DESIGN/01-to-be/55-the-knowledge-base.md b/03-DESIGN/01-to-be/55-the-knowledge-base.md index 0ad9d7db..5dd5f94f 100644 --- a/03-DESIGN/01-to-be/55-the-knowledge-base.md +++ b/03-DESIGN/01-to-be/55-the-knowledge-base.md @@ -595,7 +595,7 @@ milestones and nothing of how a delivery runs; it only listens for the announcem | A stream that keeps its history, and an object bucket of a module's own | in the integration test: a history stream at its cap refuses a new message and keeps its oldest, its condition raised at 75 percent and cleared below; an object no version or draft names is removed after a day, one still named is kept; unit tests of registration refusing a name already taken | | A long record is judged whole, one part at a time | unit tests: the frame never passes 16 KiB and says what it cut, with twenty clauses of 2000 bytes and a 40 KiB Context; every question stays under 60 KiB with a 40 KiB section and that frame, and the head part with 40 KiB of clauses; a section over 40 KiB is refused saying split it; an unchanged section keeps its review, a changed frame asks it again | -**The fifth slice's tests, one per failure path** (ADR 0592; the review by aspect's testing ruling). Unit tests are +**The fifth slice's tests, one per failure path** (ADR 0592; the review by architectural domain's testing ruling). Unit tests are table-driven; one integration test starts the module whole against the real bus server. The module's count today is 1 integration and 104 unit tests; these add about 20 table cases and stay within the budget of 50 and 500. @@ -677,9 +677,9 @@ done: Semantic or vector search; a browser view (its reading of the buckets is announced, ADR 0592); line comments on a proposal (the judgement's findings name the section and clause instead); and the rules of how-we-build, which are not decision records. Each needs a decision of its own. -## Reviewed by aspect +## Reviewed by architectural domain -The fifth slice was reviewed by aspect on 2026-11-02 (four reviewers, two aspects each; the knowledge base's own +The fifth slice was reviewed by architectural domain on 2026-11-02 (four reviewers, two aspects each; the knowledge base's own review of ADR 0592's fourth version beside), and the lead ruled on every finding. What was found, and what answers it: | Aspect | Found | Answered by |