Refine canonical meeting knowledge architecture

- establish Canonical Meeting Knowledge as the semantic source of truth
- introduce Output View Rendering architecture
- define Working Protocol, Distribution Protocol and Knowledge Objects as parallel renderers
- document renderer responsibilities and terminology
- clarify future Knowledge Object architecture
- document long-term reuse for enterprise knowledge systems

docs/architecture.md

@@ -100,9 +100,11 @@ Specialized Extraction
     ↓
 Consolidation
     ↓
-Structured Meeting Data
+Canonical Meeting Knowledge
     ↓
-Protocol Generation
+Output View Rendering
+    ↓
+Working Protocol / Distribution Protocol / Knowledge Objects
 ```
 
 Each stage solves one clearly defined problem.
@@ -185,11 +187,25 @@ Typical responsibilities:
 
 ## protocol/
 
-Generates human-readable output from structured meeting data.
+Generates output views from Canonical Meeting Knowledge.
 
-Protocol generation never invents information.
+Output generation never invents information.
 
-It only reformulates the analysis results.
+It only reformulates the analysis results for a specific audience and purpose.
+Depending on the output and maturity of the implementation, a renderer may be
+deterministic, template-based or LLM-assisted.
+
+The planned output products are:
+
+- Working Protocol (`working_protocol.md`, Arbeitsprotokoll)
+- Distribution Protocol (`distribution_protocol.md`,
+  Verteilerprotokoll)
+- Knowledge Objects, which may be rendered as a Knowledge-base Entry
+  (`knowledge_entry.md`) and later stored in a structured format such as
+  `knowledge_entry.json` (Wissensdatenbankeintrag)
+
+These are parallel renderings of the same canonical semantic model, not
+documents derived from one another.
 
 ---
 
@@ -214,6 +230,7 @@ Examples:
 - segmentation.md
 - prompts.md
 - experiments.md
+- output-views.md
 
 The architecture document only describes the overall system.
 
@@ -231,6 +248,11 @@ The current extraction step still performs multiple tasks simultaneously.
 
 This was sufficient as a proof of concept but does not reflect the intended long-term architecture.
 
+The current protocol builder is also an interim implementation. It concatenates
+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`.
+
 ---
 
 # Next Milestone
@@ -256,4 +278,4 @@ Only after reliable topic segmentation has been achieved will the specialized ex
 
 The Meeting Lab assumes that the greatest improvement in transcript quality will not come from increasingly powerful language models.
 
-Instead, quality is expected to emerge from a pipeline that decomposes a complex problem into many small, clearly defined and independently testable processing steps.
+Instead, quality is expected to emerge from a pipeline that decomposes a complex problem into many small, clearly defined and independently testable processing steps.