MichiWise

How MichiWise works

MichiWise is built as a route-first sequence. The planner can collect answers, return two validated route concepts, and generate a Fast itinerary when exact readiness checks pass. Detailed/Pro requires a signed-in Pro entitlement. Maps and purchase are not active. No real provider, OAuth, or deployment success is claimed.

  1. Station 1

    Inputs and route shape

    A traveller enters origin, gateway policy, one-to-ten Japan calendar days, travellers, interests, visit style, walking comfort, pace, transport and spending preferences, and any concise fixed plans. Those inputs define the route shape before attractions are chosen.

  2. Station 2

    Exactly two concepts after both validate

    The product returns exactly two complete, meaningfully different route concepts. Both must pass strict validation before either is displayed. A partial response is a failure.

  3. Station 3

    Exact route selection

    The traveller selects one exact route. Reviewed arrival and departure gateways, ordered regions and bases, and exact night counts are preserved. Changing a route-shaping input invalidates concepts and the selection.

  4. Station 4

    Fast or entitled Detailed/Pro generation

    After final assumptions and a bot check, Fast generation can run without Pro only when exact readiness checks pass. Detailed/Pro generation requires Google sign-in and an active or trialing Pro entitlement before quota reservation or provider work. No real provider, OAuth, or deployment success is claimed.

  5. Station 5

    Strict validation before display or storage

    Provider output is untrusted until strict validation passes. Invalid, partial, or unverified results are not shown or stored. Live facts remain unverified.

Info

What this version can and cannot do

This version can collect planner answers, return two validated route concepts, generate a Fast itinerary when exact readiness checks pass, and save validated itineraries after Google sign-in. Detailed/Pro still requires a Pro entitlement. Private shares, anonymous voting, feedback, skipped stops, shortlist, expense ledger, and saved-day rewrite are locally implemented. Maps, affiliate handoffs, and purchase remain unavailable. No real provider, OAuth, or deployment success is claimed.