Kocoder/obsidian
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2026-02-27 10:49:39

Browse Source
This commit is contained in:
Konstantin Hintermayer
2026-02-27 10:49:39 +01:00
parent dcfaa481bd
commit 59b3aa14ad
16 changed files with 123 additions and 117 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Test/.obsidian/graph.json vendored
View File

@@ -17,6 +17,6 @@
"repelStrength": 10, "repelStrength": 10,
"linkStrength": 1, "linkStrength": 1,
"linkDistance": 250, "linkDistance": 250,
"scale": 2.25, "scale": 1.0534979423868311,
"close": true "close": true
} }

72
Test/.obsidian/workspace.json vendored
View File

@@ -4,21 +4,17 @@
"type": "split", "type": "split",
"children": [ "children": [
{ {
"id": "97bacbca08721c89", "id": "12559bba3106108e",
"type": "tabs", "type": "tabs",
"children": [ "children": [
{ {
"id": "33bf02b914739c8c", "id": "3910a27b25400383",
"type": "leaf", "type": "leaf",
"state": { "state": {
"type": "markdown", "type": "graph",
"state": { "state": {},
"file": "EventKit/09 - Discovery Questions.md", "icon": "lucide-git-fork",
"mode": "source", "title": "Graph view"
"source": false
},
"icon": "lucide-file",
"title": "09 - Discovery Questions"
} }
} }
] ]
@@ -53,7 +49,7 @@
"state": { "state": {
"type": "search", "type": "search",
"state": { "state": {
"query": "tag:#eventkit", "query": "",
"matchingCase": false, "matchingCase": false,
"explainSearch": false, "explainSearch": false,
"collapseAll": false, "collapseAll": false,
@@ -94,7 +90,6 @@
"state": { "state": {
"type": "backlink", "type": "backlink",
"state": { "state": {
"file": "EventKit/09 - Discovery Questions.md",
"collapseAll": false, "collapseAll": false,
"extraContext": false, "extraContext": false,
"sortOrder": "alphabetical", "sortOrder": "alphabetical",
@@ -104,7 +99,7 @@
"unlinkedCollapsed": true "unlinkedCollapsed": true
}, },
"icon": "links-coming-in", "icon": "links-coming-in",
"title": "Backlinks for 09 - Discovery Questions" "title": "Backlinks"
} }
}, },
{ {
@@ -113,12 +108,11 @@
"state": { "state": {
"type": "outgoing-link", "type": "outgoing-link",
"state": { "state": {
"file": "Welcome.md",
"linksCollapsed": false, "linksCollapsed": false,
"unlinkedCollapsed": true "unlinkedCollapsed": true
}, },
"icon": "links-going-out", "icon": "links-going-out",
"title": "Outgoing links from Welcome" "title": "Outgoing links"
} }
}, },
{ {
@@ -156,13 +150,12 @@
"state": { "state": {
"type": "outline", "type": "outline",
"state": { "state": {
"file": "EventKit/09 - Discovery Questions.md",
"followCursor": false, "followCursor": false,
"showSearch": false, "showSearch": false,
"searchQuery": "" "searchQuery": ""
}, },
"icon": "lucide-list", "icon": "lucide-list",
"title": "Outline of 09 - Discovery Questions" "title": "Outline"
} }
}, },
{ {
@@ -180,7 +173,7 @@
} }
], ],
"direction": "horizontal", "direction": "horizontal",
"width": 458.5 "width": 370.5
}, },
"left-ribbon": { "left-ribbon": {
"hiddenItems": { "hiddenItems": {
@@ -194,25 +187,38 @@
"obsidian-git:Open Git source control": false "obsidian-git:Open Git source control": false
} }
}, },
"active": "33bf02b914739c8c", "active": "3910a27b25400383",
"lastOpenFiles": [ "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/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 1.base",
"Untitled.base", "EventKit/08 - Open Questions.md",
"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", "EventKit",
"Untitled.base",
"Untitled.canvas", "Untitled.canvas",
"Test" "Test"
] ]

32
Test/EventKit/00 - System Overview.md → Test/EventKit/00-SystemOverview.md
View File

@@ -7,7 +7,7 @@ tags:
## Vision ## 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 ### 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: Not a generic inventory tool — built around the realities of event production:
- Equipment goes **out and comes back** (rental cycle, not linear supply chain) - 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** - Assets live in **[[01-InventoryManagement#Cases & Packing|flight cases]]** and move between **warehouses and venues**
- Everything is driven by **[[02 - Planning Module|event dates and schedules]]** - Everything is driven by **[[02-PlanningModule|event dates and schedules]]**
- **[[01 - Inventory Management#Sub-hire Management|Sub-hire]]** between companies is a first-class workflow - **[[01-InventoryManagement#Sub-hire Management|Sub-hire]]** between companies is a first-class workflow
### 2. Decentralised / Federated ### 2. Decentralised / Federated
- Every company runs their **own instance** with full control over their data - 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 - 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 ### 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 - 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 ## Related Documentation
- [[01 - Inventory Management]] — Equipment, cases, locations, maintenance - [[01-InventoryManagement]] — Equipment, cases, locations, maintenance
- [[02 - Planning Module]] — Events, crew, transport, scheduling - [[02-PlanningModule]] — Events, crew, transport, scheduling
- [[03 - CRM Module]] — Clients, pipeline, quotes - [[03-CRMModule]] — Clients, pipeline, quotes
- [[04 - Federation Architecture]] — Decentralised design & protocol - [[04-FederationArchitecture]] — Decentralised design & protocol
- [[05 - Barcode and QR Scanning]] — Scanning workflows & label design - [[05-BarcodeAndQRScanning]] — Scanning workflows & label design
- [[06 - Module Integration]] — Cross-module flows - [[06-ModuleIntegration]] — Cross-module flows
- [[07 - Technical Requirements]] — Non-functional requirements - [[07-TechnicalRequirements]] — Non-functional requirements
- [[08 - Open Questions]] — Remaining decisions - [[08-OpenQuestions]] — Remaining decisions

12
Test/EventKit/01 - Inventory Management.md → Test/EventKit/01-InventoryManagement.md
View File

@@ -7,7 +7,7 @@ tags:
## Purpose ## 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 | | Outbound sub-hire | Track equipment lent to other companies |
| Inbound sub-hire | Track equipment borrowed from others | | 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 | | Sub-hire rates & costs | Track day rates, insurance charges, cross-charges |
| Return deadline tracking | Alerts for overdue sub-hire returns | | Return deadline tracking | Alerts for overdue sub-hire returns |
| Condition tracking | Record condition at dispatch and return for dispute resolution | | Condition tracking | Record condition at dispatch and return for dispute resolution |
@@ -225,7 +225,7 @@ Detailed return inspection workflow:
## Related Documentation ## Related Documentation
- [[00 - System Overview]] — High-level system overview - [[00-SystemOverview]] — High-level system overview
- [[02 - Planning Module]] — Event planning and pull lists consume inventory data - [[02-PlanningModule]] — Event planning and pull lists consume inventory data
- [[05 - Barcode and QR Scanning]] — Scanning workflows for check-in/out - [[05-BarcodeAndQRScanning]] — Scanning workflows for check-in/out
- [[04 - Federation Architecture]] — Cross-company asset tracking - [[04-FederationArchitecture]] — Cross-company asset tracking

12
Test/EventKit/02 - Planning Module.md → Test/EventKit/02-PlanningModule.md
View File

@@ -7,7 +7,7 @@ tags:
## Purpose ## 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 | | Blackout dates | Track dates when a venue is unavailable |
| Venue history | See all past events at a venue with notes | | 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 ### Calendar Integration
@@ -215,7 +215,7 @@ Crew members can log in (web or mobile app) to:
## Related Documentation ## Related Documentation
- [[00 - System Overview]] — High-level system overview - [[00-SystemOverview]] — High-level system overview
- [[01 - Inventory Management]] — Equipment data consumed by pull lists - [[01-InventoryManagement]] — Equipment data consumed by pull lists
- [[03 - CRM Module]] — Client data and pipeline feed into event creation - [[03-CRMModule]] — Client data and pipeline feed into event creation
- [[06 - Module Integration]] — How planning connects to inventory and CRM - [[06-ModuleIntegration]] — How planning connects to inventory and CRM

10
Test/EventKit/03 - CRM Module.md → Test/EventKit/03-CRMModule.md
View File

@@ -7,7 +7,7 @@ tags:
## Purpose ## 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 ## Related Documentation
- [[00 - System Overview]] — High-level system overview - [[00-SystemOverview]] — High-level system overview
- [[02 - Planning Module]] — Won deals become events - [[02-PlanningModule]] — Won deals become events
- [[01 - Inventory Management]] — Quotes reference equipment catalogue - [[01-InventoryManagement]] — Quotes reference equipment catalogue
- [[06 - Module Integration]] — CRM ↔ Planning ↔ Inventory flows - [[06-ModuleIntegration]] — CRM ↔ Planning ↔ Inventory flows

10
Test/EventKit/04 - Federation Architecture.md → Test/EventKit/04-FederationArchitecture.md
View File

@@ -7,7 +7,7 @@ tags:
## Purpose ## 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 ## Related Documentation
- [[00 - System Overview]] — High-level system overview - [[00-SystemOverview]] — High-level system overview
- [[01 - Inventory Management]] — Asset data that gets federated - [[01-InventoryManagement]] — Asset data that gets federated
- [[05 - Barcode and QR Scanning]] — Scanning federated assets - [[05-BarcodeAndQRScanning]] — Scanning federated assets
- [[07 - Technical Requirements]] — Deployment and security considerations - [[07-TechnicalRequirements]] — Deployment and security considerations

18
Test/EventKit/05 - Barcode and QR Scanning.md → Test/EventKit/05-BarcodeAndQRScanning.md
View File

@@ -7,7 +7,7 @@ tags:
## Purpose ## 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: Scan any QR code outside of a workflow to instantly see:
- Asset/case details (model, serial, owner) - Asset/case details (model, serial, owner)
- Current status ([[01 - Inventory Management#Asset Lifecycle & Statuses|available, checked out, in repair]], etc.) - Current status ([[01-InventoryManagement#Asset Lifecycle & Statuses|available, checked out, in repair]], etc.)
- Current [[01 - Inventory Management#Warehouse & Locations|location]] - Current [[01-InventoryManagement#Warehouse & Locations|location]]
- Current [[02 - Planning Module|event]] assignment (if any) - Current [[02-PlanningModule|event]] assignment (if any)
- Condition notes - 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 ## Related Documentation
- [[00 - System Overview]] — High-level system overview - [[00-SystemOverview]] — High-level system overview
- [[01 - Inventory Management]] — Assets and cases that get scanned - [[01-InventoryManagement]] — Assets and cases that get scanned
- [[04 - Federation Architecture]] — Scanning federated assets - [[04-FederationArchitecture]] — Scanning federated assets
- [[07 - Technical Requirements]] — Hardware and deployment considerations - [[07-TechnicalRequirements]] — Hardware and deployment considerations

14
Test/EventKit/06 - Module Integration.md → Test/EventKit/06-ModuleIntegration.md
View File

@@ -7,7 +7,7 @@ tags:
## Purpose ## 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 ## Related Documentation
- [[00 - System Overview]] — High-level system overview - [[00-SystemOverview]] — High-level system overview
- [[01 - Inventory Management]] — Equipment and availability - [[01-InventoryManagement]] — Equipment and availability
- [[02 - Planning Module]] — Events and scheduling - [[02-PlanningModule]] — Events and scheduling
- [[03 - CRM Module]] — Clients and pipeline - [[03-CRMModule]] — Clients and pipeline
- [[04 - Federation Architecture]] — Cross-company flows - [[04-FederationArchitecture]] — Cross-company flows
- [[05 - Barcode and QR Scanning]] — Scanning workflows powering check-in/out - [[05-BarcodeAndQRScanning]] — Scanning workflows powering check-in/out

18
Test/EventKit/07 - Technical Requirements.md → Test/EventKit/07-TechnicalRequirements.md
View File

@@ -40,7 +40,7 @@ Non-functional requirements, deployment model, API design, and infrastructure co
This means: This means:
- **Web browsers** call the same API using the Connect protocol (plain HTTP + JSON or Protobuf) — no Envoy proxy required - **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 - **Mobile apps** can use gRPC natively
- **One `.proto` definition** generates server code (Go), browser client (TypeScript), and mobile client code - **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 ## Related Documentation
- [[00 - System Overview]] — High-level system overview - [[00-SystemOverview]] — High-level system overview
- [[01 - Inventory Management]] — Inventory module served by `InventoryService` - [[01-InventoryManagement]] — Inventory module served by `InventoryService`
- [[02 - Planning Module]] — Planning module served by `PlanningService` - [[02-PlanningModule]] — Planning module served by `PlanningService`
- [[03 - CRM Module]] — CRM module served by `CRMService` and `QuoteService` - [[03-CRMModule]] — CRM module served by `CRMService` and `QuoteService`
- [[04 - Federation Architecture]] — Federation deployment and security - [[04-FederationArchitecture]] — Federation deployment and security
- [[05 - Barcode and QR Scanning]] — Hardware requirements and `ScanningService` - [[05-BarcodeAndQRScanning]] — Hardware requirements and `ScanningService`
- [[06 - Module Integration]] — Cross-module workflows - [[06-ModuleIntegration]] — Cross-module workflows
- [[08 - Open Questions]] — Remaining technical decisions - [[08-OpenQuestions]] — Remaining technical decisions

18
Test/EventKit/08 - Open Questions.md → Test/EventKit/08-OpenQuestions.md
View File

@@ -7,7 +7,7 @@ tags:
## Purpose ## 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 ## Related Documentation
- [[00 - System Overview]] — High-level system overview - [[00-SystemOverview]] — High-level system overview
- [[01 - Inventory Management]] — Inventory module design - [[01-InventoryManagement]] — Inventory module design
- [[02 - Planning Module]] — Planning module design - [[02-PlanningModule]] — Planning module design
- [[03 - CRM Module]] — CRM module design - [[03-CRMModule]] — CRM module design
- [[04 - Federation Architecture]] — Federation protocol design - [[04-FederationArchitecture]] — Federation protocol design
- [[05 - Barcode and QR Scanning]] — Scanning and hardware - [[05-BarcodeAndQRScanning]] — Scanning and hardware
- [[06 - Module Integration]] — Cross-module workflows - [[06-ModuleIntegration]] — Cross-module workflows
- [[07 - Technical Requirements]] — Technical decisions made and remaining - [[07-TechnicalRequirements]] — Technical decisions made and remaining
- [[00-DiscoveryQuestions]] — Round 1 answers - [[00-DiscoveryQuestions]] — Round 1 answers
- [[01-DiscoveryQuestions]] — Round 2 answers - [[01-DiscoveryQuestions]] — Round 2 answers

8
Test/EventKit/DiscoveryQuestions/00-DiscoveryQuestions.md
View File

@@ -6,7 +6,7 @@ tags:
# Discovery Questions # 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 ## Related Documentation
- [[00 - System Overview]] — High-level system overview - [[00-SystemOverview]] — High-level system overview
- [[08 - Open Questions]] — Existing open questions list - [[08-OpenQuestions]] — Existing open questions list
- [[07 - Technical Requirements]] — Technical decisions already made - [[07-TechnicalRequirements]] — Technical decisions already made

6
Test/EventKit/DiscoveryQuestions/01-DiscoveryQuestions.md
View File

@@ -6,7 +6,7 @@ tags:
# Discovery Questions — Round 2 # 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 ## Related Documentation
- [[08 - Open Questions]] — Tracks which questions are still open - [[08-OpenQuestions]] — Tracks which questions are still open
- [[00-DiscoveryQuestions]] — Round 1 answers - [[00-DiscoveryQuestions]] — Round 1 answers
- [[07 - Technical Requirements]] — Decisions already made - [[07-TechnicalRequirements]] — Decisions already made

4
Test/EventKit/DiscoveryQuestions/02-DiscoveryQuestions.md
View File

@@ -246,7 +246,7 @@ Should API keys be scoped to specific permissions/modules?
## Related Documentation ## Related Documentation
- [[08 - Open Questions]] — All 30 original questions now answered - [[08-OpenQuestions]] — All 30 original questions now answered
- [[00-DiscoveryQuestions]] — Round 1 answers - [[00-DiscoveryQuestions]] — Round 1 answers
- [[01-DiscoveryQuestions]] — Round 2 answers - [[01-DiscoveryQuestions]] — Round 2 answers
- [[07 - Technical Requirements]] — Technical decisions made - [[07-TechnicalRequirements]] — Technical decisions made

2
Test/EventKit/DiscoveryQuestions/03-DiscoveryQuestions.md
View File

@@ -251,4 +251,4 @@ Should there be a formal staging/preview environment?
- [[00-DiscoveryQuestions]] — Round 1 answers - [[00-DiscoveryQuestions]] — Round 1 answers
- [[01-DiscoveryQuestions]] — Round 2 answers - [[01-DiscoveryQuestions]] — Round 2 answers
- [[02-DiscoveryQuestions]] — Round 3 answers - [[02-DiscoveryQuestions]] — Round 3 answers
- [[07 - Technical Requirements]] — Technical decisions made - [[07-TechnicalRequirements]] — Technical decisions made

2
Test/EventKit/DiscoveryQuestions/04-DiscoveryQuestions.md
View File

@@ -213,4 +213,4 @@ Beyond Cmd+K, should there be keyboard shortcuts for common actions?
- [[01-DiscoveryQuestions]] — Round 2 answers - [[01-DiscoveryQuestions]] — Round 2 answers
- [[02-DiscoveryQuestions]] — Round 3 answers - [[02-DiscoveryQuestions]] — Round 3 answers
- [[03-DiscoveryQuestions]] — Round 4 answers - [[03-DiscoveryQuestions]] — Round 4 answers
- [[07 - Technical Requirements]] — Technical decisions made - [[07-TechnicalRequirements]] — Technical decisions made