Current checkpoint
Planning Tools v0.2.3+
Single endpoint architecture, mismatch protection, public explanation layer, global square-button rule and mobile QA pass are now in place.
Crux Tools / Release Gate
Release checklist before the Planning Calendar.
This page records the public website and planning-tool release gate. It keeps the current toolchain, contact flow and legal layer stable before the larger Planning Calendar / availability system begins.
Before next feature
Legal layer first.
Legal, privacy, contact and public-facing expectation language should be checked before Planning Calendar or availability data is published.
01 / Toolchain
Planning flow
- Homepage wizard gateway routes to tools.
- Specialist tools route to Capture Package Builder as final endpoint.
- Mosaic Planner preserves SVG, JSON and panel-vector execution references.
- Dataset Estimator, Rig Chooser, FOV Calculator, Season Guide and Observatory Planner store matching context for the builder.
- Capture Package Builder excludes stale or mismatched context from final brief and contact handoff.
02 / Contact
Submission path
- Final enquiry goes through Capture Package Builder.
- Contact form receives structured package text.
- Email subject and body identify the request as a capture package request.
- Thanks page displays after submission where supported by the current form route.
- No specialist tool submits directly to mail.
03 / Design
Interface consistency
- Global square-button rule is active.
- Tool cards follow the same visual rhythm.
- Dropdown and form control typography is readable.
- Mobile action rows stack cleanly.
- Long briefs and panel-vector lists wrap without horizontal overflow.
04 / Public explanation
Expectation setting
- Capture Request Process explains that tools produce planning briefs, not quotes or bookings.
- Dataset Products explains Source, Reference and Showcase routes.
- Dataset Tiers remains available for quick comparison.
- Visitor-facing pages point back to Capture Package Builder.
- Manual Crux review is clearly stated before scheduling or delivery.
05 / Legal layer
Before calendar work
- Privacy policy, terms and POPIA language reviewed against the current contact form and tool behaviour.
- Cookie / analytics statement matches current site reality.
- Legal contact and information officer details confirmed.
- Capture package text does not imply confirmed booking, quote or guaranteed delivery.
- Dataset, retention and USB/delivery language remains conditional until Crux review.
06 / Deployment QA
After upload
- Hard refresh or private-window test after deployment.
- Test one full package request from homepage to email.
- Test one mosaic override route into Capture Package Builder.
- Test one mismatched context route and confirm it is excluded.
- Test mobile layout on at least one phone-width viewport.
Legal quick links
Review before the Planning Calendar.
The Planning Calendar will introduce availability, timing, holds, target windows and possibly operational status information. Before that is published, the public legal and privacy language should be checked.
If any of these legal URLs differ on the live site, update this checklist page to match the deployed legal page names.