Improve semantic classification precision for BUG-015

docs/architecture.md

@@ -375,6 +375,20 @@ extraction results into `meeting_protocol.md` for technical validation. The
 planned architecture separates Canonical Meeting Knowledge from the final Output
 Views documented in `output-views.md`.
 
+## Extraction classification contract
+
+Decision, Action Item and Open Question extraction shares one evidence-oriented
+classification contract. It is placed after the transcript so it remains the
+final classification instruction in the single multi-category extraction call.
+Decisions require a settled outcome; Action Items require established work;
+Open Questions require a concrete unresolved need. Unsupported candidates must
+not be moved into another category.
+
+Action existence and responsibility attribution are separate checks. A valid
+Action Item may have no known owner, while a named owner requires explicit
+assignment, volunteering or acceptance. These are semantic LLM classifications;
+deterministic validation must not guess intent from keywords.
+
 ## Semantic Consolidator failure handling
 
 Semantic Consolidator V0 preserves every raw model response before parsing.
@@ -396,6 +410,28 @@ an instruction not to emit an identical group more than once. Both attempts
 and the detected repetition metadata are preserved. If the retry also fails,
 the stage fails normally; it does not make another LLM call.
 
+## Working Protocol V2 renderer contract
+
+The renderer deterministically projects consolidated items to the semantic
+fields required for presentation and omits bulky provenance fields from the
+LLM request. Every renderable item remains represented; structurally empty
+items are recorded separately rather than turned into invented prose. The
+compact renderer input is preserved as an artifact.
+
+The exact Markdown structure is generated from the same heading constants used
+by the validator and appended after the renderer input so it remains visible
+within the evaluated context. Decisions, action items and open questions carry
+input-derived hidden coverage markers. Strict validation requires every such
+renderable priority item exactly once in its matching section and rejects
+missing, duplicate, wrong-section or invented markers. Facts and technical
+details remain condensable as background.
+
+Renderer output budgeting is adaptive to required priority content and prompt
+size, while an explicit `num_predict` override remains authoritative. Raw model
+output is always preserved, and `working_protocol.md` is written only after
+strict structure and coverage validation passes. The renderer does not retry
+automatically.
+
 ---
 
 # Next Milestone