The current priority is proving one real Brisbane-origin flow: ex-HMAS Brisbane trip selection, wreck-readiness planning and an operator-ready enquiry brief.
| Release | Previous | Current | Status |
|---|---|---|---|
| R8 - Trip Catalogue Usability | 100% | 100% | Complete |
| R9 - Operator Demo Readiness | 72% | 90% | In progress |
| R10 - Founder Field-Test Readiness | 70% | 90% | In progress |
| R11 - Strong Launch Candidate | 55% | 100% | Complete for static baseline |
| R12 - Intelligence Engine v1 | 0% | 75% | Static/data skeleton implemented |
| R13 - HMAS Founder Field Test | 0% | 65% | Brisbane-to-HMAS planner and enquiry path implemented |
| R13.1 - Design and Function Remediation | 0% | 70% | Light visual system, nav consistency and trip-card actions corrected |
Homepage, top navigation and catalogue now route around Trips as the primary object.
Home to Trips to Plan to Enquire is connected, with Back to Trips available on trip dossiers.
Selected trip, mode, comfort, certification, dives and recency persist between planner and enquiry.
Concierge, trust language and status framing are explicit about what is and is not ready.
Dive profile, source, operator, gear and cost-envelope signals now exist as static pages and structured data.
Brisbane origin, wreck comfort, gear needs, operator questions and HMAS-specific enquiry output are now connected.
Dark prototype styling was replaced with a lighter cyan interface, clearer controls and consistent public navigation.
| Deferred | Reason |
|---|---|
| Payments | Commercial, refund and supplier readiness still need signoff. |
| Member login | Requires subscription infrastructure and privacy policy work. |
| Flight/hotel APIs | Premature until demand and planning workflow are validated. |
| Dynamic maps | Useful later, but not required for R11 candidate readiness. |
| Supplier portal | Requires operator agreements and backend architecture. |