Justin Trip Defaults
Purpose
Capture reusable Justin-centered Japan trip defaults so individual trip packages only need to document trip-specific overrides.
When to Use
Use this page before creating a new trip package, booking lodging, choosing day anchors, or deciding whether a detail belongs in a reusable travel page or a specific trip folder.
Planning Defaults
- Plan days around one or two strong anchors, a nearby cluster, flexible food, and at least one fallback.
- Leave enough empty space for wandering, browsing, snacks, cafes, and decompression.
- Avoid hour-by-hour optimization unless a train, flight, reservation, or ticket requires it.
- Keep lodging moves low. Add a move only when it clearly removes more friction than it creates.
- Protect arrival days, transfer days, and departure days from heavy sightseeing.
- Put weather-sensitive outdoor anchors early enough to allow a swap.
Lodging Defaults
- AC is required for summer trips.
- Lodging should provide enough space to drop bags, decompress, and sleep well; a desk is a bonus, not a requirement.
- Airbnb is acceptable when it improves space, privacy, neighborhood access, or price, but hotels are useful for luggage forwarding, late check-in, and airport-departure certainty.
- Stairs are acceptable when traveling light; do not over-prioritize ground-floor access for backpack-only trips.
- Prefer locations that reduce the hardest transfer of the block, especially airport, Shinkansen, or major day-trip departures.
- Confirm exact address, check-in method, late arrival rules, trash rules, Wi-Fi, AC, and emergency contact before relying on a stay.
Laundry And Bathing Defaults
- Local laundromats are acceptable and often preferable to weak in-unit machines.
- In-unit laundry or hotel laundry is a bonus, not a booking requirement.
- Plan one or two laundry windows on longer trips rather than carrying too much clothing.
- Public bath houses, sento, and public onsen are not default activities when tattoos or privacy make them complicated.
- Private in-room or private-reservable baths are acceptable when the lodging supports them.
Transportation Defaults
- Plan airport transfers backward from flight time, not from the first convenient train.
- For international departures, target at least a two-hour airport buffer unless a specific trip says otherwise.
- Do not make an international departure day depend on a long same-day city-to-airport transfer when a previous-night positioning stay is reasonable.
- Use the simplest route on arrival nights and luggage-heavy transfer days.
- Keep passports, medications, chargers, one-night clothes, and valuables with Justin even when luggage forwarding is used.
- Verify live train, bus, airport, and disruption details close to the travel date.
Food And Allergy Defaults
- Avoid single-point restaurant dependencies.
- Use convenience stores, bakeries, station food, food halls, and simple neighborhood meals as friction reducers.
- Build restaurant shortlists by area after the day geography is clear.
- Keep tree nut allergy phrasing ready and verify ingredients and cross-contact risk before treating a restaurant as safe.
- Keep non-seafood and low-risk backups near sushi or seafood-heavy plans.
- Do not let a restaurant reservation create transfer stress unless the meal is a deliberate trip anchor.
Verification Defaults
- Drift-sensitive facts need a current check: hours, closures, reservation rules, weather, train schedules, bus schedules, airport terminals, theater schedules, and live lodging instructions.
- Filed PDFs, screenshots, and notes are evidence, but live vendor accounts and official operator pages control operational truth.
- Keep open questions explicit until they are actually decided.
- When updating a dated day page close enough for a useful forecast, proactively pull the latest weather for the relevant area and fold the result into the day plan. Weather should not require a separate user ask.
- Use current weather to adjust route order, transit mode, outdoor/indoor emphasis, luggage handling, and fallback choices, especially for transfer days, mountain/nature days, and summer rain/heat conditions.
Gotchas
- Do not duplicate these defaults inside trip packages. Trip pages should record overrides, locked bookings, companion-specific needs, and day-specific decisions.
- A companion’s preferences belong in the relevant trip package unless they become a durable default for future trips.
- If a trip starts serving multiple traveler groups or route identities, split it into self-contained packages.