Skip to content

Open questions

Page summary: See what still needs a decision versus what still needs investigation.

Use this when: Use this to close uncertainty created while documenting the product.

  • Decision questions and evidence gaps are different queues.
  • High priority means money, seats, security/data, or a blocker.
  • Once settled, update the rule and retire the question.

Everything nobody has settled yet. Produced by writing the rules pages, not maintained separately.

Needs a decision

#AboutThe questionOwnerPriorityState
OQ-003Cancelled bookings can be reopenedAnswered: they should not be. The dashboard already blocks it; the service still allows it. Now a fix, not a question — who does it, and does anything need cleaning up in existing data? (BST-002)engineeringhighto fix
OQ-004Status changes that quietly do nothingChanges on a requested or rejected booking report success and change nothing (BST-004). Refuse with an error, or allow? The automatic cancellation job depends on it. Reproduce in dev first.engineeringhighopen
OQ-006Confirmation time on rejected bookingsRejecting a booking writes the current time into the field called confirmed-at (BST-009). Deliberate reuse to mean "when this was decided", or a slip? Reports counting confirmations by that field are affected either way.whoever wrote itmediumopen
OQ-007Part-paid bookings that go nowhereNever cancelled automatically (BST-007). Leave them, or queue them for someone?productmediumopen
OQ-010Two copies of the transition rulesThe dashboard keeps its own list of allowed status changes and it disagrees with the service's (BST-011). One list, or keep two in step? Today the dashboard is the only thing preventing OQ-003.engineeringhighopen
OQ-016A status nothing can displaypartially_confirmed is valid in the service and unknown to the dashboard (BST-013). Finish it or remove it.product + engineeringmediumopen
OQ-017A payment status that fails its own validity checkunpaid is defined but left out of the check (BST-014). Almost certainly a slip.engineeringmediumopen
OQ-018Invoice labels do not match invoice valuesA fully refunded invoice displays as "Unpaid" (BST-015). Deliberate simplification, or wrong?product + financemediumopen
OQ-011Payment values the dashboard expects but never receivesFour values handled by the dashboard do not exist in the service, and a full refund arrives under a different name (BST-012).engineeringhighopen

Needs finding out

#AboutWhat is neededOwnerPriorityState
OQ-014Only instant-confirm experiences reach partnersProduct says this is the rule. The code that enforces it has not been located. Find it, or discover it does not exist. (BST-010)mehighopen
OQ-009Which words each surface showsNot compared across the dashboard, booking engine, partner screens, emails and exports.productmediumopen
OQ-015The full list of booking sourcesFour seen: direct booking, walk-in, partner, Get Your Guide. Probably not all.productmediumopen
OQ-001Where the handbook livesLocal folder for now. Move to a hosted handbook once there are six or seven real pages. GitBook preferred, with a repository behind it so a stale page can be flagged when the code changes.Jamesmediumagreed, later

Closed

#AboutOutcome
OQ-002Partner bookings skip vendor approvalAnswered. Correct, because only experiences set to confirm instantly are offered to partners. Follow-up is OQ-014.
OQ-005The propose-changes settingSkipped by product decision, 5 Aug 2026. Not documented for now.
OQ-008Access to the shared moduleDone. ems-apis cloned 5 Aug 2026. Money rules unblocked.
OQ-012Copied lists between the two systemsSuperseded. Now measurable directly — see the dashboard expects payment values the service never sends (BST-012), a status nothing can display (BST-013).
OQ-013Get Your GuideAnswered. A travel marketplace. Skipped for now.

What the priorities mean

  • high — money, seats, security or data at risk, or it blocks another page
  • medium — slows down building, testing, support or onboarding
  • low — worth explaining, not urgent