Harborlight Ferry Suite
FailedCalm operations suite for the invented Saltmere Ferry Cooperative.
This product didn't ship
Its checks didn't pass, so it was never put live.
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
What was checked
This version didn't ship, because of a check below.
Not checked
Nothing here should be taken as tested.
- Not checked Whether its answers are true
- Not checked No build checks are on record for this version
- Not checked No model looked at the screenshots of this version
- Not checked No Prove it run: nothing it comes with was run for real
The 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.
Took from it
- 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