vehicles-fleets.md

music/vehicles-fleets.md

Vehicles, Fleets, Flight & Underwater — AAA System Design Proposal

CANON SUBORDINATION — this document is PROPOSAL-TIER: it serves canon and never outranks it.

The canon: the CVD · the T1 foundation docs · the T0 registries (registries/) · the spine

(docs/spine/CH_*.md) · the region pages (_source/02_Tier_2_Region_Pages/). Authority order: docs/DOC_MAP.md § 0.

Canon served (scanned from this document's own citations — widen it by hand where it is thin):

T1_Geo · T1_Trades · T1_Vril · (+1 more tier) · T0_Vehicle_Registry · T0_Vessel · T0_Watercraft_Registry

READ THAT CANON FIRST — open it and derive from it before you build anything from this document.

If this document disagrees with canon, CANON WINS and this document is the defect — fix the

document, never the canon. Nothing here is applied until it is ratified into canon.

Status: PROPOSAL / DESIGN (Opus 4.8, 2026-07-13). Josh expanded the vehicle stub into an ambitious AAA vision — this is the deep, canon-grounded design for the whole vehicle domain: build/upgrade craft across the arc, get fleets, integrate magic/vril, customize onboard, crew with familiars + companions, fly (with dogfights), dive (submarines), and open exploration you could not reach before — all without fast-travel-trivializing the walked geography.

Grounds on a full read of: T1_Vril §2/§3/§5/§6 (the 7+6+1 architecture, the six Vimana modes, the recharge network, §6.5 the flying home-base promotion), T1_Trades §3.10/§5.10/§7.2 (the Trade-10 Fishing & Navigation ladder — the naval sibling), T1_World_Geography §11 (Travel Methods by Arc; the walked-spine + Vimana/Maatherion controlled-traversal locks), docs/proposals/DOMAINS_VEHICLES_AND_ENRICHMENT_BACKLOG.md (the unified Domains frame + the §9b command/deployment addendum + the ³He propulsion physics + the C1–C7 cardinals), docs/proposals/AAA_REARCHITECTURE_BRIEF.md (Layer-model v2, the modern-day myth mandate, win-verb variety, the fun mandate), and the Hard-Lines registry (HL_0033, HL_0049, HL_0082).

The cardinal do-not-invent rule binds: chapter / Component / numerical / naming / hard-line / §17 canon is Josh's. This proposal BUILDS ON the existing specs — it does not reinvent them. Everything that would add a count, a device, a home-base, or touch the walked-geography line is flagged in §5 for Josh.

---

1. Vision

A craft in *Humanity* is not a fast-travel button. It is a spellbook you sail, fly, and dive — a persistent, buildable, inscribable extension of the protagonist and the found-family she gathers. You own one flagship per medium — the Ship (sea), the Vimana (sky, Device 1), and a humble Land Rig (mounts + mobile camp) — and you *grow the same craft across the whole arc*, era by era, the way she grows her own mastery. The magic is not bolted on: the hull is a Trade-9 inscription substrate you rune, the keel takes a socketed vril-orb for propulsion when the wind dies, and the crew are the bonded familiars and significant companions you raised — deployed by the physics of their medium.

The novelty — the thing no AAA does — is the third and fourth axes of exploration. The world's *forward edge stays walked*: you earn every new region on foot and on era-authentic craft, so the geography canon is never trivialized. What the vehicles blow open is the Z-axis (the sky's upper vril-strata; the drowned deep) and the return axis (fast revisit of ground already crossed). Dive the Ship into a sunken city, then shift time through the vril-substrate to walk its living streets before the flood; take the Vimana into the thin high vril-strata and vril-joust a bound storm-titan the family loosed on you. The craft is how the *whole world gains a dimension* the moment you earn it — never how the story skips a step.

This is Layer-model-v2 made physical: L1 the AAA build/fight/explore loop; L1.5 era-authentic craft you actually live aboard (you eat in the galley, you sail the dhow the Swahili coast sailed); L2 the completionist's "max every ship and vehicle" chase and the Reddit-worthy deck-layout builds; L3 the ³He/orgone propulsion metaphysics and the vril-seat-device architecture the rabbit-hole player decodes.

---

2. The design & the loops

2.1 The three flagships — one grammar, era-authentic acquisition

You own one craft per medium and upgrade *that same craft* across the arc (the §6.5 "single Vimana upgraded" principle, generalized). Acquisition is era-locked so the geography stays walked — no steamship in Ch 8, no Vimana before Ch 55.

Ownership is one flagship per medium. Additional watercraft you acquire are not new flagships — they are fleet vessels you crew and dispatch (§2.5). This is the single ownership rule that makes "get fleets" and "geography stays walked" coexist.

2.2 Vril / magic integration — the triad (the heart of the fantasy-craft)

Every flagship is vril-integrated at three registers, each composing with an existing canon system so nothing new is invented at the metaphysics layer:

(a) Propulsion — how it moves.

• *Ship:* mundane sail/oar in early eras — but ocean-substrate perception (Trade-10 field mechanic, unlocks at Adeptus Minor per HL_0017) lets you *read* wind and current as a real navigational edge. Late-game, socket a vril-orb into the keel: becalmed or against the current, channel vril through the keel-orb for vril-assisted propulsion (costs vril, per the depletion physics — never free).
• *Vimana:* the locked canon — a toroidal superconducting disc submerged in superfluid helium-3, coil-driven 0.1–2.0 T at ~20–30 k rpm, the vril-seat device's self-produced EM field yielding self-propulsion + antigravity (and the same rig powers a tractor beam). This is Device 1; the ³He physics is the L2/L3 substrate (§4 firewalls; propagate to SCIENCE_GROUNDING.md).
• *Rig:* bonded mounts (a mount is a familiar/companion persona — Trade-1 crossover); late, a vril-assisted runner/wheel.

(b) Runed hulls — inscription is customization-as-magic (Trade-9). The hull, frames, and sails are an inscription substrate you rune. This makes "customize onboard" a *magic-crafting* activity, not cosmetics. Rune tier gates on Inscription mastery tier (the substrate-perception threshold, Adeptus Minor+). Example runework:

• *Warded hull* — damage resistance (a Blacksmithing armor module + an Inscription ward layered).
• *Silent-running* — the ship reads cold on the vril-signature; evade the Velheim net at sea (composes with the Ch 36–37 surveillance-gap thesis — the ship *is* the gap made playable).
• *Lift / buoyancy* — assists the Vimana's antigravity; assists a ship's shallow-draft.
• *Cold-ward + pressure-ward* — the depth-gate for the deep (§2.4); Metroid-style access tiers.
• *Resonance-sail* — catches vril-wind in high-density atmospheres.

Runes deplete and recharge: dock at a recharge node (obelisk / pyramid / tomb / waterfall / orb, per §5) to recharge the hull's vril-battery. The vehicle domain *consumes the recharge network* — a first real system-level consumer of it.

(c) Orb-socketing — the equipment layer (§5.6, reused). Orbs are canonically dual-function: recharge sources AND slot-system equipment components. A flagship carries socket slots; socketing an orb brings a vril-system online — the vril-lance, the shield-rotor, the deep-lantern, the tractor-beam feed. This reuses the existing orb slot mechanic and invents no device: orbs are portable concentrators, never one of the seven infinite devices (firewall §4).

2.3 Onboard customization — trade-crafted modules on a deck-grid

Customization runs on the unified Domains build grammar (the same grammar as the Personal Dimension): the flagship is a deck-grid; you place trade-crafted modules; crew stations sit on modules. This is the L2 "streaming/Reddit-worthy base building" hook. Every module maps to the trade that crafts it — so the vehicle domain is a *consumer of all ten trades*, deepening trade mastery instead of competing with it:

The deck-grid slot COUNT is deferred to Josh (a count = new numerical canon — §5). The *grammar* (grid + trade-modules + stations) is Opus-lockable now.

2.4 The exploration ladder — how each craft opens what was closed (the Metroidvania spine)

This is the design principle that keeps vehicles AAA *and* canon-safe. Vehicles open the Z-axis and the revisit axis; never the forward story-region edge.

• Rig / mounts → carry-capacity, crew, and the walked world at ground pace. *No new-region skip.*
• Ship → offshore / island / reef sites *within visited regions*; the naval arena; wind/current reading.
• Ship + submersible → the shallow deep (shipwrecks, reefs, coastal drowned sites).
• Vimana Mode 2 (flight, Ch 55) → aerial-only sites, peaks, the upper vril-strata; fast revisit (Mode 1 — *previously-visited locations only*, per §6.1).
• Vimana Mode 3 (underwater, Ch 59 first / Ch 64 peak) → the deep: trenches, sunken cities, Doggerland (Thread 4 Flood Memory).
• Vimana Mode 5 (dimensional, Ch 66) → the Atlantis threshold (endgame, canon-locked).

Each rung gates the *next axis*, never the forward edge of the story. New regions stay walked. Higher vril-strata are *thinner* (the depletion physics run vertically too) — so altitude and depth are risk gradients, not free real estate.

The deep loop (submarine / underwater). Deeper = darker, higher pressure — but the deep concentrates ancient vril (tombs concentrate deep-time vril; drowned ruins are vril-dense). So the deep is *dangerous but vril-rich* — a clean risk/reward gradient gated by the cold-ward + pressure-ward hull tiers. And the canon time-fluctuation composition is the novel payoff: at a drowned site, the astral/time mechanic lets you perceive it as the thriving society it was (CVD, verbatim: "navigate their drowned ruins and, through time-fluctuation, experiences them as thriving societies"). Descend to the ruin (present, drowned) → shift to the past (thriving) → restore the site in the past and it becomes a stronger vril-node in the present (the backlog §4 capacity-progression, wired into the deep). The deep carries marquee bestiary — each culture's OWN sea-monster (Jörmungandr, Tiamat's brood, Naga Padoha, Olokun/Nommo) via the environmental-boss protocol.

2.5 Fleets — the dispatch-and-set-piece model (the hard problem, solved)

Josh wants fleets; the firewall is "don't fast-travel-trivialize walked geography." The solution: the fleet is a dispatch/logistics + set-piece layer, not a second controllable armada, and it is spatially bounded to already-walked waters.

• You pilot one flagship Ship. Additional watercraft become fleet vessels you crew and dispatch — escorts, supply-runners, scout-cutters, a fishing fleet.
• They run off-screen expeditions over time across already-walked routes only (never first-discovery): gather resources, scout revisit-sites, run intel, intercept Velheim shipping (thematically you build a *counter-network* to the family's 5,000-year extraction fleet — the opposite of a slaver economy).
• They can be summoned to a set-piece: in a naval boss battle your dispatched escorts arrive as a scripted fleet-action, commanded through a light tactical/gambit layer (position, focus-fire, screen) — the "command a group" fantasy delivered as a set-piece + strategy layer, not a fully-piloted armada and not a fast-travel map.
• Gated by crew (significant bonded companions, never a mercenary hire-pool — the §9b anti-mercenary guardrail) and by home-port infrastructure (the Trade-10 homes Ch 8 / Ch 56 become your admiralty).

The load-bearing firewall: the fleet cannot move the protagonist to an unvisited region. New ground is crossed only on the walked spine. The fleet lives in the backtrack/consolidation space. Fleet vessel count cap = Josh (numerical — §5). Care firewall C7 reaffirmed: no cargo-margin / raider-optimization fleet loop in Ch 33–35 slave-trade waters — in those waters the only frame is the §5.5 assimilation-integrity choice (participate / subvert / refuse), never tonnage.

2.6 Land — mobility without fast-travel (the walked-geography guardian)

Land is the medium most in tension with the geography hard line, so it is deliberately the *humblest* flagship. The Rig is a mobile expedition camp + era-authentic mounts (T1_Geo §11: horse Ch 22, camel Ch 32, reindeer-sled Ch 29, river-craft) — it carries crew and cargo and lets you *live on the road*, but it moves at ground pace through the walked world. It does not skip regions. Modern-era chapters (Ch 39+) grant an actual vehicle, but region-arrival stays gated by the spine. Whether "own one per medium" includes a drivable land craft at all is a Josh fork (§5, F4) — it touches the walked-geography line most directly.

2.7 Crew — familiars & companions (deep; extends the §9b addendum)

The crew is the found-family, and the ship is where the "fun AARPG, a pleasure to travel with" tone lives — banter, galley scenes, festivals aboard.

Deployment-by-medium + speed (the §9b realism matrix, extended):

• Water familiars fight in/around the hull at sea; on the Vimana (air) they duck into the Personal Dimension (their "pocket") and re-emerge over water. On the sub they scout ahead into depth/pressure the craft can't yet survive and surface intel (a dive-point, a threat, a vril-node) — a beautiful, novel use of the bonded koi/turtle.
• Flying familiars wheel around a slow/stalled ship or grounded rig; can't keep pace at speed → retreat to the Dimension; on the Vimana they thrive as escort wings in dogfights.
• Ground familiars ride and guard the Ship/Rig; retreat at high speed / in air.

This gives the Personal Dimension a live combat function and makes each medium distinct.

Stations (persona + relationship gated, never progression-gating): helm/navigator (Trade-10), lookout (perception persona — spots sites/threats/dive-points early), gunner (works the vril-lance / harpoon in set-pieces), boatswain-engineer (Trade-8 — auto-repairs hull mid-fight), cook (Trade-7 — morale/buff), menagerie-keeper (Trade-1), rigger-inscriber (Trade-9 — recharges wards mid-battle). Which station an entity can hold is a function of its persona + your relationship (the opportunity engine — a distant companion gives blunter options, a deep bond the sophisticated ones). Dispatch (§2.5, §9b(d)): send a known companion off-ship at the real cost of their absence and a relationship dimension — never a coin for a stranger.

2.8 The aerial dogfight loop (the Vimana's signature set-piece)

The modern-day myth mandate *requires* Velheim to field supernatural aerial assets (bound spirits, forced constructs with teeth, hunter-operatives). So dogfights are canon-supported. The Vimana is not a jet — it's a supernatural vril-craft in the celestial-vehicle register, so the dogfight is a vril-jousting positional duel, not twitchy flak:

• Altitude = vril-strata density. Climb into thin high vril and your systems strain (the depletion physics, vertical) — a positioning tension.
• Overdraw the ³He cryo-rig and the antigravity disc destabilizes → a vent/cooldown → the core resource tension.
• Rotate the runed shields, fire vril-lances, and use the tractor-beam to grapple an enemy craft off-course *or pull a falling ally back*.
• Crew stations matter: gunner works the lance, engineer nurses the cryo-rig, a flying-familiar wings as escort.
• Enemies: Velheim forced-construct fliers, bound storm-spirits, a hunter-operative's craft; mythological aerial beings where canon supports (Thunderbird SQ, roc, Garuda-echoes — care-tiered).
• The peak set-piece: one unforgettable aerial boss (a Velheim sky-fortress or a loosed storm-titan) — spectacle rendered, not summarized (the AAA "one set-piece per chapter" move).

2.9 Progression & meta

• Vril-site capacity network (backlog §4): dock at a vril-node and restore it → a permanent max-vril / max-hull-battery increase (Zelda-shrine meta; gate the biggest gains to the Component-11 nine + a curated set so depletion-as-difficulty is never trivialized).
• Trade ladders gate systems: Trade-10 gates ship systems + the sounding rig; Trade-9 gates rune tier; Trade-8 gates the sub / cryo / tractor rigs. The vehicle domain *pulls* trade progression.
• L2 completionist: "max upgrades on all sea ships and Vimana flying ships and vehicles" is named verbatim in Layer-model-v2 — so full-upgrade + best-layout is a first-class L2 chase.

---

3. Alternatives considered (the genuine forks)

A. Fleet model. (a) *Dispatch + set-piece only* — RECOMMENDED: delivers the commander fantasy, preserves walked geography, anti-mercenary. (b) *Light-tactical controllable RTS armada* — more spectacle, but risks a fast-travel map-painter and an idle-game optimization loop that collides with C7. (c) *No fleet, single ship* — safest, but leaves Josh's explicit "get fleets" on the table. → (a).

B. Aerial combat model. (a) *Positional-tactical + free-flight exploration* — RECOMMENDED: fits the vril-resource identity, solo-dev-feasible, free-flight opens the Z-axis. (b) *Full arcade flight-sim* — genre-mismatched (this is an AARPG, not Ace Combat) and a build-risk. (c) *On-rails set-pieces only* — cheap but not "fun AARPG." → (a).

C. Submarine scope. (a) *Ship submersible-promotion + Vimana Mode 3* — RECOMMENDED: the drowned-city time-shift loop is too strong to reserve to the Vimana's narrow late window; a ship submersible opens the shallow deep across the mid-arc. (b) *Vimana Mode 3 only* — the backlog's minimum; leaves the mid-arc deep empty. (c) *Diving-bell tether only* — a taste, no exploration loop. → (a), flagged (touches whether a new vehicle-class is implied — §5 F3).

D. Land ownership. (a) *Mounts + mobile camp, no drivable pre-modern land craft* — RECOMMENDED: protects the walked line. (b) *Full owned land vehicle per medium* — clean symmetry but the biggest fast-travel risk. → (a), but this is a Josh fork (§5 F4).

---

4. Canon composition & firewalls

Composes cleanly with: the 7+6+1 architecture (Vimana = Device 1, untouched); the six Vimana modes (§6.1 — the exploration ladder just *organizes* them); the recharge network (§5 — the vehicle domain is its first system-level consumer); Trade-9 Inscription (runed hulls), Trade-10 (the naval ladder), Trade-8 (the rigs), and all ten trades (modules); orbs (§5.6 dual-function, reused); the Personal Dimension (the crew "pocket" + the §9b deployment matrix); the entity-persona + opportunity engine (stations/dispatch); the three endings + integrity (integrity-visible hull substrate; recharge responsiveness per §5.7); the modern-day myth mandate (Velheim aerial/naval supernatural assets); win-verb variety (sail / dive / dogfight / command / survive — no verb runs consecutive chapters).

Firewalls (hard):

1. NEVER "Vessel." "Vessel" is the House-of-Velheim antagonist-agent term. Use Watercraft (system/registry) / Ship (player-facing). A T0_Vessel_* registry would guarantee a hallucination collision (C1).

2. 7+6+1 locked; no 8th device. The Ship and Rig are vehicle/encounter classes, never devices. Socketed orbs are portable concentrators, not the seven infinite devices (C2).

3. The Vimana is one craft upgraded (§6.5), never a fleet, never a second airborne device.

4. Walked geography is sacred. Vehicles open the Z-axis (sky/deep) + the revisit axis, NEVER first-discovery of a new story region. Vimana Mode 1 = previously-visited locations only. The fleet cannot move the protagonist to unvisited ground.

5. HL_0033 / HL_0082 untouched. Vehicles are not trades and not home-bases; a ship is not a "mobile compound." The 10-trades × 2-homes lock and the four-compound / two-field-trade split are untouched.

6. HL_0049 mode-variety. Naval / aerial / deep are encounter arenas that host the seven combat modes, never a new dominant_combat_mode value — a naval set-piece logs e.g. direct or vril_management with encounter-category = naval. Do not corrupt the mode-variety scatter.

7. Care (C7). No merchant / cargo / raider optimization loop in Ch 33–35 slave-trade waters — assimilation-integrity choice only.

8. Anti-fringe. The ³He propulsion is grounded-speculative (real components, one sanctioned antigravity leap), never fringe; the Vril-Society / Orsic occult layer is held at the HL_0109 artistic-bridge register with NO diffusionism; the Vimana is supernatural (vril), never an "ancient aircraft"; 33.33°S is a felt vril-resonance node, never asserted real-world "significance."

9. Reveal ladder. No pre-Ch-76 Grand Sage hints; the family-pattern is not player-legible until ~Ch 38+ — dogfights against Velheim assets in the modern arc are fine, but keep the "who-frame" discipline (no agent-noun the player can't yet know).

---

5. Forks for Josh (options + recommendation)

• F1 — VH_ / Watercraft registries as structure. Approve T0_Vehicle_Registry (VH_ IDs — all three mediums, fleet vessels, and modules as persona-bearing entities) + T0_Watercraft_Registry as live-only structural registries (ENTITY_PERSONA precedent), NOT world-canon. *Rec: approve as structure.* No module/vessel COUNTS enter until F2/F5 rule them.
• F2 — deck-grid slot COUNT + module COUNT. A count is new numerical canon. Options: (a) fixed per-medium slot count; (b) upgrade-expandable count; (c) defer to Fable tuning under a Josh-set ceiling. *Rec: (b) with a Josh-set ceiling — expandable feels premium, a ceiling protects balance.*
• F3 — the Ship submersible. Does the Ship get a submersible promotion (opening the mid-arc shallow deep), or is all underwater reserved to Vimana Mode 3? *Rec: yes to the submersible (Alt-C(a)) — the drowned-city time-shift loop is the strongest single loop in the bundle and should not wait for the narrow Ch 59–64 window.*
• F4 — land medium ownership. Is there an owned Land flagship, or is land = mounts + mobile camp + the walked spine only? *Rec: mounts + mobile camp pre-modern; a real vehicle modern-era only, region-arrival still spine-gated (Alt-D(a)).* This is the fork that touches the walked-geography hard line most directly.
• F5 — fleet vessel count cap + "fleet = canon?" Does the fleet enter canon, and with what cap? *Rec: yes, dispatch-and-set-piece model (Alt-A(a)), cap set by Josh — a small, meaningful number (bonded-crew-limited), never an unbounded armada.*
• F6 — §6.5 Vimana home-base module/upgrade PARAMETERS. T1_Vril §6 explicitly reserves these for Josh ("base and module upgrade parameters pending authorial assignment"). This proposal supplies the *grammar*; the parameters are his to author.
• F7 — confirm the standing cardinals. C1 (Watercraft/Ship, never Vessel), C2 (not the 8th device), C4 (Ch 37 — recommend KEEP the surveillance-gap, do not flip to a kinetic Velheim fleet — it would contradict the authored Ch 36–37 thesis), C6/C7. *Rec: confirm all; keep Ch 37.* (Note: C3 — the Trade-10 modern-home "Pacific Northwest" stale ref — is already fixed to Arctic Ch 56 in the live T1_Trades §3.10; no action.)

---

6. Opus-can-spec-now vs Fable-5 handoff

Opus can lock this session (design that composes with canon, invents no count/device/home-base):

• The unified three-medium flagship grammar (§2.1) + the anti-trivialize principle (Z-axis + revisit, never the forward edge) — §2.4.
• The vril-integration triad (propulsion / runed-hull-inscription / orb-socketing) — §2.2, composing with Trade-9, orb §5.6, the recharge network.
• The module→trade mapping (which trade crafts what) — §2.3 (grammar only; counts to F2).
• The crew-station + deployment-by-medium matrix (extends §9b) — §2.7.
• The exploration ladder mapped onto the existing six Vimana modes — §2.4 (organizes canon, invents nothing).
• The fleet-as-dispatch design shape + the aerial dogfight loop + the deep/time-shift loop as designed loops — §2.5/§2.8/§2.4 (counts/caps to Josh).
• The VH_ registry field schema (structure) — pending F1 approval.
• Reaffirm the naming firewall (Watercraft/Ship, never Vessel).

Fable-5 handoff (deep implementation / final prose / tuning, downstream):

• Tuning numbers: upgrade costs, the deck-slot count once F2 rules the ceiling, dogfight resource curves (cryo-vent thresholds, vril-strata strain), depth-pressure ward thresholds, fleet-dispatch timers.
• Grounding prose: the ³He toroidal-superconductor propulsion into docs/SCIENCE_GROUNDING.md (grounded-speculative, physicist-pleasing, one sanctioned antigravity leap); the Maria Orsic / Vril-Society occult layer into docs/ESOTERIC_GROUNDING.md at the HL_0109 artistic-bridge register (anti-fringe: no diffusionism).
• Per-chapter light spine hooks: craft manifests + traversal Key-site anchors woven at the schema's natural points (Mechanical-anchors block 18, Asset-anchors block 17) during the re-cascade — born-in for unbuilt water chapters, two-line anchor touches for built ones at their next RR.
• Per-culture encounter design: each culture's OWN sea-monster (Frame-A) and aerial being via the environmental-boss protocol (bestiary-restoration mandate).
• Set-piece prose: the signature aerial-boss dogfight and the drowned-city time-shift descent, rendered as scene-time spectacle.
• Scatter discipline: log naval/aerial/deep set-pieces as encounter-category, NEVER a new dominant_combat_mode value (HL_0049).

---

7. The AAA hook

Your craft is a spellbook you sail. You inscribe its hull with Trade-9 runes, socket its keel with a vril-orb, and crew it with the bonded creatures you raised — then you take it where the map had no floor and no ceiling: dive a drowned city and shift time to walk its living streets before the flood, or climb into the thin high vril and vril-joust a storm-titan the family loosed on you — while the world's forward edge stays yours to walk, one earned region at a time.

---

Follow-up (2026-07-13): the Mothership model — one transforming flagship that carries and deploys sub-craft

Josh's expansion: "wouldn't it be cooler to have different boats, and in our larger/most-upgraded ones a submarine and other vehicles? Think No Man's Sky; also One Piece Luffy's ship with that mechanic that makes it into so many things." The ask is a modular MOTHERSHIP with a dock/hangar (Thousand-Sunny Soldier-Dock-System / No Man's Sky freighter) that CARRIES and DEPLOYS sub-craft — a submarine, a fast skiff, a flying craft, a land rig — and can TRANSFORM/reconfigure (the Sunny's paddle / Coup-de-Burst). This resolves it against §1–§7 and the two hard locks (7+6+1 Vimana; walked geography).

The one design collision, named first

The naive reading — "the most-upgraded ship becomes a mothership that carries a submarine, a skiff, a flying craft, and a land rig" — hits two canon walls the moment it touches the air and the sky-flagship:

• Geography §11 lock: the mortal-world modern arc (Ch 39–54) is expressly "walking, sea, no flight." Flight arrives only at Ch 55 with the Vimana. A flying sub-craft launched from the Ship's hangar in, say, Ch 40 would break the no-flight canon outright.
• 7+6+1 lock: the Vimana is Device 1 of 7, a single craft upgraded (§6.5), "never a fleet, never a second airborne device." It can therefore never be a hangar toy the Ship "owns," and a separate powered flyer risks reading as an eighth-device / second air-craft.

So the mothership model is adopted — but the "flying craft" is not a pre-Ch-55 hangar tender, and the sky-flagship is not absorbed as cargo. Both are handled below.

The definitive model — Sunny-hull + Soldier-Dock + a docking peer-flagship

1. One persistent, TRANSFORMING flagship mothership (the Sunny principle). The current "own one Ship and upgrade that same hull across the arc" (§2.1) is kept and promoted: the Ship is a mothership-hub — a single hull you grow and refit era by era (dugout → dhow Ch 8 → caravel Ch 33–38 → research vessel Ch 39+ → submersible-capable mothership, late). It does not become many owned boats; it transforms between configurations, which is exactly the "one ship, so many things" mechanic Josh means:

• Cruise config (sail/oar, era-authentic — the walked-spine traveller).
• Battle config — guns/ram/harpoon run out, warded hull engaged (§2.3 Blacksmithing + §2.2b Inscription).
• Dive config — seals, dive-planes, and the cold-ward + pressure-ward hull tiers engage (§2.4 depth gate); the mothership itself submerges where its ward-tier allows.
• Anchored-base config — the deck-grid unfolds into the mobile home-base (galley, sick-bay, menagerie; §2.3).

The transformation is magic, not machinery: the vril-inscribed hull (Trade-9) reshapes under a Trade-8/Trade-9 co-driven reconfiguration — runes redraw the frame. This is the Sunny's paddle/animation register done as vril-craft.

2. The Soldier-Dock hangar that carries and DEPLOYS collectible sub-craft (this is the new layer). The mothership carries a dock/hangar (an Engineering + Tailoring deck-module on the §2.3 grid) that berths and launches sub-craft — small, purpose-built tenders, never flagships:

• Submersible pod — the star sub-craft; opens the shallow-deep + the drowned-city time-shift loop (§2.4) *locally*, gated by ward-tier. (This subsumes the §2.4 "Ship + submersible" — the submersible is now a *deployed pod*, cleaner than promoting the whole hull every dive.)
• Fast skiff / dinghy — the nimble surface/shallow/river tender (river-craft canon Ch 11/42/50); the away-team's quick insertion craft.
• Deployable land-rig rover — the Land Rig (§2.6) folded in as a carried tender the mothership drops at a coast or river mouth for inland local excursions at ground pace. (The Rig's era-authentic *mounts* layer stays separate and walked; only the *rover* becomes a carried tender.)
• Vril-launch flyer — LATE-ARC ONLY (Ch 55+). The one flying sub-craft Josh wants exists only after the Vimana era opens flight, as a short-range vril-launch/glider tender that never becomes free intercontinental flight. Before Ch 55 the mothership's "air" is lookout-familiars only (§2.7). This keeps the no-flight canon intact.

Sub-craft are LOCAL limbs, and that is the walked-geography firewall. Every sub-craft launches from the mothership's current position and must return to it; none can carry the protagonist to a new story region. The mothership itself still travels era-authentically along the walked spine (Geo §11 unchanged). Sub-craft are for local exploration / combat / set-pieces — dive this reef, run that river delta, rove this coast — never first-discovery of onward ground.

3. Where "different boats / collect-swap" (the No Man's Sky fantasy) lives — the sub-craft tier, not the flagship. Josh asked whether the player can own *different hulls*. Answer: the collection fantasy is satisfied at the sub-craft tier, not by swapping flagships. You collect culture-specific tenders across the arc — a Swahili mtepe skiff, a Norse faering, an Austronesian outrigger, a modern research submersible — and berth them in the Soldier-Dock, each with a role and a feel. So Josh gets *both* references cleanly: the Sunny = the single transforming flagship + its Soldier-Dock; No Man's Sky = the collectible tender roster you dock and swap. The flagship stays singular (protecting the "one grown craft" identity and the upgrade-arc); the variety-and-collection itch is scratched below it. (A full collect/swap of *flagship hulls* is offered as the losing fork F8 — it dilutes hull identity and adds a hull-count = numerical canon.)

4. The Coup-de-Burst analog — a vril-surge maneuver, not a map skip. The Sunny's Coup de Burst is a battle maneuver, not a world-map fast-travel, and that distinction is the whole safety of importing it. The mothership's version: channel a socketed keel-orb for a one-shot vril-burst — breach a blockade, crash-dive to a trench mouth, leap a reef gap, break contact from a Velheim net at sea. It is costly (depletion physics, §2.2a — never free), it is a tactical scene move inside an already-reached area, and it cannot cross to unvisited ground. It is spectacle and escape/entry, not traversal.

5. The Vimana is a docking PEER-FLAGSHIP, never a tender (the 7+6+1 firewall, honored fully). "The flagship carries the others" gets its fullest expression at the late-arc convergence (Ch 55+): the Vimana can dock with / launch from the sea-mothership, so the two flagships become a combined sea-air base — a carrier-and-its-craft tableau, the biggest "your fleet is one machine now" beat in the game. But the Vimana remains a single sovereign upgraded Device-1 craft: docking is a staging / base-scene affordance, not a capability change, not a new operational mode, not an eighth device, and the Vimana is never "owned" as hangar cargo. It berths as a peer and departs as a peer.

6. Crew — the away-team fantasy (extends §2.7). When a sub-craft launches, a bonded familiar or companion pilots it while a skeleton bonded crew holds the mothership (helm, and an engineer nursing the reconfiguration/cryo rig). This turns §2.7's deployment-by-medium matrix into a live away-team system: the water-familiar or a Trade-10 companion takes the submersible into pressure the mothership can't yet survive and surfaces intel; a scout-persona takes the skiff up a delta; a flying-familiar or the aerial-persona flies the late-arc launch as escort. Persona + relationship shape *which* entity crews *which* craft and *how well* (the opportunity engine) — never progression-gating (multiple viable crews; the no-dead-end rule holds).

Reconciling "own one per medium that upgrades" — the exact restatement

The old rule stands, restated for the mothership: you own one grown flagship per medium — but the sea flagship is now a transforming mothership-hub that carries collectible sub-craft tenders (submersible, skiff, land-rover, late-arc flyer) as its deployed limbs, and the sky flagship (Vimana) is a sovereign peer that can dock with it. The Land Rig ceases to be a third co-equal flagship — its rover folds into the mothership's hangar as a tender, while its walked-world mounts remain the ground-pace layer. Net: one mothership-hub + its carried tenders + a docking peer-flagship, not three separate boats and not a swappable armada. "Get fleets" (the §2.5 dispatch layer) is unchanged and still lives strictly in already-walked waters.

The AAA hook (mothership register)

One inscribed hull that unfolds into a fleet. You grow a single vril-runed mothership, and at the pull of a keel-orb it reconfigures — guns run out, dive-planes fold down, the deck-grid blossoms into a home — while its Soldier-Dock launches the submarine, the skiff, and the shore-rover you collected from every coast you assimilated into, each crewed by a beast or companion you raised. Late, the sky-craft itself berths on your deck and the sea and the air become one machine — and not once does any of it skip the ground you have not yet walked.

New / updated firewalls (add to §4)

• F-a — no-flight-before-Ch-55 (NEW, load-bearing). The flying sub-craft is a Ch 55+ tender only; pre-Ch-55 mothership "air" = lookout-familiars only. A hangar flyer in the Ch 39–54 modern arc violates Geo §11 ("no flight") — hard no.
• F-b — the Vimana docks, it is not carried. Vimana↔mothership docking is a late-arc staging/base scene; it changes no Vimana canon (no new mode §6.1, no device change, not an eighth device, never hangar cargo). Reaffirms firewalls §4.2/§4.3.
• F-c — sub-craft are local limbs. Every tender launches from and returns to the mothership's current position; none reaches an unvisited region. The Coup-de-Burst is a tactical scene maneuver, never a map skip. Reaffirms §4.4.
• F-d — never "Vessel." Mothership / Ship / Watercraft / sub-craft / tender. Reaffirms §4.1.
• Care C7 (§4.7), HL_0049 mode-variety (§4.6), HL_0033 homes (§4.5) all untouched — the dock is an encounter/base module, not a trade home-base or a device; sub-craft socket orbs (portable concentrators, §4.2), never devices.

New forks for Josh (extend §5)

• F8 — hull model. (a) *Single transforming mothership + collectible SUB-CRAFT tenders* — RECOMMENDED (delivers both the Sunny and the No Man's Sky fantasies; protects the one-grown-flagship identity and the upgrade-arc). (b) *Collect/swap full FLAGSHIP hulls* — more NMS-literal, but dilutes hull identity and adds a hull-count = numerical canon. → (a).
• F9 — sub-craft roster + hangar-berth COUNT (numerical). Rec: expandable-with-a-Josh-set-ceiling (mirrors F2) — collecting tenders is a premium L2 chase; a ceiling protects balance.
• F10 — the flying sub-craft. Confirm it is Ch 55+ vril-launch only (Rec — the sole no-flight-safe form), or drop a separate flyer entirely and let the Vimana be the only air. Rec: confirm Ch 55+ launch tender.
• F11 — Vimana↔mothership docking. Approve the late-arc dock as a staging/base-scene + set-piece affordance with zero Vimana-canon change (no mode, no device). Rec: approve as scene/base only.
• F12 — Land Rig fold-in. Fold the Rig's rover into the mothership as a carried tender (Rec) while keeping its walked-world mounts standalone — vs. keeping the Rig a third co-equal flagship. Rec: fold the rover in; keep mounts walked.

Generated by harness/site/structure_site.py — the URL path is the repo path. review root