From 59b3aa14ad2402dac1ccbf9a5d66341b4c0c6b58 Mon Sep 17 00:00:00 2001 From: KoCoder Date: Fri, 27 Feb 2026 10:49:39 +0100 Subject: [PATCH] vault backup: 2026-02-27 10:49:39 --- Test/.obsidian/graph.json | 2 +- Test/.obsidian/workspace.json | 72 ++++++++++--------- ...ystem Overview.md => 00-SystemOverview.md} | 32 ++++----- ...anagement.md => 01-InventoryManagement.md} | 12 ++-- ...lanning Module.md => 02-PlanningModule.md} | 12 ++-- .../{03 - CRM Module.md => 03-CRMModule.md} | 10 +-- ...ecture.md => 04-FederationArchitecture.md} | 10 +-- ...Scanning.md => 05-BarcodeAndQRScanning.md} | 18 ++--- ...Integration.md => 06-ModuleIntegration.md} | 14 ++-- ...rements.md => 07-TechnicalRequirements.md} | 18 ++--- ... Open Questions.md => 08-OpenQuestions.md} | 18 ++--- .../00-DiscoveryQuestions.md | 8 +-- .../01-DiscoveryQuestions.md | 6 +- .../02-DiscoveryQuestions.md | 4 +- .../03-DiscoveryQuestions.md | 2 +- .../04-DiscoveryQuestions.md | 2 +- 16 files changed, 123 insertions(+), 117 deletions(-) rename Test/EventKit/{00 - System Overview.md => 00-SystemOverview.md} (70%) rename Test/EventKit/{01 - Inventory Management.md => 01-InventoryManagement.md} (97%) rename Test/EventKit/{02 - Planning Module.md => 02-PlanningModule.md} (95%) rename Test/EventKit/{03 - CRM Module.md => 03-CRMModule.md} (96%) rename Test/EventKit/{04 - Federation Architecture.md => 04-FederationArchitecture.md} (97%) rename Test/EventKit/{05 - Barcode and QR Scanning.md => 05-BarcodeAndQRScanning.md} (92%) rename Test/EventKit/{06 - Module Integration.md => 06-ModuleIntegration.md} (93%) rename Test/EventKit/{07 - Technical Requirements.md => 07-TechnicalRequirements.md} (97%) rename Test/EventKit/{08 - Open Questions.md => 08-OpenQuestions.md} (93%) diff --git a/Test/.obsidian/graph.json b/Test/.obsidian/graph.json index c3ea451..d127921 100644 --- a/Test/.obsidian/graph.json +++ b/Test/.obsidian/graph.json @@ -17,6 +17,6 @@ "repelStrength": 10, "linkStrength": 1, "linkDistance": 250, - "scale": 2.25, + "scale": 1.0534979423868311, "close": true } \ No newline at end of file diff --git a/Test/.obsidian/workspace.json b/Test/.obsidian/workspace.json index be0918d..7acaabc 100644 --- a/Test/.obsidian/workspace.json +++ b/Test/.obsidian/workspace.json @@ -4,21 +4,17 @@ "type": "split", "children": [ { - "id": "97bacbca08721c89", + "id": "12559bba3106108e", "type": "tabs", "children": [ { - "id": "33bf02b914739c8c", + "id": "3910a27b25400383", "type": "leaf", "state": { - "type": "markdown", - "state": { - "file": "EventKit/09 - Discovery Questions.md", - "mode": "source", - "source": false - }, - "icon": "lucide-file", - "title": "09 - Discovery Questions" + "type": "graph", + "state": {}, + "icon": "lucide-git-fork", + "title": "Graph view" } } ] @@ -53,7 +49,7 @@ "state": { "type": "search", "state": { - "query": "tag:#eventkit", + "query": "", "matchingCase": false, "explainSearch": false, "collapseAll": false, @@ -94,7 +90,6 @@ "state": { "type": "backlink", "state": { - "file": "EventKit/09 - Discovery Questions.md", "collapseAll": false, "extraContext": false, "sortOrder": "alphabetical", @@ -104,7 +99,7 @@ "unlinkedCollapsed": true }, "icon": "links-coming-in", - "title": "Backlinks for 09 - Discovery Questions" + "title": "Backlinks" } }, { @@ -113,12 +108,11 @@ "state": { "type": "outgoing-link", "state": { - "file": "Welcome.md", "linksCollapsed": false, "unlinkedCollapsed": true }, "icon": "links-going-out", - "title": "Outgoing links from Welcome" + "title": "Outgoing links" } }, { @@ -156,13 +150,12 @@ "state": { "type": "outline", "state": { - "file": "EventKit/09 - Discovery Questions.md", "followCursor": false, "showSearch": false, "searchQuery": "" }, "icon": "lucide-list", - "title": "Outline of 09 - Discovery Questions" + "title": "Outline" } }, { @@ -180,7 +173,7 @@ } ], "direction": "horizontal", - "width": 458.5 + "width": 370.5 }, "left-ribbon": { "hiddenItems": { @@ -194,25 +187,38 @@ "obsidian-git:Open Git source control": false } }, - "active": "33bf02b914739c8c", + "active": "3910a27b25400383", "lastOpenFiles": [ - "EventKit/00 - System Overview.md", + "EventKit/08-OpenQuestions.md", + "EventKit/07-TechnicalRequirements.md", + "EventKit/06-ModuleIntegration.md", + "EventKit/05-BarcodeAndQRScanning.md", + "EventKit/04-FederationArchitecture.md", + "EventKit/03-CRMModule.md", + "EventKit/02-PlanningModule.md", + "EventKit/01-InventoryManagement.md", + "EventKit/00-SystemOverview.md", + "12-DiscoveryQuestionsRound4.md", + "EventKit/DiscoveryQuestions/04-DiscoveryQuestions.md", + "EventKit/DiscoveryQuestions/03-DiscoveryQuestions.md", + "EventKit/DiscoveryQuestions/02-DiscoveryQuestions.md", + "EventKit/DiscoveryQuestions/01-DiscoveryQuestions.md", + "EventKit/DiscoveryQuestions/00-DiscoveryQuestions.md", + "EventKit/DiscoveryQuestions/13-DiscoveryQuestionsRound5.md", + "EventKit/DiscoveryQuestions/12-DiscoveryQuestionsRound4.md", + "EventKit/DiscoveryQuestions/11-DiscoveryQuestionsRound3.md", + "EventKit/DiscoveryQuestions/10-DiscoveryQuestionsRound2.md", + "EventKit/DiscoveryQuestions/09-DiscoveryQuestions.md", + "EventKit/13 - Discovery Questions Round 5.md", + "EventKit/DiscoveryQuestions", + "EventKit/12 - Discovery Questions Round 4.md", + "EventKit/11 - Discovery Questions Round 3.md", + "EventKit/10 - Discovery Questions Round 2.md", "EventKit/09 - Discovery Questions.md", - "EventKit/08 - Open Questions.md", - "EventKit/04 - Federation Architecture.md", - "EventKit/03 - CRM Module.md", - "EventKit/02 - Planning Module.md", - "EventKit/01 - Inventory Management.md", - "create a link.md", - "Welcome.md", "Untitled 1.base", - "Untitled.base", - "Inventory Management Tool.md", - "EventKit/07 - Technical Requirements.md", - "EventKit/06 - Module Integration.md", - "EventKit/05 - Barcode and QR Scanning.md", - "Test/Test.md", + "EventKit/08 - Open Questions.md", "EventKit", + "Untitled.base", "Untitled.canvas", "Test" ] diff --git a/Test/EventKit/00 - System Overview.md b/Test/EventKit/00-SystemOverview.md similarity index 70% rename from Test/EventKit/00 - System Overview.md rename to Test/EventKit/00-SystemOverview.md index 934a31c..dcad059 100644 --- a/Test/EventKit/00 - System Overview.md +++ b/Test/EventKit/00-SystemOverview.md @@ -7,7 +7,7 @@ tags: ## Vision -EventKit is a **decentralised, [[04 - Federation Architecture|federated]]** [[01 - Inventory Management|inventory management]], [[02 - Planning Module|planning]], and [[03 - CRM Module|CRM]] platform purpose-built for the **event industry**. Each company hosts its own instance with full data sovereignty, while optional federation enables cross-company workflows like sub-hire tracking, equipment sharing, and inter-company asset visibility. +EventKit is a **decentralised, [[04-FederationArchitecture|federated]]** [[01-InventoryManagement|inventory management]], [[02-PlanningModule|planning]], and [[03-CRMModule|CRM]] platform purpose-built for the **event industry**. Each company hosts its own instance with full data sovereignty, while optional federation enables cross-company workflows like sub-hire tracking, equipment sharing, and inter-company asset visibility. ### Business Model @@ -43,22 +43,22 @@ EventKit is a **decentralised, [[04 - Federation Architecture|federated]]** [[01 Not a generic inventory tool — built around the realities of event production: - Equipment goes **out and comes back** (rental cycle, not linear supply chain) -- Assets live in **[[01 - Inventory Management#Cases & Packing|flight cases]]** and move between **warehouses and venues** -- Everything is driven by **[[02 - Planning Module|event dates and schedules]]** -- **[[01 - Inventory Management#Sub-hire Management|Sub-hire]]** between companies is a first-class workflow +- Assets live in **[[01-InventoryManagement#Cases & Packing|flight cases]]** and move between **warehouses and venues** +- Everything is driven by **[[02-PlanningModule|event dates and schedules]]** +- **[[01-InventoryManagement#Sub-hire Management|Sub-hire]]** between companies is a first-class workflow ### 2. Decentralised / Federated - Every company runs their **own instance** with full control over their data -- Instances can **[[04 - Federation Architecture|federate]]** with trusted partners for cross-company workflows +- Instances can **[[04-FederationArchitecture|federate]]** with trusted partners for cross-company workflows - No central authority or vendor lock-in -- Equipment can be **[[04 - Federation Architecture#Global Asset Identity|tracked across company boundaries]]** via federation +- Equipment can be **[[04-FederationArchitecture#Global Asset Identity|tracked across company boundaries]]** via federation ### 3. Barcode / QR Code Scanning -- Every asset, case, and warehouse location gets a **[[05 - Barcode and QR Scanning#QR Code Design|scannable QR code]]** +- Every asset, case, and warehouse location gets a **[[05-BarcodeAndQRScanning#QR Code Design|scannable QR code]]** - QR codes encode a **URL** — works with any phone camera or dedicated scanner -- Scanning powers [[05 - Barcode and QR Scanning#Scanning Workflows|workflows]]: check-out, check-in, stocktake, case packing, sub-hire receive/return +- Scanning powers [[05-BarcodeAndQRScanning#Scanning Workflows|workflows]]: check-out, check-in, stocktake, case packing, sub-hire receive/return --- @@ -125,11 +125,11 @@ graph LR ## Related Documentation -- [[01 - Inventory Management]] — Equipment, cases, locations, maintenance -- [[02 - Planning Module]] — Events, crew, transport, scheduling -- [[03 - CRM Module]] — Clients, pipeline, quotes -- [[04 - Federation Architecture]] — Decentralised design & protocol -- [[05 - Barcode and QR Scanning]] — Scanning workflows & label design -- [[06 - Module Integration]] — Cross-module flows -- [[07 - Technical Requirements]] — Non-functional requirements -- [[08 - Open Questions]] — Remaining decisions +- [[01-InventoryManagement]] — Equipment, cases, locations, maintenance +- [[02-PlanningModule]] — Events, crew, transport, scheduling +- [[03-CRMModule]] — Clients, pipeline, quotes +- [[04-FederationArchitecture]] — Decentralised design & protocol +- [[05-BarcodeAndQRScanning]] — Scanning workflows & label design +- [[06-ModuleIntegration]] — Cross-module flows +- [[07-TechnicalRequirements]] — Non-functional requirements +- [[08-OpenQuestions]] — Remaining decisions diff --git a/Test/EventKit/01 - Inventory Management.md b/Test/EventKit/01-InventoryManagement.md similarity index 97% rename from Test/EventKit/01 - Inventory Management.md rename to Test/EventKit/01-InventoryManagement.md index 89a1496..beb4875 100644 --- a/Test/EventKit/01 - Inventory Management.md +++ b/Test/EventKit/01-InventoryManagement.md @@ -7,7 +7,7 @@ tags: ## Purpose -Track and manage all physical equipment assets throughout their lifecycle — from procurement through daily rental operations to maintenance and retirement. Specialised for the event industry's unique needs: equipment goes out to [[02 - Planning Module|events]], gets used, and comes back. +Track and manage all physical equipment assets throughout their lifecycle — from procurement through daily rental operations to maintenance and retirement. Specialised for the event industry's unique needs: equipment goes out to [[02-PlanningModule|events]], gets used, and comes back. --- @@ -141,7 +141,7 @@ stateDiagram-v2 | ------------------------ | --------------------------------------------------------------------------------------------------------- | | Outbound sub-hire | Track equipment lent to other companies | | Inbound sub-hire | Track equipment borrowed from others | -| Federated sub-hire | When both companies use EventKit, track the asset across instances (see [[04 - Federation Architecture]]) | +| Federated sub-hire | When both companies use EventKit, track the asset across instances (see [[04-FederationArchitecture]]) | | Sub-hire rates & costs | Track day rates, insurance charges, cross-charges | | Return deadline tracking | Alerts for overdue sub-hire returns | | Condition tracking | Record condition at dispatch and return for dispute resolution | @@ -225,7 +225,7 @@ Detailed return inspection workflow: ## Related Documentation -- [[00 - System Overview]] — High-level system overview -- [[02 - Planning Module]] — Event planning and pull lists consume inventory data -- [[05 - Barcode and QR Scanning]] — Scanning workflows for check-in/out -- [[04 - Federation Architecture]] — Cross-company asset tracking +- [[00-SystemOverview]] — High-level system overview +- [[02-PlanningModule]] — Event planning and pull lists consume inventory data +- [[05-BarcodeAndQRScanning]] — Scanning workflows for check-in/out +- [[04-FederationArchitecture]] — Cross-company asset tracking diff --git a/Test/EventKit/02 - Planning Module.md b/Test/EventKit/02-PlanningModule.md similarity index 95% rename from Test/EventKit/02 - Planning Module.md rename to Test/EventKit/02-PlanningModule.md index 286e8c4..81bf34c 100644 --- a/Test/EventKit/02 - Planning Module.md +++ b/Test/EventKit/02-PlanningModule.md @@ -7,7 +7,7 @@ tags: ## Purpose -Manage the full lifecycle of events — from initial [[03 - CRM Module|enquiry]] through on-site execution to post-event close-out. Co-ordinates [[01 - Inventory Management|equipment]], crew, transport, and venue logistics into a single operational view. +Manage the full lifecycle of events — from initial [[03-CRMModule|enquiry]] through on-site execution to post-event close-out. Co-ordinates [[01-InventoryManagement|equipment]], crew, transport, and venue logistics into a single operational view. --- @@ -168,7 +168,7 @@ Crew members can log in (web or mobile app) to: | Blackout dates | Track dates when a venue is unavailable | | Venue history | See all past events at a venue with notes | -> **Venue federation** is planned but will start as local-only. In a future phase, instances will be able to share venue specs across the network via [[04 - Federation Architecture|federation]]. +> **Venue federation** is planned but will start as local-only. In a future phase, instances will be able to share venue specs across the network via [[04-FederationArchitecture|federation]]. ### Calendar Integration @@ -215,7 +215,7 @@ Crew members can log in (web or mobile app) to: ## Related Documentation -- [[00 - System Overview]] — High-level system overview -- [[01 - Inventory Management]] — Equipment data consumed by pull lists -- [[03 - CRM Module]] — Client data and pipeline feed into event creation -- [[06 - Module Integration]] — How planning connects to inventory and CRM +- [[00-SystemOverview]] — High-level system overview +- [[01-InventoryManagement]] — Equipment data consumed by pull lists +- [[03-CRMModule]] — Client data and pipeline feed into event creation +- [[06-ModuleIntegration]] — How planning connects to inventory and CRM diff --git a/Test/EventKit/03 - CRM Module.md b/Test/EventKit/03-CRMModule.md similarity index 96% rename from Test/EventKit/03 - CRM Module.md rename to Test/EventKit/03-CRMModule.md index 245c70a..98e3d92 100644 --- a/Test/EventKit/03 - CRM Module.md +++ b/Test/EventKit/03-CRMModule.md @@ -7,7 +7,7 @@ tags: ## Purpose -Manage client relationships, sales pipeline, quoting, and communication for event companies. Tightly integrated with the [[02 - Planning Module]] (won deals become events) and [[01 - Inventory Management]] (quotes reference real equipment and pricing). +Manage client relationships, sales pipeline, quoting, and communication for event companies. Tightly integrated with the [[02-PlanningModule]] (won deals become events) and [[01-InventoryManagement]] (quotes reference real equipment and pricing). --- @@ -199,7 +199,7 @@ Import from other systems is an optional future feature. Supported sources: ## Related Documentation -- [[00 - System Overview]] — High-level system overview -- [[02 - Planning Module]] — Won deals become events -- [[01 - Inventory Management]] — Quotes reference equipment catalogue -- [[06 - Module Integration]] — CRM ↔ Planning ↔ Inventory flows +- [[00-SystemOverview]] — High-level system overview +- [[02-PlanningModule]] — Won deals become events +- [[01-InventoryManagement]] — Quotes reference equipment catalogue +- [[06-ModuleIntegration]] — CRM ↔ Planning ↔ Inventory flows diff --git a/Test/EventKit/04 - Federation Architecture.md b/Test/EventKit/04-FederationArchitecture.md similarity index 97% rename from Test/EventKit/04 - Federation Architecture.md rename to Test/EventKit/04-FederationArchitecture.md index 500d63b..6173b79 100644 --- a/Test/EventKit/04 - Federation Architecture.md +++ b/Test/EventKit/04-FederationArchitecture.md @@ -7,7 +7,7 @@ tags: ## Purpose -Enable multiple EventKit instances to communicate securely, allowing cross-company workflows like [[01 - Inventory Management#Sub-hire Management|sub-hire tracking]], equipment availability queries, and cross-boundary [[05 - Barcode and QR Scanning|asset tracking]] — while each company retains full sovereignty over their own data. +Enable multiple EventKit instances to communicate securely, allowing cross-company workflows like [[01-InventoryManagement#Sub-hire Management|sub-hire tracking]], equipment availability queries, and cross-boundary [[05-BarcodeAndQRScanning|asset tracking]] — while each company retains full sovereignty over their own data. --- @@ -447,7 +447,7 @@ message FederationEvent { ## Related Documentation -- [[00 - System Overview]] — High-level system overview -- [[01 - Inventory Management]] — Asset data that gets federated -- [[05 - Barcode and QR Scanning]] — Scanning federated assets -- [[07 - Technical Requirements]] — Deployment and security considerations +- [[00-SystemOverview]] — High-level system overview +- [[01-InventoryManagement]] — Asset data that gets federated +- [[05-BarcodeAndQRScanning]] — Scanning federated assets +- [[07-TechnicalRequirements]] — Deployment and security considerations diff --git a/Test/EventKit/05 - Barcode and QR Scanning.md b/Test/EventKit/05-BarcodeAndQRScanning.md similarity index 92% rename from Test/EventKit/05 - Barcode and QR Scanning.md rename to Test/EventKit/05-BarcodeAndQRScanning.md index fef9948..ee59242 100644 --- a/Test/EventKit/05 - Barcode and QR Scanning.md +++ b/Test/EventKit/05-BarcodeAndQRScanning.md @@ -7,7 +7,7 @@ tags: ## Purpose -Enable fast, accurate equipment tracking through QR code scanning. Every [[01 - Inventory Management|asset]], [[01 - Inventory Management#Cases & Packing|case]], and [[01 - Inventory Management#Warehouse & Locations|warehouse location]] gets a scannable code, powering workflows from check-out to stocktake to cross-company [[01 - Inventory Management#Sub-hire Management|sub-hire]]. +Enable fast, accurate equipment tracking through QR code scanning. Every [[01-InventoryManagement|asset]], [[01-InventoryManagement#Cases & Packing|case]], and [[01-InventoryManagement#Warehouse & Locations|warehouse location]] gets a scannable code, powering workflows from check-out to stocktake to cross-company [[01-InventoryManagement#Sub-hire Management|sub-hire]]. --- @@ -229,11 +229,11 @@ sequenceDiagram Scan any QR code outside of a workflow to instantly see: - Asset/case details (model, serial, owner) -- Current status ([[01 - Inventory Management#Asset Lifecycle & Statuses|available, checked out, in repair]], etc.) -- Current [[01 - Inventory Management#Warehouse & Locations|location]] -- Current [[02 - Planning Module|event]] assignment (if any) +- Current status ([[01-InventoryManagement#Asset Lifecycle & Statuses|available, checked out, in repair]], etc.) +- Current [[01-InventoryManagement#Warehouse & Locations|location]] +- Current [[02-PlanningModule|event]] assignment (if any) - Condition notes -- [[01 - Inventory Management#Maintenance & Testing|Maintenance]] due dates +- [[01-InventoryManagement#Maintenance & Testing|Maintenance]] due dates --- @@ -275,7 +275,7 @@ Scan any QR code outside of a workflow to instantly see: ## Related Documentation -- [[00 - System Overview]] — High-level system overview -- [[01 - Inventory Management]] — Assets and cases that get scanned -- [[04 - Federation Architecture]] — Scanning federated assets -- [[07 - Technical Requirements]] — Hardware and deployment considerations +- [[00-SystemOverview]] — High-level system overview +- [[01-InventoryManagement]] — Assets and cases that get scanned +- [[04-FederationArchitecture]] — Scanning federated assets +- [[07-TechnicalRequirements]] — Hardware and deployment considerations diff --git a/Test/EventKit/06 - Module Integration.md b/Test/EventKit/06-ModuleIntegration.md similarity index 93% rename from Test/EventKit/06 - Module Integration.md rename to Test/EventKit/06-ModuleIntegration.md index 5fa7cdf..2176cf5 100644 --- a/Test/EventKit/06 - Module Integration.md +++ b/Test/EventKit/06-ModuleIntegration.md @@ -7,7 +7,7 @@ tags: ## Purpose -This document describes how the three core modules ([[01 - Inventory Management|Inventory]], [[02 - Planning Module|Planning]], [[03 - CRM Module|CRM]]) work together, including the key cross-module workflows and the unified features that span all modules. +This document describes how the three core modules ([[01-InventoryManagement|Inventory]], [[02-PlanningModule|Planning]], [[03-CRMModule|CRM]]) work together, including the key cross-module workflows and the unified features that span all modules. --- @@ -177,9 +177,9 @@ A cross-module activity stream showing: ## Related Documentation -- [[00 - System Overview]] — High-level system overview -- [[01 - Inventory Management]] — Equipment and availability -- [[02 - Planning Module]] — Events and scheduling -- [[03 - CRM Module]] — Clients and pipeline -- [[04 - Federation Architecture]] — Cross-company flows -- [[05 - Barcode and QR Scanning]] — Scanning workflows powering check-in/out +- [[00-SystemOverview]] — High-level system overview +- [[01-InventoryManagement]] — Equipment and availability +- [[02-PlanningModule]] — Events and scheduling +- [[03-CRMModule]] — Clients and pipeline +- [[04-FederationArchitecture]] — Cross-company flows +- [[05-BarcodeAndQRScanning]] — Scanning workflows powering check-in/out diff --git a/Test/EventKit/07 - Technical Requirements.md b/Test/EventKit/07-TechnicalRequirements.md similarity index 97% rename from Test/EventKit/07 - Technical Requirements.md rename to Test/EventKit/07-TechnicalRequirements.md index fdfb367..ac43852 100644 --- a/Test/EventKit/07 - Technical Requirements.md +++ b/Test/EventKit/07-TechnicalRequirements.md @@ -40,7 +40,7 @@ Non-functional requirements, deployment model, API design, and infrastructure co This means: - **Web browsers** call the same API using the Connect protocol (plain HTTP + JSON or Protobuf) — no Envoy proxy required -- **[[04 - Federation Architecture|Federation]]** between instances uses gRPC for efficient binary communication +- **[[04-FederationArchitecture|Federation]]** between instances uses gRPC for efficient binary communication - **Mobile apps** can use gRPC natively - **One `.proto` definition** generates server code (Go), browser client (TypeScript), and mobile client code @@ -540,11 +540,11 @@ All major entity changes trigger outbound webhooks: ## Related Documentation -- [[00 - System Overview]] — High-level system overview -- [[01 - Inventory Management]] — Inventory module served by `InventoryService` -- [[02 - Planning Module]] — Planning module served by `PlanningService` -- [[03 - CRM Module]] — CRM module served by `CRMService` and `QuoteService` -- [[04 - Federation Architecture]] — Federation deployment and security -- [[05 - Barcode and QR Scanning]] — Hardware requirements and `ScanningService` -- [[06 - Module Integration]] — Cross-module workflows -- [[08 - Open Questions]] — Remaining technical decisions +- [[00-SystemOverview]] — High-level system overview +- [[01-InventoryManagement]] — Inventory module served by `InventoryService` +- [[02-PlanningModule]] — Planning module served by `PlanningService` +- [[03-CRMModule]] — CRM module served by `CRMService` and `QuoteService` +- [[04-FederationArchitecture]] — Federation deployment and security +- [[05-BarcodeAndQRScanning]] — Hardware requirements and `ScanningService` +- [[06-ModuleIntegration]] — Cross-module workflows +- [[08-OpenQuestions]] — Remaining technical decisions diff --git a/Test/EventKit/08 - Open Questions.md b/Test/EventKit/08-OpenQuestions.md similarity index 93% rename from Test/EventKit/08 - Open Questions.md rename to Test/EventKit/08-OpenQuestions.md index e7901d9..51c6837 100644 --- a/Test/EventKit/08 - Open Questions.md +++ b/Test/EventKit/08-OpenQuestions.md @@ -7,7 +7,7 @@ tags: ## Purpose -Remaining decisions and questions that need answers before or during implementation. Organised by topic area. See [[07 - Technical Requirements]] for decisions already made. +Remaining decisions and questions that need answers before or during implementation. Organised by topic area. See [[07-TechnicalRequirements]] for decisions already made. --- @@ -91,13 +91,13 @@ All 30 questions have been answered. ✅ ## Related Documentation -- [[00 - System Overview]] — High-level system overview -- [[01 - Inventory Management]] — Inventory module design -- [[02 - Planning Module]] — Planning module design -- [[03 - CRM Module]] — CRM module design -- [[04 - Federation Architecture]] — Federation protocol design -- [[05 - Barcode and QR Scanning]] — Scanning and hardware -- [[06 - Module Integration]] — Cross-module workflows -- [[07 - Technical Requirements]] — Technical decisions made and remaining +- [[00-SystemOverview]] — High-level system overview +- [[01-InventoryManagement]] — Inventory module design +- [[02-PlanningModule]] — Planning module design +- [[03-CRMModule]] — CRM module design +- [[04-FederationArchitecture]] — Federation protocol design +- [[05-BarcodeAndQRScanning]] — Scanning and hardware +- [[06-ModuleIntegration]] — Cross-module workflows +- [[07-TechnicalRequirements]] — Technical decisions made and remaining - [[00-DiscoveryQuestions]] — Round 1 answers - [[01-DiscoveryQuestions]] — Round 2 answers diff --git a/Test/EventKit/DiscoveryQuestions/00-DiscoveryQuestions.md b/Test/EventKit/DiscoveryQuestions/00-DiscoveryQuestions.md index 2a098c0..4d7625c 100644 --- a/Test/EventKit/DiscoveryQuestions/00-DiscoveryQuestions.md +++ b/Test/EventKit/DiscoveryQuestions/00-DiscoveryQuestions.md @@ -6,7 +6,7 @@ tags: # Discovery Questions -Fill in your answers below each question. These will feed back into the existing documentation — see [[08 - Open Questions]] for the current list of unresolved items. +Fill in your answers below each question. These will feed back into the existing documentation — see [[08-OpenQuestions]] for the current list of unresolved items. --- @@ -144,6 +144,6 @@ Email only, or also push notifications, SMS, Slack/Teams webhooks? ## Related Documentation -- [[00 - System Overview]] — High-level system overview -- [[08 - Open Questions]] — Existing open questions list -- [[07 - Technical Requirements]] — Technical decisions already made +- [[00-SystemOverview]] — High-level system overview +- [[08-OpenQuestions]] — Existing open questions list +- [[07-TechnicalRequirements]] — Technical decisions already made diff --git a/Test/EventKit/DiscoveryQuestions/01-DiscoveryQuestions.md b/Test/EventKit/DiscoveryQuestions/01-DiscoveryQuestions.md index 688dacb..0d1f375 100644 --- a/Test/EventKit/DiscoveryQuestions/01-DiscoveryQuestions.md +++ b/Test/EventKit/DiscoveryQuestions/01-DiscoveryQuestions.md @@ -6,7 +6,7 @@ tags: # Discovery Questions — Round 2 -Deeper questions building on your earlier answers. These target the remaining open items from [[08 - Open Questions]] and drill into implementation details. +Deeper questions building on your earlier answers. These target the remaining open items from [[08-OpenQuestions]] and drill into implementation details. --- @@ -238,6 +238,6 @@ Should dark mode be supported? ## Related Documentation -- [[08 - Open Questions]] — Tracks which questions are still open +- [[08-OpenQuestions]] — Tracks which questions are still open - [[00-DiscoveryQuestions]] — Round 1 answers -- [[07 - Technical Requirements]] — Decisions already made +- [[07-TechnicalRequirements]] — Decisions already made diff --git a/Test/EventKit/DiscoveryQuestions/02-DiscoveryQuestions.md b/Test/EventKit/DiscoveryQuestions/02-DiscoveryQuestions.md index 59aa8b6..6dc22ff 100644 --- a/Test/EventKit/DiscoveryQuestions/02-DiscoveryQuestions.md +++ b/Test/EventKit/DiscoveryQuestions/02-DiscoveryQuestions.md @@ -246,7 +246,7 @@ Should API keys be scoped to specific permissions/modules? ## Related Documentation -- [[08 - Open Questions]] — All 30 original questions now answered +- [[08-OpenQuestions]] — All 30 original questions now answered - [[00-DiscoveryQuestions]] — Round 1 answers - [[01-DiscoveryQuestions]] — Round 2 answers -- [[07 - Technical Requirements]] — Technical decisions made +- [[07-TechnicalRequirements]] — Technical decisions made diff --git a/Test/EventKit/DiscoveryQuestions/03-DiscoveryQuestions.md b/Test/EventKit/DiscoveryQuestions/03-DiscoveryQuestions.md index 01148ee..54f2350 100644 --- a/Test/EventKit/DiscoveryQuestions/03-DiscoveryQuestions.md +++ b/Test/EventKit/DiscoveryQuestions/03-DiscoveryQuestions.md @@ -251,4 +251,4 @@ Should there be a formal staging/preview environment? - [[00-DiscoveryQuestions]] — Round 1 answers - [[01-DiscoveryQuestions]] — Round 2 answers - [[02-DiscoveryQuestions]] — Round 3 answers -- [[07 - Technical Requirements]] — Technical decisions made +- [[07-TechnicalRequirements]] — Technical decisions made diff --git a/Test/EventKit/DiscoveryQuestions/04-DiscoveryQuestions.md b/Test/EventKit/DiscoveryQuestions/04-DiscoveryQuestions.md index c033b3f..2ecac2f 100644 --- a/Test/EventKit/DiscoveryQuestions/04-DiscoveryQuestions.md +++ b/Test/EventKit/DiscoveryQuestions/04-DiscoveryQuestions.md @@ -213,4 +213,4 @@ Beyond Cmd+K, should there be keyboard shortcuts for common actions? - [[01-DiscoveryQuestions]] — Round 2 answers - [[02-DiscoveryQuestions]] — Round 3 answers - [[03-DiscoveryQuestions]] — Round 4 answers -- [[07 - Technical Requirements]] — Technical decisions made +- [[07-TechnicalRequirements]] — Technical decisions made