ArkEdventure2027
Business Requirements Document v1.0 — November 20, 2026
How to use this document. This BRD is the build spec. Sections 4–10 define each content area with acceptance criteria the finished page must pass. Sections 11–12 define who can see and edit what. Section 16 is the phased plan to build against, with a Definition of Done. Appendix A is the single source of truth: every date, amount, and confirmation number in the app must trace to it. Anything not in Appendix A is marked TBD / to confirm in the app — it is not invented.
Online version is current. This page is the single source of truth. The downloadable PDF is a snapshot as of Nov 20, 2026 — where the two differ, this page governs.
Build constraint that shapes everything: No spend at all. Hosting, deployment, and any data store must stay on free tiers already in use (Cloudflare Pages). No paid APIs, no paid plugins, and no per-family accounts in V1. Access is gated by one shared family password, with drafts under a second, different password (see §13) — neither password value appears anywhere in this document or in the site's code.
Purpose — one place, not a scrolling chat
Problem today. Trip updates go out by WhatsApp group message. That works for a single announcement, but families cannot find an old message, check a balance, or confirm a flight time without scrolling or asking again. Flight confirmations are forwarded by Carmen, money is collected by Franky, and decisions from the principal arrive through separate threads. There is no durable, shared reference.
Purpose of ArkEdventure2027. Give every family one link they can open on their phone at any time to answer, in under 30 seconds: When do we fly? Where are we staying? What have we paid and what is still due, and when? What are we doing each day? What is the latest announcement? Who do I call in an emergency, and where are the forms and tickets?
Success looks like
- Families stop asking in WhatsApp for information already published — they check the app first.
- Every amount and date in the app matches Appendix A exactly; no second version of the truth.
- When something changes (flight time, balance due date, itinerary), one edit in the app + one short WhatsApp pointer replaces a long correction thread.
- By March 12, 2027 (Porter balance auto-charge and name-list deadline), every family has seen their final balance and deadline in the app.
What success is not
The app does not collect money, change bookings, or replace the school's own permission forms and communications. It publishes verified information clearly. Payments remain by Interac e-transfer as today; bookings remain with the airlines and the school.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Audience and stakeholders
| Group | Who / how many | What they need |
|---|---|---|
| Family | 17 flight families on the group flights, within 58 families signed up on the school form overall. Each family = student + any travelling siblings / parents as signed up. | Flight times, deposit paid, balance owing and due date, hotel, daily plan, latest announcements. Flight-finance detail that does not apply to non-flight families must be clearly labelled as flight-group only. |
| Franky | Builder & site admin | Built the deposit tracker, collected deposits, issued cheque No. 095; builds and maintains this app. |
| Planners | Gladys, April, Carmen | Plan the trip together. Carmen forwards airline confirmations and the sign-up sheet; source for booking changes. Gladys (parent of Max Falk, Family 15) and April (parent of Ava Dai, Family 11) — specific planning responsibilities to be confirmed. |
| Madame Adina | School principal | Approves official announcements and itinerary; fronted the Flair deposit (see Finance). |
Language: English as primary (school communications are in English). Keep sentences short and plain — many families read on phones and English may not be the home language (Cantonese is spoken in several homes). Avoid jargon; spell out abbreviations on first use.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Scope
| In scope — V1 | Out of scope — V1 |
|---|---|
| Password-gated information hub with 7 areas: Flights, Hotel, Finance, Itinerary, Announcements, Quick contacts & Emergency, Documents — no trip content is visible until the shared family password is entered (see §13) | No online payments, e-transfer buttons, or payment processing |
| Home / dashboard that surfaces: trip countdown, next deadline, latest announcement, and quick links to each area | No booking, seat selection, or name-change requests through the app |
| Per-family finance summary (deposit paid / balance) as already shared in the WhatsApp group — see Privacy (§11) | No per-family logins or accounts — access is by one shared family password only (see §13) |
| Mobile-first pages that work on a phone after one shared-password entry — no per-family login or account | No private messaging, comments, or chat inside the app (WhatsApp remains the discussion channel) |
| Print-friendly trip summary (flights + hotel + emergency contacts once confirmed) | No photo sharing / uploads from families in V1 |
| Content editable by the organizer without a code deploy for announcements and itinerary updates (see §12) | No push notifications — announcements are pulled (families check the link) + a WhatsApp pointer when something important posts |
| No collection of children's personal data beyond names already on the sign-up sheet and already shared with the group |
Scope guardrails
- No invented content. If a fact is not in Appendix A, the page shows “To be confirmed” with the owner who will confirm it — never a plausible placeholder presented as fact.
- No spend. Any feature that needs a paid service is out of scope by definition, however useful. Note it under Future Ideas, do not build it.
- One trip only. This app is for April 13–20, 2027. It is not a general school-trip platform. Reuse is a bonus, not a requirement.
Future ideas (not in V1 — record only, do not build without Franky's go)
Packing checklist per day; rooming list (only if the principal approves sharing it); offline copy for travel day; French phrase card for students; post-trip photo link (external, school-approved only).
Information architecture
| Page | Route (proposed) | Answers |
|---|---|---|
| Home | / | What is happening next? What changed? |
| Flights | /flights | When, which airline, which confirmation? |
| Hotel | /hotel | Where are we staying, check-in/out, contact? |
| Finance | /finance | What was collected, what is paid, what is still due? |
| Itinerary | /itinerary | What are we doing each day? |
| Announcements | /announcements | What is the latest official update? |
| Quick contacts & Emergency | /emergency | Who do I call? What do I do in an emergency? |
| Documents | /documents | Where are the forms, tickets, and packing lists? |
Navigation is a simple top bar / bottom tab bar on mobile with those eight labels, in that order. No hamburger-only navigation — parents must see all sections without hunting.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Content area — Flights
Families' most-checked page. It must show both legs exactly as booked, with no mixing of meeting estimates and confirmed facts. The September 26 meeting estimate ($150 deposit, balance ~March 23) is superseded for flights by the October confirmations — the app shows confirmed figures only, and labels the March 23 date as the final payment collection target in Finance, not as the airline charge date.
| Outbound | Inbound (return) | |
|---|---|---|
| Flight | Porter Airlines PD 372 | Flair Airlines F8 107 |
| Route & date | Vancouver (YVR) → Montreal (YUL), Tue April 13, 2027 | Montreal (YUL) → Vancouver (YVR), Tue April 20, 2027, 08:30–11:10 |
| Confirmation | KC8MMN | F997NW |
| Group size | 56 seats | 35 seats on the paid deposit (34 family seats + 1 extra — see Finance) |
| Money | Total $17,013.78 — deposit $4,200 paid; balance $12,813.78 | Total $10,253.86 — $5,126.93 paid; $5,126.93 balance due |
| Key date | Balance auto-charged March 12, 2027; passenger name list also due March 12, 2027 | Balance due date to confirm with Flair / principal — show as TBD until confirmed in writing |
Principal's travel note (show on Flights page): Madam Adina flies outbound with the group on Porter (her $75 seat is covered by families — see Finance) and arranges her own return. Do not list her as a passenger on the Flair return.
Acceptance criteria — Flights
- Both legs display airline, flight number, route, date, and confirmation number exactly as in the table above.
- Outbound balance ($12,813.78) and auto-charge date (March 12, 2027) are shown together — never the amount without the date.
- Any schedule time not confirmed in Appendix A shows as “Time to be confirmed — check back” rather than a guessed time. Only the Flair 08:30–11:10 time is confirmed for display.
- A “Last verified” date appears under the flight details, updated whenever Carmen forwards a new confirmation.
- Page states in plain language: arrive-at-airport guidance is TBD until the school publishes it — no invented check-in time.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Content area — Hotel
Known: Marriott Peel, Montreal — named in the September 26, 2026 school meeting notes. Not known: no hotel booking confirmation is on file yet. The app must be honest about that distinction; a named hotel is not a confirmed booking.
| Field | Status for V1 |
|---|---|
| Hotel name | Marriott Peel — from meeting notes, Sep 26, 2026 Meeting note |
| Address, phone, check-in / check-out times, rooming, breakfast, cost per family | TBD / to confirm — display as “To be confirmed by the school” until a written confirmation is received |
| Confirmation number | TBD — do not publish until received; never publish a confirmation that exposes other guests' details |
Acceptance criteria — Hotel
- Hotel page names Marriott Peel with the source label “Per Sep 26 school meeting — confirmation pending.”
- Every unconfirmed field shows TBD, not a copied web-search result presented as the booking. A general map link may be added only if labelled “hotel location (general)” and verified.
- When confirmation arrives, the page is updated in the same workflow as §12 and the “confirmation pending” label is removed in the same edit — the two states never coexist.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Content area — Finance
Every figure below is already reconciled in the deposit tracker. The app republishes that reconciliation; it does not recalculate it differently. Finance is one of five equal areas — factual and complete, not the centre of the app.
Deposit collection — complete. $9,180.88 from 17 families, completed Oct 21, 2026 (a day before deadline). Remitted to Adina Priel by cheque No. 095, Oct 21, 2026.
How the per-family deposit was built
| Component | Rate | Notes |
|---|---|---|
| Porter outbound deposit | $75.00 per seat | Family deposits $4,125.00 (55 family seats) |
| Principal's Porter seat — family share | $2.88 per child | $75.00 shared by children headcount (26 children); rounded per family in the tracker |
| Flair inbound deposit | $146.49 per seat | Family deposits $4,980.88 (34 seats) |
| Per-family total | $227.88 – $891.73 | By seats/children. Ex: Family 10 Destiny Chen $670.24; Family 12 Jacques Ip $228.13. |
Reconciliation the app must show (per Carmen Wong)
- Porter: $4,125.00 + $75.00 principal cover = $4,200.00 paid — reconciles exactly.
- Flair: Adina paid $5,126.93 for 35 seats. Families collected for 34 seats = $4,980.88. Difference $146.05 = one extra seat (Christopher Bong, returns on group flight); per Carmen, Flair is to adjust. Do not claim the collection covers the full Flair deposit paid. Show $146.05 as open.
- Totals: deposits paid $9,326.93 vs. $9,180.88 collected/remitted — difference is exactly the $146.05.
What is still due
| Item | Amount / date |
|---|---|
| Porter balance (group) | $12,813.78 — auto-charged March 12, 2027. Per-person balance in the confirmation: $228.82. |
| Flair balance (group) | $5,126.93 — due date TBD to confirm. |
| Final payment collection from families | Target about March 23, 2027 (20 days before departure, per Sep 26 meeting). Exact per-family final amounts: TBD — publish only after Franky reconciles them in the tracker. Do not derive them on the web page. |
| Hotel / other trip costs | TBD — no amounts on file yet. Finance page reserves a section, shows TBD. |
Per-family deposits — all 17 paid in full
These amounts were already shared openly in the WhatsApp group updates during collection.
| Family | Student / family | Deposit | Status |
|---|---|---|---|
| 01 | Emileah Bong | $445.86 | Paid |
| 02 | Carrie Wang | $305.77 | Paid |
| 03 | Olivia Jiang | $891.73 | Paid |
| 04 | Genevieve Yen | $305.77 | Paid |
| 05 | Natalie Hu | $445.86 | Paid |
| 06 | Allison Li | $667.35 | Paid |
| 07 | Willa Heath | $891.73 | Paid |
| 08 | Braven Lo | $891.73 | Paid |
| 09 | Dylan Zhao | $445.86 | Paid |
| 10 | Destiny Chen | $670.24 | Paid |
| 11 | Ava Dai | $227.88 | Paid |
| 12 | Jacques Ip | $228.13 | Paid |
| 13 | August Liu | $305.77 | Paid |
| 14 | Lucas Zhang | $445.86 | Paid |
| 15 | Max Falk | $227.88 | Paid |
| 16 | Debbie Jiang | $891.73 | Paid |
| 17 | Blake Yuan | $891.73 | Paid |
| Total — 17 families | $9,180.88 | ||
| Flair $146.05 — Christopher Bong extra seat | $146.05 | Open |
Acceptance criteria — Finance
- Collection total ($9,180.88), cheque number (095), payee (Adina Priel), and completion date (Oct 21, 2026) appear together in one summary block.
- Per-family table lists all 17 families with amount and Paid status — the same amounts already shared in the WhatsApp group updates. Totals foot to $9,180.88 on the page.
- The $146.05 Flair item is shown as open, with owner (Flair adjustment, via Carmen / Adina) — never netted away silently.
- No bank details, e-transfer references, or sender names are published (§11) — status and amount only. Future per-family balances appear only after they exist in the tracker and are verified by Franky.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Content area — Itinerary
No day-by-day itinerary is on file yet. Ship the known frame (dates, flights, hotel) with a structure ready to fill — unpublished days show “Details to be confirmed by the school,” not invented activities.
| Day | Known frame | Detail status |
|---|---|---|
| Tue Apr 13, 2027 | Travel day — Porter PD 372, YVR → YUL; hotel check-in (TBD) | TBD meeting point & time |
| Wed Apr 14 – Mon Apr 19 | In Montreal — school program days | TBD daily activities, meals, free time |
| Tue Apr 20, 2027 | Return — Flair F8 107, 08:30 YUL → 11:10 YVR | TBD checkout & pickup plan |
Ottawa parent day trip — undecided. Show only as “Under consideration — not confirmed” if the school wants it visible. Never as scheduled or bookable until confirmed. Owner: Adina / Carmen.
Each published day must carry: Date + title, meeting time/point, activities in time order, meals, what to bring/wear, supervising adults if provided, return-to-hotel time, and a “changed” marker with date when edited after publication.
Maps & Places: every meeting point carries a tappable directions link that opens the family's map app — a meeting point is never a bare address. “Back to hotel” directions are available from itinerary venues.
Acceptance criteria — Itinerary
- All 8 days (Apr 13–20) have a row/section from launch, even if the detail is TBD — no missing days.
- No activity, venue, time, or price appears unless it came from the school (Adina / Carmen / official handout). Web-search suggestions are not itinerary facts.
- Ottawa trip, if shown, carries the “not confirmed” label in the heading itself, not only in body text.
- On a phone, today's day (during the trip) is reachable in one tap from Home (“Today in Montreal”).
- Every published meeting point has a tappable directions link; no meeting point is shown as a bare address.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Content area — Announcements
Announcements are the app's replacement for “important WhatsApp message that scrolls away.” WhatsApp still sends the pointer (“New announcement in ArkEdventure2027 — final balances posted”); the app holds the durable text.
Announcement format
| Field | Rule |
|---|---|
| Title + date/time posted | Required. Times in Pacific Time (PCT) before departure, with Montreal local time added during the trip week where relevant. |
| Category | Flights / Hotel / Finance / Itinerary / General / Action required |
| Action required + deadline | If families must do something, the first two lines state what and by when. Example pattern: “Pay final flight balance by [date] — see Finance.” |
| Body | Short paragraphs, bullets for lists. Same plain style as the school's messages — no marketing language. |
| Pinned | At most 2 pinned at once (next deadline + latest critical change). Older pins move to the archive automatically when unpinned. |
Acceptance criteria — Announcements
- Announcements list is reverse-chronological; pinned items stay on top and on Home.
- Each announcement shows who issued it (School / Adina, Carmen, or Franky — organizer) — no anonymous posts.
- Corrections are published as a new announcement that references the one it corrects; the original is marked “Updated — see [date]” rather than silently edited.
- Launch content includes at least: (1) welcome / how to use the app, (2) deposit collection complete + thank-you (17 of 17 paid a day early), (3) next deadline explainer (March 2027 balances). Drafts need Franky's approval before publishing.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Content area — Quick contacts & Emergency
One place for who to call and what to do — organizers, hotel, emergency services, and the nearest hospital. Most contacts are TBD until the school confirms them; nothing appears here before its owner confirms it for publication.
| Contact | Detail | Status |
|---|---|---|
| Emergency | 911 | Public — works across Canada, including Montreal |
| Franky | Trip organizer — contact via the WhatsApp group | TBD phone for publication |
| Planners — Gladys, April, Carmen | Day-of contacts during the trip | TBD |
| Madame Adina | School principal — approves emergency procedures | TBD phone for publication |
| Hotel (Marriott Peel) | Front-desk phone | TBD booking not confirmed |
| Nearest hospital | Name, address, phone | TBD owner: Adina |
| Emergency procedures | Lost / late / medical — what families do first | TBD school to provide |
Acceptance criteria — Quick contacts & Emergency
- Every confirmed contact is a tappable call link on a phone — no number shown as plain text to copy by hand.
- No personal phone number appears until its owner confirms it for publication.
- Emergency procedures come only from the school — never written from a web search.
- Hotel contact appears only once the booking is confirmed (Q1).
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Content area — Documents
One place for the papers families need — consent forms, packing lists, flight and hotel confirmations, tickets. A document appears here only once the school provides the file; the list below is the full set, not a partial one.
| Document | Source | Status |
|---|---|---|
| Consent forms | School | TBD file not provided |
| Packing list | School | TBD file not provided |
| Porter confirmation KC8MMN | Airline, via Carmen | TBD ticket file not provided |
| Flair confirmation F997NW | Airline, via Adina | TBD ticket file not provided |
| Hotel confirmation | School / hotel | TBD booking not confirmed |
Acceptance criteria — Documents
- Every listed document links to the school-provided file and opens on a phone.
- No document appears before the school provides it — the table shows TBD, not a placeholder link.
- Each document shows its source and the date it was received.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Roles, permissions, and privacy
Who can do what
| Role | Can view | Can edit / publish |
|---|---|---|
| Family (reader) | All published pages, only after entering the shared family password. No individual account. | Nothing. No comments, no uploads. |
| Franky — Builder & site admin | All published + drafts | All areas. Publisher in V1; sole publisher for Finance figures (must match tracker). Maintains the site and the link. |
| Planners — Gladys, April, Carmen | All published + drafts | Plan the trip together. Carmen supplies flight / booking updates; Gladys (parent of Max Falk, Family 15) and April (parent of Ava Dai, Family 11) — responsibilities to be confirmed. All three can view and draft changes. Franky publishes in V1. |
| Madame Adina — School principal | All published + drafts | Approves official announcements, itinerary, and hotel information before publication. Supplies Flair / hotel confirmations. Can view and draft changes. |
Publishing (decided Nov 20, 2026): Franky, the planners, and Adina can all publish. Planners and Adina publish by emailing Fo from their authorized email address — Fo structures the update, Muse verifies it against the source and publishes it to live, with no approval from Franky needed. Updates from anyone else are staged for Franky's approval instead. The authorized email list is held by Franky and Muse, not printed here (email addresses are never published — see Privacy below). One control stays: every change is still verified against its source before it goes live, and anything outside this trip and this app is out of scope — 'app info' means only the ArkEdventure2027 app for the Montreal trip and nothing else. If in doubt, Franky is asked first.
Admin views — Draft and Live
Signing in with the drafts password is the admin login. It gives Franky, the planners, and Adina two views with a switch between them:
- Draft view: unpublished changes and drafts, clearly labelled as not yet live, with “changed” markers showing what differs from Live.
- Live view: exactly what families see with the shared family password — the published site, nothing more.
Switching views never publishes anything. Publishing is a separate, explicit action, and in V1 only Franky publishes. Families signed in with the shared family password see Live only and never see the switch.
Privacy — what each family can see
| Visible to all families (by design) | Never published |
|---|---|
| Flights, hotel (once confirmed), itinerary, announcements | E-transfer sender names, references, memos, bank / account details, or payment screenshots |
| Finance summary: group totals, what was collected, what the group still owes the airlines | Email addresses, phone numbers, or home addresses of any family |
| Per-family deposit amounts + Paid status — already shared openly in the WhatsApp group updates during collection, so republishing them changes no family's exposure | Children's full legal names beyond what the sign-up sheet already uses in the group, medical / dietary / passport details, rooming with personal notes |
| Family display names as in the tracker (e.g. “10 - Destiny Chen”) | Airline confirmation passenger lists, or any document image containing personal data |
| Franky's, Adina's, Carmen's, Gladys's, or April's personal contact details beyond what the school already publishes | |
| The shared family password and the drafts password — never in any page, file, code, repository, or this BRD (see §13) |
Search engines: set noindex so the site does not appear in public search results. Takedown: Franky can unpublish any page within one edit if a family or the school raises a privacy concern; the concern and action are noted in the update log (§12).
Acceptance criteria — Roles & privacy
- A pre-launch privacy check passes: no item from the “Never published” list appears on any page, in any image, or in any downloadable file.
- Finance page wording states that amounts shown are the group amounts already shared in WhatsApp updates.
- Site carries noindex and no analytics that collect family data.
- Password gate passes the acceptance criteria in §13 — correct password grants access, a wrong one does not, and a direct link to an inner page does not bypass the gate.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Content-update workflow
Most errors in a trip app are not coding errors — they are a wrong amount or an old flight time published confidently. This workflow is the control.
- Source arrives. Airline confirmation (via Carmen), school notice (Adina), hotel confirmation, or tracker change (Franky). Save the source; note its date. A WhatsApp rumour is not a source.
- Draft. Franky drafts the change (new announcement + edit to the affected area page); planners and Adina can view drafts and draft changes under the drafts password. Planners and Adina can also publish directly via the authorized email route (see below) — decided Nov 20, 2026. Figures are copied from the tracker / confirmation, never retyped from memory.
- Verify. Check: amounts foot, dates include weekday + year, confirmation numbers character-for-character, TBD labels removed only where the source actually confirms the field. For Finance, re-read the tracker row after drafting.
- Approve (when required). Official itinerary, hotel, and school announcements need Adina's (or Carmen's, for booking facts) go-ahead. Finance republication of tracker figures needs no new approval — the tracker is the approval.
- Publish + timestamp. Publish, update the page's “Last verified / Last updated” line, and log the change (date, area, what changed, source).
- Point from WhatsApp. One short WhatsApp message with the link for anything families must act on. Minor typo fixes need no pointer.
Planner updates via Fo — no ferrying (live Nov 20, 2026)
Planners and Adina email trip updates to Fo from their authorized email address (list held by Franky and Muse, not published here) with the section, what changed, and the source. Fo structures each update and pushes it to the Muse bridge queue; the fo-bridge hook wakes Muse within seconds. Muse verifies the change against its source, puts it in Draft directly, and publishes it to live — no approval from Franky needed. Updates from anyone else are staged for Franky's approval instead. If information is missing, Fo emails the sender to ask for it — planners get a conversation with Muse via email when needed. Scope: planners and Adina can only access information directly related to this app and the Montreal trip — 'app info' means only the ArkEdventure2027 app for the Montreal trip and nothing else; anything else is out of scope, and if in doubt Franky is asked first. Test-proven Nov 20, 2026 (email → Fo → bridge → wake → verify; test content never published).
| Change type | Target turnaround | WhatsApp pointer? |
|---|---|---|
| Flight time / date change, deadline change | Same day the confirmation is received | Yes — always |
| New announcement from school | Same day | Yes |
| Finance balance published | Only after tracker reconciliation is signed off by Franky | Yes, with deadline stated |
| Itinerary detail added | Within 2 days of school handout | Once per batch, not per day-row |
| Typo / formatting | Next edit pass | No |
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Non-functional, tech stack & password gate
Note on this page: this BRD site itself is published open — no password gate on this site. Its Worker only handles the feedback boxes (one per section) and the Feedback list below, storing feedback in D1; it handles no passwords. The password gates specified below are requirements for the ArkEdventure2027 trip app that this BRD specifies, not for this BRD publication.
Non-functional requirements
| Requirement | Spec for this build |
|---|---|
| Cost | $0 total, ongoing. Cloudflare Pages free tier for hosting/deploy. No paid domain required in V1 (use the Pages subdomain); a custom domain is optional only if already owned. No paid APIs, fonts, images, or analytics. |
| Platform — “building here” | Built by Muse in this workspace and deployed with the advanced Cloudflare Pages deploy, which bundles the Worker (_worker.js) that runs the password gate — a static-only deploy is not sufficient for V1, because it attaches no Worker and the gate would not run. Source lives in the project repo so any fix is a redeploy, not a rebuild. Full stack in §13 (continued) below. |
| Mobile-first | Designed at ~390px first. Readable without zoom (body 16px+ on web), tap targets 44px+, no horizontal scroll, no hover-only content. Tested at 390px, tablet, and desktop widths before launch. |
| Simplicity for parents | Max 3 taps from Home to any fact. Plain headings that match how parents ask (“What do we still owe?”). No jargon, no account creation, no app install. |
| Performance | Static pages, minimal JavaScript. Usable on hotel / airport Wi-Fi and mobile data. Images compressed; no auto-playing media. |
| Accessibility | Sufficient colour contrast, headings in order, meaningful link text, alt text on any image. Do not convey status by colour alone (Paid also says “Paid”). |
| Data | V1 content as structured files in the repo (e.g. one data file per area) so amounts/dates exist once and render everywhere they appear — a flight date edited once updates Home, Flights, and Itinerary together. |
| Availability / backup | Repo is the backup. Content log (§12) lets any page be reconstructed. No database in V1 — if volume ever suggested one, that is a decision point for Franky (see §13, Tech stack), not an assumed addition. |
| Dates & times | All dates America/Vancouver (PCT) unless labelled Montreal local. Always show weekday + month + day + year for deadlines. Never a bare “March 12” without the year and context. |
Tech stack — building here on the existing $0 stack
| Component | Choice | Role in V1 |
|---|---|---|
| Hosting | Cloudflare Pages, free tier | Hosts the site on the Pages subdomain. No paid domain is required in V1. |
| Server-side gate & checks | Cloudflare Worker, as _worker.js, via the advanced Pages deploy | Runs the password gate and any server-side checks on every request. The advanced deploy is required — a static-only deploy attaches no Worker, so the gate would not run. |
| Trip pages & content | Static content in the project repository | Home, Flights, Hotel, Finance, Itinerary, and Announcements are static pages / data files, served behind the gate. Fast on a phone, with minimal JavaScript. |
| Password configuration | Secret configured at deploy time | The shared password is supplied separately by the owner (Franky) and set as a secret / environment configuration at deploy time. It is never part of the site's code or content (see gate rules below). |
Why this stack fits
- Zero cost: every component is a free tier Franky already uses. No paid service is introduced anywhere in V1.
- Mobile-first: static pages load quickly on hotel / airport Wi-Fi and mobile data, at phone width, with no app install.
- Simple to update: a content fix is an edit to the source, then a redeploy — not a rebuild or a migration.
- A real gate, without paid auth: the Worker checks the password on the server, so protection does not depend on hiding content in the browser.
Intentionally not used in V1: No database. No per-user accounts. No paid authentication service. No paid APIs, plugins, or analytics, and no purchased custom domain. Content lives as structured files in the repository (§13, Data), which is also the backup.
How content updates work: Edit the source in the repository, verify the change under the §12 workflow, redeploy with the advanced Pages deploy, then verify on the canonical Pages domain: the site loads, the gate challenges a new visitor, and every area opens after the password is entered. Changing the password follows the same path — update the secret, redeploy, verify — with no code change.
Decision point — do not assume: if any future component would need a service Franky does not already use for free (for example a database, per-user accounts, a paid auth service, or a paid domain), stop and flag it as a decision point for Franky before building it. It is not added by default, and the $0 rule still applies.
Password gate — specification (for the ArkEdventure2027 app)
The site is gated. The password screen is the only public part of the site; everything behind it is for the trip families.
- Whole site, no exceptions: the gate applies to Home and to every area — Flights, Hotel, Finance, Itinerary, Announcements, Quick contacts & Emergency, and Documents — and to any file that carries trip content. No trip content is visible, and none is sent to the browser, until the password has been entered correctly.
- One shared password: a single shared family password for all families in V1. There are no usernames, no per-family passwords, and no accounts to create or recover.
- Drafts have a different password: the drafts area is gated under a second password, different from the shared family password. Only Franky, the planners (Carmen, Gladys, April), and Adina have it. It is configured as a separate secret at deploy time and is never written into this BRD, the site's code, the repository, or any file.
- Changeable by the owner: Franky can change the password at any time by updating the deploy-time secret and redeploying (no code change). After the change is verified, the old password no longer works and the new password is shared with families through WhatsApp.
- Failed attempts are handled safely: a wrong or empty entry shows only a generic “incorrect password” message — no hint, no part of the password, and no trip content. The check runs on the server (in the Worker), not only in the page. Repeated failed attempts are delayed / rate-limited so guessing is not practical.
- Neither password is ever written down in the system: neither password value must ever appear in this BRD, in the site's code, in the repository, or in any file, log, or screenshot. Each is supplied separately by the owner and configured only as a secret at deploy time. Anyone building or deploying the site must not print it, log it, or copy it into a document.
- Distribution: families receive the password through the existing WhatsApp group, separately from this document. If the password is believed to have leaked, the owner changes it as above — the link alone is never enough to read the site.
Acceptance criteria — Password gate
- Entering the correct shared password grants access to Home and all seven areas.
- Entering a wrong or empty password grants no access, shows the generic error, and reveals no trip content.
- The gate cannot be bypassed by a direct link: opening an inner page URL (for example Flights or Finance) without having entered the password returns the password screen, not the page content — on a first visit, on refresh, and in a new browser.
- Within the same browser session after a correct entry, moving between areas does not require re-entering the password on every page.
- Password-change test passes: after the owner updates the secret and redeploys, the old password fails and the new password works.
- Drafts gate: entering the correct drafts password grants access to the drafts area; the shared family password does not open drafts. The two passwords are independent — changing one does not change the other.
- Admin views: signing in with the drafts password offers a Draft / Live switch. Live view shows exactly what the shared family password shows; Draft view labels every unpublished change. Switching views publishes nothing.
- Pre-launch secret check passes: a search of the BRD, the site code, the repository, and project files finds no password value anywhere.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Risks, assumptions, and open questions
Risks
| Risk | Mitigation in this BRD |
|---|---|
| Stale flight info — schedule changes after publication | “Last verified” date on Flights; same-day update rule (§12); existing flight-status checks continue outside the app. |
| Flair $146.05 adjustment never comes through | Shown openly as an open item. If Flair refuses, Franky / Adina decide who absorbs it — the app updates Finance to the decided treatment, with an announcement. It is never quietly absorbed into family balances. |
| March crunch — Porter auto-charge (Mar 12), name list (Mar 12), and family final payments (~Mar 23) collide | Home surfaces the next deadline from January onward; Finance publishes per-family final amounts as early as the tracker allows. |
| Hotel turns out different from Marriott Peel meeting note | TBD labelling (§5) means a change is a confirmation, not a correction of a false claim. |
| Link or shared password spreads beyond the group | Whole-site password gate (§13) + noindex + “never published” list (§11). The link alone does not open the site. If the password is believed leaked, the owner changes the deploy-time secret, redeploys, and shares the new password via WhatsApp. |
| Families keep relying only on WhatsApp and miss app updates | Every important publish gets a WhatsApp pointer (§12). The app replaces storage, not the nudge. |
Assumptions
- 58 sign-ups / 17 flight families as of this BRD; if the flight group changes, Finance and Flights are updated from the tracker / new confirmation, not by editing totals by hand.
- Amounts are in Canadian dollars (CAD) throughout.
- Adina and Carmen continue as the authoritative sources for bookings and school decisions.
- Families have a phone browser and WhatsApp — no other software is assumed.
Open questions — answer before the phase noted
| # | Question | Owner | Needed by |
|---|---|---|---|
| Q1 | Hotel confirmation: address, check-in/out, rooms, cost, confirmation no.? | Adina / Carmen | Phase 1 content freeze |
| Q2 | Flair balance due date (exact) and will Flair adjust the $146.05 Chris seat? | Carmen / Adina → Flair | Phase 2 |
| Q3 | Day-by-day itinerary + meeting points/times for Apr 13 and Apr 20? | Adina (school) | Phase 2 |
| Q4 | Ottawa parent day trip: happening? Date, cost, sign-up method? | Adina | Phase 2 |
| Q5 | Per-family final flight balances and exact collection deadline in March? | Franky (tracker) | Phase 2 |
| Q6 | Emergency contacts to publish in §9 + day-of contact method during the trip? | Adina | Phase 3 |
| Q7 | Share the link and shared password beyond flight families (all 58) or flight families first? | Franky + Adina | Launch |
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
How families actually use each area — before and during the trip
ArkEdventure2027 is not a finance tool with trip pages attached. Finance matters before departure; on the road, flights, hotel, itinerary, and announcements matter more, hour by hour. Each area below is specified to the same depth, for the moment a parent actually opens it.
| Area | Before the trip (at home) | During the trip (Apr 13–20, in Montreal) |
|---|---|---|
| Flights | Check dates, times, confirmations; plan airport arrival; note Mar 12 balance/name-list deadline. | Travel-day card on Home: today's flight, meeting point, “arrive by” time (once school confirms it). Return-day view on Apr 20 shows checkout + airport transfer in one place with the flight. |
| Hotel | See where the group stays, plan drop-off / contact, note check-in expectations. | Hotel address + phone tappable to call / open maps; “back to hotel” directions from itinerary venues; lost / late procedure once the school provides it (TBD). |
| Finance | Confirm deposit paid; see final balance and deadline; plan the March payment. This is the primary finance moment — after final balances are settled, Finance becomes a receipt/archive. | Families should rarely need Finance in Montreal. It stays available as a record, but Home during the trip leads with Today, Hotel, and Announcements — not money. |
| Itinerary | Preview each day, arrange work / care for siblings, pack for planned activities. | The most-opened area on the trip. Home shows “Today” first: times, meeting point, what to bring, meals, return to hotel. Tomorrow is one tap away for planning the night before. |
| Announcements | Catch deadline reminders and changes without scrolling WhatsApp. | Same-day changes (weather, timing, meeting point) post here + WhatsApp pointer. Pinned announcement on Home is the first thing a parent checks each morning. |
| Quick contacts & Emergency | Save the numbers before departure; know who to call and what to do if something goes wrong. | One-tap call links for organizers, hotel, and hospital; emergency procedures in one place. The most urgent page on the trip. |
| Documents | Download consent forms and packing lists; check tickets before travel day. | Tickets and confirmations on hand at the airport; consent forms available if the school asks for them. |
Equal-weight design rules
- Home gives all seven areas equal entry points. During Apr 13–20, Home re-orders itself: Today (Itinerary) → Announcements (pinned) → Flights (today's leg) → Hotel → Quick contacts & Emergency → Documents → Finance. Before the trip, Home leads with Next Deadline + Latest Announcement + countdown, with all five equally reachable.
- No area requires more taps than another. No area is hidden in a submenu.
- Acceptance for launch is per-area (Sections 4–10) — the app is not “done” if Finance passes and Itinerary is still a placeholder of TBD rows without the Today view working.
- On-trip usability test (Phase 3): a parent, on a phone, standing in the hotel lobby scenario, can find (a) today's meeting time, (b) hotel phone, (c) today's flight or return plan, (d) the latest announcement, and (e) an emergency contact — each in under 30 seconds, without help.
Design implication: Build the itinerary Today view, hotel contact actions, and travel-day flight card with the same care as the finance table. They are not “content to fill in later” — they are core product for the week families are actually travelling.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Phased plan & Definition of Done
| Phase | Build | Exit gate |
|---|---|---|
| Phase 1 — Core hub Build first | Cloudflare Pages site on the §13 stack (advanced deploy, Worker _worker.js, whole-site password gate), Home + all 7 area pages with Appendix A facts; Finance with completed deposit table + reconciliation; Flights with both legs; Hotel with TBD labelling; Itinerary frame (8 days); Announcements with 3 launch posts; Quick contacts & Emergency with organizer + hotel contacts (hospital / procedures TBD); Documents with the forms and tickets on file. Mobile nav, noindex, privacy check. | All §4–10 acceptance criteria that do not depend on TBD confirmations pass at 390px, and the password-gate criteria in §13 pass. Link shareable with Franky for review. |
| Phase 2 — Complete the picture | Fill hotel confirmation (Q1), Flair due date / adjustment outcome (Q2), full itinerary (Q3), Ottawa decision (Q4), per-family final balances (Q5) as each source arrives — via §12 workflow, one area at a time. | Each filled area re-passes its acceptance criteria; no TBD label remains on a field the source has confirmed. |
| Phase 3 — Trip-ready | Today view, travel-day cards, print-friendly summary, emergency contacts complete once the school confirms them (Q6), on-trip usability test, final WhatsApp launch message with the link. | Usability test in §15 passes; print summary checked on paper; Franky + Adina sign off to share the link (Q7). |
Phases are content gates, not date promises. Do not hold Phase 1 waiting for hotel/itinerary confirmations — ship the honest TBD version so families learn the link early.
Wish list — not committed to any phase
- My Family dashboard — each family sees its own booking details, payment status, and assigned group. Held back: it needs a lot of per-family data that is hard to keep updated (Franky, Nov 20, 2026).
- Photo gallery — families share trip photos with appropriate permissions. Needs a storage and permissions decision first; no commitment.
Definition of Done — the whole app
- Every fact in the app traces to Appendix A or to a logged source received after this BRD (with date + source in the update log).
- All seven areas pass their acceptance criteria (§4–10) at 390px, tablet, and desktop; no horizontal scroll; no placeholder presented as fact.
- Finance totals foot to the tracker ($9,180.88 collected); the $146.05 Flair item is correctly shown as open until Flair/Adina close it.
- Privacy check (§11) passes; site is noindex; $0 cost verified (no paid service in the deploy).
- Password gate (§13) passes on the live site: correct password grants access, a wrong one does not, a direct inner link does not bypass it, and no password value exists in this BRD, the code, the repository, or any project file.
- Deploy verified on the canonical Pages domain, via the advanced deploy with the Worker active: the gate challenges a new visitor, home loads after entry, all 7 area routes load, latest announcement renders — not just “deploy succeeded.”
- Franky has approved the launch announcements and the WhatsApp pointer message before the link is shared with families.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Verified trip facts (single source of truth)
All amounts CAD. If any fact above changes, update this appendix in the BRD's next version and the app in the same pass — the two never diverge.
- Trip
- Ark Montreal Edventure 2027, April 13–20, 2027. 17 flight families; 58 families signed up overall.
- Outbound
- Porter PD 372, YVR → YUL, Apr 13, 2027, conf KC8MMN, 56 seats. Total $17,013.78; deposit $4,200 paid; balance $12,813.78 auto-charged Mar 12, 2027; name list due Mar 12, 2027.
- Inbound
- Flair F8 107, YUL → YVR, Apr 20, 2027, 08:30–11:10, conf F997NW. Total $10,253.86; $5,126.93 paid by Adina Priel (MasterCard); $5,126.93 balance due (date TBD).
- Hotel
- Marriott Peel — Sep 26, 2026 meeting notes only. No confirmation on file. All other hotel fields TBD.
- Finance
- Deposits $9,180.88 collected from 17 families, complete Oct 21, 2026; cheque No. 095 to Adina Priel. Per family $227.88–$891.73 (Porter $75/seat + Flair $146.49/seat + $2.88/child principal-seat share). Final family payments target ~Mar 23, 2027. Flair $146.05 extra-seat item (Christopher Bong) pending Flair adjustment, per Carmen Wong.
- Itinerary / Ottawa
- No day-by-day itinerary on file — TBD. Optional parent Ottawa day trip — undecided — TBD.
- People
- Franky Ip (builder & site admin; organizer / collector), Carmen Wong (planner — bookings / sign-up sheet), Gladys Li (planner — responsibilities to be confirmed; parent of Max Falk, Family 15), April Yi Pui Ha (planner — responsibilities to be confirmed; parent of Ava Dai, Family 11), Adina Priel (school principal).
Download the BRD as PDF (18 pages) — a snapshot as of Nov 20, 2026. This online page is current and is the single source of truth; where the two differ, this page governs.
Feedback on this section
Spotted something wrong, missing, or unclear in this section? Tell us — it goes to the trip organizers.
Feedback
Feedback submitted through the boxes on each section, newest first. Names appear only when the submitter gave one. Sections with no feedback yet show “No feedback yet”.
Loading feedback…