Appearance
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
| # | About | The question | Owner | Priority | State |
|---|---|---|---|---|---|
| OQ-003 | Cancelled bookings can be reopened | Answered: 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) | engineering | high | to fix |
| OQ-004 | Status changes that quietly do nothing | Changes 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. | engineering | high | open |
| OQ-006 | Confirmation time on rejected bookings | Rejecting 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 it | medium | open |
| OQ-007 | Part-paid bookings that go nowhere | Never cancelled automatically (BST-007). Leave them, or queue them for someone? | product | medium | open |
| OQ-010 | Two copies of the transition rules | The 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. | engineering | high | open |
| OQ-016 | A status nothing can display | partially_confirmed is valid in the service and unknown to the dashboard (BST-013). Finish it or remove it. | product + engineering | medium | open |
| OQ-017 | A payment status that fails its own validity check | unpaid is defined but left out of the check (BST-014). Almost certainly a slip. | engineering | medium | open |
| OQ-018 | Invoice labels do not match invoice values | A fully refunded invoice displays as "Unpaid" (BST-015). Deliberate simplification, or wrong? | product + finance | medium | open |
| OQ-011 | Payment values the dashboard expects but never receives | Four values handled by the dashboard do not exist in the service, and a full refund arrives under a different name (BST-012). | engineering | high | open |
Needs finding out
| # | About | What is needed | Owner | Priority | State |
|---|---|---|---|---|---|
| OQ-014 | Only instant-confirm experiences reach partners | Product says this is the rule. The code that enforces it has not been located. Find it, or discover it does not exist. (BST-010) | me | high | open |
| OQ-009 | Which words each surface shows | Not compared across the dashboard, booking engine, partner screens, emails and exports. | product | medium | open |
| OQ-015 | The full list of booking sources | Four seen: direct booking, walk-in, partner, Get Your Guide. Probably not all. | product | medium | open |
| OQ-001 | Where the handbook lives | Local 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. | James | medium | agreed, later |
Closed
| # | About | Outcome |
|---|---|---|
| OQ-002 | Partner bookings skip vendor approval | Answered. Correct, because only experiences set to confirm instantly are offered to partners. Follow-up is OQ-014. |
| OQ-005 | The propose-changes setting | Skipped by product decision, 5 Aug 2026. Not documented for now. |
| OQ-008 | Access to the shared module | Done. ems-apis cloned 5 Aug 2026. Money rules unblocked. |
| OQ-012 | Copied lists between the two systems | Superseded. Now measurable directly — see the dashboard expects payment values the service never sends (BST-012), a status nothing can display (BST-013). |
| OQ-013 | Get Your Guide | Answered. 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