Define topic-oriented protocol architecture
This commit is contained in:
@@ -521,6 +521,23 @@ conversation management into commitments. The complete taxonomy, trade-offs,
|
||||
architecture interactions and migration questions are recorded in
|
||||
[`design/evidence_commitment_model.md`](design/evidence_commitment_model.md).
|
||||
|
||||
## Topic-oriented primary protocol
|
||||
|
||||
One of the highest-level Version 2 requirements is:
|
||||
|
||||
> **The protocol is primarily a topic-oriented reconstruction of the meeting, not a category-oriented listing of extracted information.**
|
||||
|
||||
Semantic categories remain metadata and supporting structure within topics;
|
||||
they must not dictate the main document structure. The conceptual target flow
|
||||
is `Transcript -> Evidence Extraction -> Topic Reconstruction -> Semantic
|
||||
Synthesis -> Protocol Rendering`. The primary renderer should eventually
|
||||
receive topic-oriented semantic knowledge. Category-oriented Action Item,
|
||||
Decision, Open Question and management views remain useful derived outputs.
|
||||
|
||||
The detailed rationale, example, architectural implications and explicit
|
||||
deferral of a final Topic Reconstruction schema are documented in
|
||||
[`design/evidence_commitment_model.md`](design/evidence_commitment_model.md#thematic-protocol-as-the-primary-structure).
|
||||
|
||||
Implementation is intentionally postponed until this architecture has been
|
||||
reviewed. No Version 2 goal in this section changes current extraction,
|
||||
canonicalization, consolidation or rendering behavior.
|
||||
|
||||
Reference in New Issue
Block a user