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
This commit is contained in:
2026-07-31 09:32:12 +02:00
parent 09d125e54a
commit 23bbc744f7
12 changed files with 512 additions and 83 deletions
+64
View File
@@ -242,11 +242,74 @@ This object feeds the Canonical Meeting Knowledge representation.
---
# Canonical Extraction Object
Planned deterministic intermediate object created from raw chunk extraction
JSON.
Example:
```json
{
"id": "fact.chunk_03.0001",
"category": "fact",
"text": "...",
"source_references": [
{
"chunk_id": "chunk_03",
"source_file": "chunk_03_extraction.json",
"evidence": "..."
}
]
}
```
The Deterministic Canonicalizer should create this kind of object without an
LLM. It validates and normalizes raw extraction objects, assigns stable IDs and
source references, normalizes category names and basic field structure,
performs only safe deterministic cleanup, may group exact duplicates and must
preserve all source evidence.
It must not perform uncertain semantic merging.
---
# Consolidated Topic
Planned semantic object produced by the Semantic Consolidator.
Example:
```json
{
"topic_id": "topic_001",
"title": "...",
"background": [],
"decisions": [],
"action_items": [],
"open_questions": [],
"durable_information": [],
"uncertainty": [],
"source_references": []
}
```
The Semantic Consolidator may use the local LLM to merge semantically
equivalent statements, group content by topic, preserve evidence from all
contributing chunks, mark contradictions and uncertainty and separate durable
information from transient discussion.
It produces Canonical Meeting Knowledge. It does not directly write a protocol.
---
# Canonical Meeting Knowledge
The canonical semantic representation of one meeting.
This representation is the single source of truth for all downstream outputs.
It is a structured representation, preferably JSON, and is not itself a prose
protocol.
```json
{
@@ -260,6 +323,7 @@ This representation is the single source of truth for all downstream outputs.
"questions": [],
"positions": [],
"technical_details": [],
"durable_information": [],
"rationale": [],
"uncertainty": [],
"source_references": []