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/pipeline.md

@@ -36,10 +36,14 @@ Specialized Extraction
 Consolidation
         │
         ▼
-Structured Meeting
+Canonical Meeting Knowledge
         │
         ▼
-Protocol Generation
+Output View Rendering
+        │
+        ├── Working Protocol
+        ├── Distribution Protocol
+        └── Knowledge Objects
 ```
 
 Each stage receives a well-defined input and produces a well-defined output.
@@ -299,13 +303,13 @@ Planned
 
 ---
 
-# Stage 7 – Structured Meeting
+# Stage 7 – Canonical Meeting Knowledge
 
 ## Purpose
 
-Produce a complete machine-readable representation of the meeting.
+Produce the canonical semantic representation of one meeting.
 
-This is the primary output of the analysis pipeline.
+This representation is the single source of truth for all downstream outputs.
 
 Example:
 
@@ -326,29 +330,58 @@ Example:
 
 The exact schema will evolve during development.
 
+Conceptually, the Canonical Meeting Knowledge should include:
+
+- meeting metadata
+- topics
+- facts
+- decisions
+- action items
+- open questions
+- positions
+- technical information
+- rationale and discussion context
+- contradictions or uncertainty
+- source references and evidence
+
+The detailed schema remains future implementation work.
+
 ## Current Status
 
 Planned
 
 ---
 
-# Stage 8 – Protocol Generation
+# Stage 8 – Output View Rendering
 
 ## Purpose
 
-Generate human-readable documents from structured meeting data.
+Render purpose-specific outputs from Canonical Meeting Knowledge.
 
-Possible outputs include:
+The planned output products are:
 
-- Full protocol
-- Executive summary
-- Action list
-- Decision log
-- Technical report
+- Working Protocol (`working_protocol.md`, Arbeitsprotokoll)
+- Distribution Protocol (`distribution_protocol.md`, Verteilerprotokoll)
+- Knowledge Objects, rendered as a Knowledge-base Entry (`knowledge_entry.md`)
+  and later stored in a structured format such as `knowledge_entry.json`
+  (Wissensdatenbankeintrag)
 
-Protocol generation never performs additional analysis.
+Output rendering never performs additional analysis.
 
-It only transforms existing structured information into readable text.
+It only transforms existing structured information into the required view.
+
+The outputs are rendered in parallel from the canonical representation. The
+Distribution Protocol is not derived from the Working Protocol, and Knowledge
+Objects are not derived from either protocol.
+
+Rendering may be deterministic, template-based or LLM-assisted depending on the
+output and implementation maturity.
+
+Completeness differs by output:
+
+- The Working Protocol optimizes for recall and traceability.
+- The Distribution Protocol optimizes for relevance and brevity.
+- Knowledge Objects optimize for durability and reuse.
 
 ## Processing Type
 
@@ -420,9 +453,9 @@ A processing stage may be replaced by another implementation as long as it prese
 
 ⬜ Consolidation
 
-⬜ Structured Meeting
+⬜ Canonical Meeting Knowledge
 
-⬜ Protocol Generation
+⬜ Output View Rendering
 ```
 
-The immediate development focus is **Topic Segmentation**, as it provides the semantic structure on which all subsequent processing stages depend.
+The immediate development focus is **Topic Segmentation**, as it provides the semantic structure on which all subsequent processing stages depend.