Harborlight Ferry Suite
Status: Failed.
Your muse
Build Harborlight, a complete operations suite for the made-up Saltmere Ferry Cooperative, an invented island ferry company. All people, boats, routes and numbers are made up. This is a big, multi-part product, so please split the work across subagents, one per part, and take as long as the quality needs. Do the whole thing, not a sketch. Parts: 1. Public booking site: timetable for 6 invented routes, seat and vehicle booking, fares by season, booking lookup by code, and a cancel flow. 2. Dispatcher console: a live board of 8 boats, drag to reassign crews, delay and weather notices that update the public site, and a day replay. 3. Crew app: shift calendar, swap requests with approval, hours limits with warnings, safety checklists before each sailing. 4. Maintenance tracker: parts inventory, work orders, boat downtime calendar that blocks bookings when a boat is out, and overdue alerts. 5. Finance reports: revenue by route and season, fuel cost per crossing, refunds, CSV export, and charts. 6. Passenger assistant: a chat helper on the public site that answers from the timetable and notices using saved data, and hands off to a person. 7. Admin: roles for dispatcher, crew, mechanic and finance, an audit log of every change, and seed data with at least 90 days of made-up history. Every part must share one real database and work end to end: a booking made on the public site must show on the dispatcher board, a boat taken out for maintenance must block new bookings and notify affected passengers, and finance must see refunds. Write automated tests for every part and run them. Test all the cross-part flows in a browser and fix what fails before finishing. Make the look distinctive and calm, like a harbor at dawn, on phones and desktops.
From the owner: Stop the run.
State is good: actions and data libs exist. Now the pages.
The plan: Harborlight Ferry Suite
Calm operations suite for the invented Saltmere Ferry Cooperative.
- Visitor opens public site and sees 6 invented routes and service notices
- Visitor picks route, date and party plus vehicle if needed
- App shows matching sailings with times, seats left and season fare
- Visitor selects a sailing that is not blocked by downtime or cancellation
See the full plan
Who it's for
Ferry passengers plus dispatcher, crew, mechanic and finance staff in this demo.
How it works
- Visitor opens public site and sees 6 invented routes and service notices.
- Visitor picks route, date and party plus vehicle if needed.
- App shows matching sailings with times, seats left and season fare.
- Visitor selects a sailing that is not blocked by downtime or cancellation.
- Visitor enters party size and vehicle and confirms demo booking.
- App saves booking to shared database and shows a booking code.
- Visitor looks up booking by code later and sees live status.
- Visitor can cancel booking and sees refund amount for finance.
- Dispatcher sees the new booking and cancel on the live board.
- Finance sees the sale and any refund in reports and CSV.
Screens
- Public Home and Timetable. Browse 6 routes, sailings, fares and service notices.
- Booking Flow. Pick sailing, seats, vehicle and confirm booking to get a code.
- Booking Lookup and Cancel. Find a booking by code, see live status and cancel with refund.
- Dispatcher Board. Live view of 8 boats, sailings, bookings, delays and crew assignments.
- Day Replay. Step through one day of sailings and notices.
- Crew Calendar. See shifts, hours totals and warnings.
- Swaps and Approvals. Request swaps and approve or decline them.
- Safety Checklist. Complete required checks before each sailing.
- Parts Inventory. See parts, counts and low stock.
- Work Orders. Create and track maintenance jobs and overdue alerts.
- Downtime Calendar. Take boats out and see blocked sailings.
- Finance Reports. See revenue by route and season, fuel per crossing, refunds, charts and CSV export.
- Passenger Assistant. Chat helper on public site with cited answers and person handoff draft.
- Admin Roles and Audit. Switch demo roles, reseed 90 day history and read the audit log.
- Quality Checks and Cross Part Tests. Run automated checks for every part and browser flows and see pass or fail.
What goes in
- Text: Route, date and party size for timetable search.
- Text: Seats, vehicle type and booking code for create, lookup and cancel. No real contact details.
- Text: Passenger chat question typed on the public site.
What comes out
- Text: Booking confirmation with code, sailing, fare and cancel link.
- Text: Dispatcher board, day replay, crew roster, maintenance lists and audit log views.
- Text: Finance report with revenue by route and season, fuel per crossing, refunds and CSV download.
- Text: Assistant answer with cited sailing or notice plus handoff draft when needed.
Models
Model Used for Why Muse Wonder Answer passenger questions from saved timetable and notices It reads the saved sailings and notices and returns a grounded answer with sources, plus a handoff draft when it cannot answer. Limits
- All people, boats, routes and numbers are invented for Saltmere Ferry Cooperative. Nothing is a real sailing.
- Bookings store only a code, sailing, seats, vehicle and fare. No real names, emails, payments, SMS or tickets.
- Boat downtime blocks new bookings and shows a banner plus affected codes on lookup. There are no emails or texts. The owner approves any outbound message.
- Assistant answers only from saved timetable and notices. When unsure it shows a handoff draft the visitor copies to the harbor desk.
- Roles are demo switches in the browser because there is no sign in. Anyone opening the app can try each role.
- Live board changes show within seconds for up to 20 watchers at once and 10 on one network.
- Downtime, delay and refund math is demo logic with invented fuel and fare numbers.
- Works with keyboard and touch. Drag to reassign also has tap to assign for phones.
From your inspo
The person gave text only with no references and asked for Harborlight, a full operations suite for the invented Saltmere Ferry Cooperative with seven linked parts sharing one database.
Takes
- Full ferry operations job covering booking, dispatch, crew, maintenance, finance, assistant and admin
- End to end shared data flows between public bookings, dispatcher board, downtime blocks and refunds
- Calm harbor at dawn mood carried in copy and generated imagery only
Cost per run: about $0.03 (est.). One assistant answer reads about 5000 input tokens at $4 per million ($0.02) and writes about 300 output tokens at $20 per million ($0.006). Total is about $0.026, rounded to $0.03 per run.
What you asked for 0 of 45 checked and working
- R1: Show a public timetable for 6 invented routes with times and boats. Not checked yet
- R2: Let visitors book seats and vehicles on a sailing and keep the booking after reload. Not checked yet
- R3: Price fares by season and show the correct fare at booking. Not checked yet
- R4: Let visitors look up a booking by its code. Not checked yet
- R5: Provide a cancel flow that cancels by code and creates a refund record. Not checked yet
- R6: Show a dispatcher live board of 8 invented boats with sailings, crew and status. Not checked yet
- R7: Let dispatchers drag to reassign crews, with tap to assign on touch screens, and keep it after reload. Not checked yet
- R8: Let dispatchers post delay and weather notices that update the public site within seconds. Not checked yet
- R9: Provide a day replay that steps through one day of sailings and notices. Not checked yet
- R10: Show a crew shift calendar and keep assignments after reload. Not checked yet
- R11: Handle swap requests with approval by a lead and keep the result after reload. Not checked yet
- R12: Enforce hours limits with warnings before a crew member goes over. Not checked yet
- R13: Require a safety checklist before each sailing and keep the signed checklist. Not checked yet
- R14: Track parts inventory with counts and keep it after reload. Not checked yet
- R15: Track work orders with boat, priority and status and keep them after reload. Not checked yet
- R16: Keep a boat downtime calendar that blocks new bookings when a boat is out. Not checked yet
- R17: Show overdue alerts for work orders and downtime that need action. Not checked yet
- R18: Report revenue by route and season from real bookings. Not checked yet
- R19: Report fuel cost per crossing with invented fuel numbers. Not checked yet
- R20: Show refunds from cancelled bookings in finance. Not checked yet
- R21: Export finance reports to CSV that downloads in the browser. Not checked yet
- R22: Show finance charts for revenue, fuel and refunds. Not checked yet
- R23: Provide a chat helper on the public site that answers from saved timetable and notices. Not checked yet
- R24: Hand off to a person with a copied draft and harbor desk details when the helper cannot answer. No auto messages. Not checked yet
- R25: Provide role views for dispatcher, crew, mechanic and finance as demo switches. Not checked yet
- R26: Keep an audit log of every change with role, action and time, still there after reload. Not checked yet
- R27: Seed made up history for at least 90 days of sailings, bookings, maintenance and finance. Not checked yet
- R28: Show a booking made on the public site on the dispatcher board without reload. Not checked yet
- R29: When a boat is taken out, block new bookings and show a notice plus affected codes on lookup. Not checked yet
- R30: Show every cancelled booking refund in finance reports. Not checked yet
- R31: Use a distinctive calm harbor at dawn style that reads well on phones and desktops. Not checked yet
- R32: Provide clear navigation between booking, dispatch, crew, maintenance, finance, assistant and admin with empty states before data and error states when a save fails. Not checked yet
- R33: Let staff delete what was saved, such as notices, swap requests, work orders, parts and downtime blocks, and keep cancelled bookings as cancelled records for audit and finance. Not checked yet
- R34: Run the whole Harborlight product as one complete operations suite where every part reads and writes the same shared database. Not checked yet
- R35: Present all boats, routes, island stops and company details as invented content for the island ferry company with a made up banner. Not checked yet
- R36: Build the whole multi part product with all seven parts working, not a partial sketch or demo of one part. Not checked yet
- R37: Organize the product in clear parts so work can be split across teams with one part each, all merging into one shared database. Not checked yet
- R38: Hold a high quality bar for data accuracy, calm design and readable copy across phones and desktops. Not checked yet
- R39: Deliver the whole thing as a finished working suite, not a sketch or mockup. Not checked yet
- R40: Provide the dispatcher console as a live board with boats, crews, delays and replay in one place. Not checked yet
- R41: When the assistant cannot answer, hands the visitor a handoff draft to copy to the harbor desk. Not checked yet
- R42: When downtime blocks a sailing, notify affected passengers with a banner and affected codes on lookup. Not checked yet
- R43: Include a quality page that can write and run automated tests for every part and show pass or fail. Not checked yet
- R44: Test all cross part flows in a browser from that quality page and fix failures so booking to dispatch to finance stays green before finishing. Not checked yet
- R45: Make every part share one real database and work end to end so bookings, downtime, refunds and notices stay in sync. Not checked yet
This build didn't ship.
Stopped by you.
A broken product is never shown as working. Muse Code's notes are in its steps.