Document canonicalization and consolidation milestone

- preserve Working Protocol Synthesizer V0 as comparison baseline
- introduce deterministic canonicalization stage
- define semantic consolidator responsibilities
- clarify Canonical Meeting Knowledge generation
- document source-language output policy
- align roadmap, architecture and experiment log

docs/output-views.md

@@ -13,6 +13,10 @@ Meeting transcript
     ->
 chunk extraction
     ->
+Deterministic Canonicalizer
+    ->
+Semantic Consolidator
+    ->
 Canonical Meeting Knowledge
     ├── Working Protocol
     ├── Distribution Protocol
@@ -45,6 +49,18 @@ The detailed schema is future implementation work. The current implementation
 still uses simple extraction JSON files and a basic Markdown protocol builder for
 technical validation.
 
+The next planned architecture stage before this representation is explicit:
+
+- The Deterministic Canonicalizer validates and normalizes extraction objects,
+  assigns stable source references and IDs, performs only safe deterministic
+  cleanup and preserves all source evidence. It uses no LLM and must not make
+  uncertain semantic merges.
+- The Semantic Consolidator uses the local LLM to merge semantically equivalent
+  statements, group content by topic, preserve evidence from all contributing
+  chunks, mark contradictions and uncertainty, separate durable information from
+  transient discussion and produce Canonical Meeting Knowledge. It does not
+  directly write a protocol.
+
 ## Renderers
 
 Each Output View is produced by a renderer.
@@ -57,6 +73,10 @@ Depending on the implementation, rendering may be:
 
 The architecture does not assume that every renderer must always use an LLM.
 
+Rendered protocol language should normally match the dominant language of the
+source transcript or consolidated meeting knowledge unless an explicit output
+language is requested.
+
 ## Working Protocol
 
 Suggested filename: `working_protocol.md`