How documents in this project relate, what feeds what, and the update rules.
┌──────────────────────────────┐
│ ARCHITECTURE REFERENCE │
│ (this wiki — canonical) │
│ │
│ State machines, flows, │
│ components, companies, │
│ EDICOM interface, models │
└──────────┬───────────────────┘
│
┌───────────────┼───────────────┐
│ │ │
┌─────▼─────┐ ┌─────▼─────┐ ┌─────▼─────┐
│ Design │ │ Diagrams │ │ Memory │
│ Docx │ │ (.drawio) │ │ Bank │
│ (OneDrive) │ │ (OneDrive)│ │ (.claude) │
└───────────┘ └───────────┘ └───────────┘
Architecture Reference is the single source of truth. Everything else derives from it.
decisions.md ───────────────┐
(PROJECT OVERSIGHT) │
│
Meeting minutes ────────────┼──→ Architecture Reference (wiki)
& transcripts │
│
Open questions ─────────────┘
(when answered → decision)
| Source | Location | How It Feeds |
|---|---|---|
| decisions.md | PROJECT OVERSIGHT/ |
Decisions register. New architecture/integration/process decisions → update Architecture Reference |
| issues.md | PROJECT OVERSIGHT/ |
When resolved, may produce decisions → update decisions.md → update Architecture Reference |
| risks.md | PROJECT OVERSIGHT/ |
When mitigated, may produce decisions |
| Open Questions | PROJECT OVERSIGHT/Archive/ |
When answered → becomes a decision → update decisions.md → update Architecture Reference |
| Meeting minutes | meetings/, minutes/ |
Decisions extracted → logged in decisions.md |
| Target | Location | Sync Rule |
|---|---|---|
| Spec (split files) | Solution/spec/ (13 files: 00-overview.md to 12-appendices.md + 13-ui-screens.md) |
Update when Architecture Reference changes. Sections mirror wiki content with additional implementation detail. |
| Database DDL | Solution/spec/schema/create-schema.sql |
Full SQL Server DDL (5 tables). Update when table/column changes are made. |
| ERD (draw.io) | Solution/spec/schema/erd.drawio |
draw.io diagram of all tables and relationships. Update when schema changes. |
| Diagrams | Solution/spec/schema/ and design/ |
Redraw when flows, state machines, or components change. |
| Wiki pages | This wiki (ERP-Integration, Country-Rules, EDICOM-Integration, etc.) | Reference Architecture Reference; don't duplicate its content. |
1. Add row to decisions.md (the decisions register)
2. If it affects architecture:
a. Update Architecture Reference (wiki)
b. Update dependent wiki pages (ERP-Integration, Country-Rules, EDICOM-Integration)
c. Update spec files (Solution/spec/) if implementation detail changes
d. Update DDL + ERD if schema changes (Solution/spec/schema/)
e. Update diagrams if flows change
1. Mark resolved in issues.md (with resolution + date)
2. If resolution = new decision:
a. Add to decisions.md
b. Follow "When a decision is made" above
1. Update risks.md (move to Mitigated/Closed)
2. If mitigation = new decision:
a. Add to decisions.md
b. Follow "When a decision is made" above
1. Move to Resolved section in Open Questions register
2. If answer = new decision:
a. Add to decisions.md
b. Follow "When a decision is made" above
/OneDrive-Business/Documents 1/chart/e-invoicing/
PROJECT OVERSIGHT/
decisions.md ← decisions register (single source)
issues.md ← issues register
risks.md ← risk register
Archive/
Open_Questions.md ← 100 open questions
CHART_E-Invoicing_Decisions.csv ← original 55 decisions (archived)
CHART_E-Invoicing_Issues.csv ← original 34 issues (archived)
design/
CHART_E-Invoicing_Architecture_Design v2.docx ← shared design doc
diagrams/ ← draw.io diagrams
high level design/ ← high-level flow diagrams
meetings/ ← meeting materials
minutes/ ← meeting minutes
Architecture Reference ← CANONICAL source of truth (state machines, flows, companies, components)
Country Rules ← per-country e-invoicing models, formats, mandates, penalties
ERP Integration ← per-ERP: AR/AP flows, PDF handling, AP tool chains, file shares
EDICOM Integration ← EDICOM services, UCF format, API spec, network security
Information Flow ← this page
Project Organisation ← team, RACI, governance
Milestones ← dates, dependencies, critical path
Decisions Log ← architecture decisions (DEC-001+) and meeting decisions (MD-001+)
Actions Log ← consolidated action tracker
Risks and Issues ← risk register, issue log
ERP-EDICOM Integration Options ← build vs buy analysis
Solution/spec/ ← architecture spec (13 split markdown files + mockups)
Solution/spec/schema/ ← database DDL (create-schema.sql) + ERD (erd.drawio)
Meetings/minutes/ ← 74 extracted meeting minutes + INDEX.md
Data/mock invoices/ ← mock invoice data
| Anti-Pattern | What to Do Instead |
|---|---|
| Update the spec without updating the wiki | Update wiki first, then sync to spec |
| Make a decision in a meeting but don't log it | Add it to decisions.md immediately |
| Create a new document to capture a decision | Add to existing decisions register |
| Duplicate architecture facts in multiple documents | Reference the Architecture Reference; don't copy |
| Answer an open question without recording it | Record answer in Open Questions → create decision if applicable |
This page defines the information flow. The Architecture Reference is the canonical source of truth.