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/data-models.md

@@ -238,23 +238,60 @@ After extraction, every topic contains the collected information.
 }
 ```
 
-This object represents the main output of the analysis pipeline.
+This object feeds the Canonical Meeting Knowledge representation.
 
 ---
 
-# Meeting Result
+# Canonical Meeting Knowledge
 
-The complete structured meeting.
+The canonical semantic representation of one meeting.
+
+This representation is the single source of truth for all downstream outputs.
 
 ```json
 {
     "meeting_id": "meeting_001",
 
-    "topics": []
+    "metadata": {},
+    "topics": [],
+    "facts": [],
+    "decisions": [],
+    "todos": [],
+    "questions": [],
+    "positions": [],
+    "technical_details": [],
+    "rationale": [],
+    "uncertainty": [],
+    "source_references": []
 }
 ```
 
-Protocol generation operates exclusively on this structure.
+This is the common intermediate representation for all final Output Views.
+The exact schema is not final and should be refined during future
+implementation work.
+
+---
+
+# Output Views
+
+The final outputs are independent renderings of the Canonical Meeting Knowledge.
+
+```text
+Canonical Meeting Knowledge
+    ├── Working Protocol
+    ├── Distribution Protocol
+    └── Knowledge Objects
+```
+
+The Working Protocol, Distribution Protocol and Knowledge Objects are not
+derived from one another. Each renderer reads the same canonical semantic
+model and selects the level of detail appropriate for its purpose.
+
+Knowledge Objects represent durable organizational knowledge such as processes,
+definitions, responsibilities, rules, accepted practices and long-term
+decisions. They are independent of the original meeting wording. Markdown is one
+possible presentation, but JSON or another structured format is expected to
+become the canonical storage format later.
 
 ---
 
@@ -272,4 +309,4 @@ Possible future additions include:
 
 These fields will only be introduced when they provide measurable benefits.
 
-The Meeting Lab intentionally avoids designing an overly complex schema in advance.
+The Meeting Lab intentionally avoids designing an overly complex schema in advance.