--- tags: - eventkit --- # Open Questions ## Purpose Remaining decisions and questions that need answers before or during implementation. Organised by topic area. See [[07-TechnicalRequirements]] for decisions already made. --- ## Business & Scope | # | Question | Options / Notes | | --- | ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | 1 | ~~**Primary equipment types** — which sectors first?~~ | ✅ **Answered**: Audio, Lighting, Rigging, Power distribution for MVP | | 2 | ~~**Target company size** — small (1-5 people) or larger (20+)?~~ | ✅ **Answered**: Small to medium companies wanting to share resources. Both scales should be possible | | 3 | ~~**Pricing model** — how will EventKit itself be offered?~~ | ✅ **Answered**: Open core — free self-hosted, paid SaaS with premium features | | 4 | ~~**MVP scope** — which module to build first?~~ | ✅ **Answered**: Inventory + Scanning → Planning → CRM → Federation | | 5 | ~~**Data migration** — what systems are companies migrating from?~~ | ✅ **Answered**: Nice-to-have future feature. Import tooling not a priority for MVP | --- ## Technical | # | Question | Options / Notes | | --- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | 6 | ~~**Tech stack** — backend language and framework?~~ | ✅ **Decided: Go** with ConnectRPC | | 7 | ~~**Frontend framework**~~ | ✅ **Decided: React** with @tanstack/router + @tanstack/query + shadcn/ui. Mobile: React Native / Expo (planned, not priority) | | 8 | ~~**Database**~~ | ✅ **Decided: PostgreSQL 15+** | | 9 | ~~**Search engine**~~ | ✅ **Answered**: PostgreSQL full-text search first, dedicated engine (Meilisearch) later if needed | | 10 | ~~**File storage**~~ | ✅ **Answered**: Both — local filesystem + S3-compatible, configurable per deployment | | 11 | ~~**Real-time updates**~~ | ✅ **Answered**: Not from the start. Future nice-to-have via gRPC server-streaming | | 12 | ~~**Background jobs**~~ | ✅ **Answered**: External broker (NATS or Redis) — suited for Kubernetes deployment | --- ## Federation | # | Question | Options / Notes | | --- | ---------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | | 13 | ~~**Discovery** — how do companies find each other?~~ | ✅ **Answered: Manual URL exchange** between companies | | 14 | ~~**Protocol format**~~ | ✅ **Decided: gRPC via ConnectRPC** with Protobuf service definitions | | 15 | ~~**Pricing in federation** — should sub-hire rates be shared automatically?~~ | ✅ **Answered: Prices negotiated per-transaction** — out-of-band negotiation, system tracks equipment movement | | 16 | ~~**Asset ownership transfer** — can an asset be permanently sold to another instance?~~ | ✅ **Answered: Yes** — permanent ownership transfer is supported | | 17 | ~~**Federation versioning** — how to handle protocol upgrades?~~ | ✅ **Answered**: Protobuf backward compat, document breaking changes, no formal version negotiation | | 18 | ~~**Dispute resolution** — what happens if companies disagree about asset condition?~~ | ✅ **Answered**: Timestamped condition logs + out-of-band dispute handling | --- ## Scanning & Hardware | # | Question | Options / Notes | | --- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | 19 | ~~**Primary scanning device** — phone cameras or dedicated scanners?~~ | ✅ **Answered**: Both — phone camera default, Bluetooth scanner as power-user option | | 20 | ~~**Label printer** — should EventKit support direct printing?~~ | ✅ **Answered**: PDF default, direct printing optional | | 21 | ~~**Existing barcodes** — do companies already have asset labels?~~ | ✅ **Answered: Yes, support legacy barcode import/mapping** if possible | | 22 | ~~**Offline requirements** — how often will users be offline?~~ | ✅ **Answered: Nice-to-have**, not a hard requirement | --- ## CRM | # | Question | Options / Notes | | --- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 23 | ~~**Invoicing depth** — full invoicing or integration with existing accounting?~~ | ✅ **Answered: Integrated accounting features are the priority.** Xero/QuickBooks integration is optional/secondary. Invoices, payments, and purchases all in-app | | 24 | ~~**Accounting integrations** — which platforms?~~ | ✅ **Answered: Xero and QuickBooks** — optional, not priority. Integrated features come first | | 25 | ~~**Email integration** — built-in email or link to external?~~ | ✅ **Answered**: Full IMAP/SMTP with sub-addressing for routing emails to projects/clients | | 26 | ~~**Marketing features** — email campaigns needed?~~ | ✅ **Answered**: Not for now — leave to dedicated tools | --- ## Planning | # | Question | Options / Notes | | --- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | 27 | ~~**Crew management depth** — basic assignment or full scheduling?~~ | ✅ **Answered**: Crew members login and confirm availability. Basic scheduling with crew portal | | 28 | ~~**Transport planning** — basic or advanced?~~ | ✅ **Answered**: Start basic → intermediate (weight/volume) → advanced (route optimisation) | | 29 | ~~**Venue database** — shared across instances?~~ | ✅ **Answered**: Start local, federate later | | 30 | ~~**Calendar integration** — which platforms?~~ | ✅ **Answered**: CalDAV + iCal export for MVP. Google Calendar + Outlook/Exchange later | --- ## Priority Matrix All 30 questions have been answered. ✅ --- ## Related Documentation - [[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