Document project architecture and development methodology

- add AGENTS.md with development and prompt-engineering rules
- add PROJECT_KNOWLEDGE.md summarizing current architecture and findings
- add CHANGELOG.md
- add ROADMAP.md
- establish experiments.md as the project's experiment log
- document Canonical Meeting Knowledge architecture
- document Output Views and Knowledge Objects
- capture accepted experimental results and engineering methodology

ROADMAP.md

@@ -0,0 +1,185 @@
+# Roadmap
+
+No dates are assigned. Phases describe dependency order, not release promises.
+
+## Phase 1 - Stable Local Extraction
+
+Goal:
+
+- Establish reliable per-chunk extraction behavior for core meeting semantics.
+
+Deliverables:
+
+- Stronger Gold Standard coverage across facts, positions, decisions, todos,
+  questions and technical details.
+- Improved category prompts.
+- Repeatable evaluation workflow.
+- Documented prompt experiment log.
+
+Prerequisites:
+
+- Existing chunk extraction flow.
+- Existing Gold Standard runner and methodology.
+
+Out of scope:
+
+- Full-transcript LLM extraction.
+- Larger context-window strategy changes without an explicit experiment.
+- Consolidation or final protocol rendering.
+
+## Phase 2 - Consolidation
+
+Goal:
+
+- Merge independent extraction results into a coherent meeting-level
+  representation without losing evidence.
+
+Deliverables:
+
+- Duplicate merging.
+- Evidence retention.
+- Category-shift reconciliation, especially facts versus positions and
+  positions versus decisions.
+- Contradiction and uncertainty markers.
+- Consolidated meeting representation.
+
+Prerequisites:
+
+- Stable local extraction baseline.
+- Gold tests that expose cross-chunk duplication and category shifts.
+
+Out of scope:
+
+- Final Canonical Meeting Knowledge schema.
+- User-facing protocol polish.
+- Retrieval or RAG integration.
+
+## Phase 3 - Canonical Meeting Knowledge
+
+Goal:
+
+- Define and implement the semantic intermediate model that becomes the source
+  of truth for downstream outputs.
+
+Deliverables:
+
+- Canonical Meeting Knowledge schema.
+- Source evidence and traceability fields.
+- Clear distinction between durable knowledge and meeting-specific actions.
+- Migration path from consolidated extraction JSON into the canonical model.
+
+Prerequisites:
+
+- Consolidation behavior that preserves evidence and uncertainty.
+- Agreement on required semantic categories.
+
+Out of scope:
+
+- GUI.
+- Export formats beyond those needed to validate the model.
+- Knowledge-system storage design.
+
+## Phase 4 - Output Views
+
+Goal:
+
+- Render purpose-specific outputs from Canonical Meeting Knowledge without
+  changing meaning.
+
+Deliverables:
+
+- Working Protocol / Arbeitsprotokoll renderer.
+- Distribution Protocol / Verteilerprotokoll renderer.
+- Knowledge Objects / Wissensdatenbankeintrag renderer or structured export.
+- Tests or checks showing that output views are parallel renderings of the same
+  canonical model.
+
+Prerequisites:
+
+- Implemented Canonical Meeting Knowledge.
+- Clear audience and completeness rules for each output view.
+
+Out of scope:
+
+- Additional analysis during rendering.
+- Deriving one output view from another.
+- Retrieval integration.
+
+## Phase 5 - Review and Quality Control
+
+Goal:
+
+- Add optional review stages that improve omission detection, consistency and
+  model selection.
+
+Deliverables:
+
+- Optional whole-transcript review.
+- Omission detection.
+- Consistency checks.
+- Model comparison workflow.
+- Hardware and runtime benchmarks.
+
+Prerequisites:
+
+- Stable extraction, consolidation and canonical model.
+- Representative test meetings.
+
+Out of scope:
+
+- Automatic acceptance of review suggestions without evidence.
+- Product UI work.
+- Cloud deployment.
+
+## Phase 6 - Productization
+
+Goal:
+
+- Turn the validated pipeline into a usable local workflow.
+
+Deliverables:
+
+- Recording/transcription workflow.
+- FFmpeg integration.
+- Meeting metadata capture.
+- Participant entry.
+- GUI.
+- Stable deployment process.
+- Export workflows.
+
+Prerequisites:
+
+- Stable pipeline stages and output views.
+- Clear operational requirements for local use.
+
+Out of scope:
+
+- Enterprise knowledge retrieval.
+- Future Meeting Assistant integration beyond export contracts.
+- Cloud-first architecture.
+
+## Phase 7 - Knowledge-System Integration
+
+Goal:
+
+- Reuse durable meeting knowledge in broader knowledge systems.
+
+Deliverables:
+
+- Structured Knowledge Objects.
+- Retrieval-ready storage format.
+- Future RAG integration path.
+- Reuse contracts for Meeting Assistant and other knowledge systems.
+
+Prerequisites:
+
+- Canonical Meeting Knowledge and Knowledge Objects are implemented and stable.
+- Durable knowledge is separated from meeting-specific actions and discussion
+  history.
+
+Out of scope:
+
+- Building a full enterprise search product inside Meeting Lab.
+- Treating raw transcripts or generated protocols as the knowledge source of
+  truth.
+