9.2 KiB
9.2 KiB
tags
| tags | |
|---|---|
|
Open Questions
Purpose
Remaining decisions and questions that need answers before or during implementation. Organised by topic area. See 07 - Technical Requirements for decisions already made.
Business & Scope
| # | Question | Options / Notes |
|---|---|---|
| 1 | ✅ Answered: Audio, Lighting, Rigging, Power distribution for MVP | |
| 2 | ✅ Answered: Small to medium companies wanting to share resources. Both scales should be possible | |
| 3 | ✅ Answered: Open core — free self-hosted, paid SaaS with premium features | |
| 4 | ✅ Answered: Inventory + Scanning → Planning → CRM → Federation | |
| 5 | ✅ Answered: Nice-to-have future feature. Import tooling not a priority for MVP |
Technical
| # | Question | Options / Notes |
|---|---|---|
| 6 | ✅ Decided: Go with ConnectRPC | |
| 7 | ✅ Decided: React with @tanstack/router + @tanstack/query + shadcn/ui. Mobile: React Native / Expo (planned, not priority) | |
| 8 | ✅ Decided: PostgreSQL 15+ | |
| 9 | ✅ Answered: PostgreSQL full-text search first, dedicated engine (Meilisearch) later if needed | |
| 10 | ✅ Answered: Both — local filesystem + S3-compatible, configurable per deployment | |
| 11 | ✅ Answered: Not from the start. Future nice-to-have via gRPC server-streaming | |
| 12 | ✅ Answered: External broker (NATS or Redis) — suited for Kubernetes deployment |
Federation
| # | Question | Options / Notes |
|---|---|---|
| 13 | ✅ Answered: Manual URL exchange between companies | |
| 14 | ✅ Decided: gRPC via ConnectRPC with Protobuf service definitions | |
| 15 | ✅ Answered: Prices negotiated per-transaction — out-of-band negotiation, system tracks equipment movement | |
| 16 | ✅ Answered: Yes — permanent ownership transfer is supported | |
| 17 | ✅ Answered: Protobuf backward compat, document breaking changes, no formal version negotiation | |
| 18 | ✅ Answered: Timestamped condition logs + out-of-band dispute handling |
Scanning & Hardware
| # | Question | Options / Notes |
|---|---|---|
| 19 | ✅ Answered: Both — phone camera default, Bluetooth scanner as power-user option | |
| 20 | ✅ Answered: PDF default, direct printing optional | |
| 21 | ✅ Answered: Yes, support legacy barcode import/mapping if possible | |
| 22 | ✅ Answered: Nice-to-have, not a hard requirement |
CRM
| # | Question | Options / Notes |
|---|---|---|
| 23 | ✅ Answered: Integrated accounting features are the priority. Xero/QuickBooks integration is optional/secondary. Invoices, payments, and purchases all in-app | |
| 24 | ✅ Answered: Xero and QuickBooks — optional, not priority. Integrated features come first | |
| 25 | ✅ Answered: Full IMAP/SMTP with sub-addressing for routing emails to projects/clients | |
| 26 | ✅ Answered: Not for now — leave to dedicated tools |
Planning
| # | Question | Options / Notes |
|---|---|---|
| 27 | ✅ Answered: Crew members login and confirm availability. Basic scheduling with crew portal | |
| 28 | ✅ Answered: Start basic → intermediate (weight/volume) → advanced (route optimisation) | |
| 29 | ✅ Answered: Start local, federate later | |
| 30 | ✅ Answered: CalDAV + iCal export for MVP. Google Calendar + Outlook/Exchange later |
Priority Matrix
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-DiscoveryQuestions — Round 1 answers
- 01-DiscoveryQuestions — Round 2 answers