Skip to content
Dead Water In development

Voyage ledger

How far from the complete game

The destination used here is the roadmap: sections A, B and C at their stated exit tests, with human-acceptance passes recorded and the shared-world deployment decision taken and executed. Nothing in this ledger is a shipping promise.

As of 2026-09-30 · recomputed from the ledger rows on every site build

Overall 79%

63 scored items · 1 owner-gated, excluded from the mean

  • verified
  • awaiting humans
  • partial
  • open
  • owner gate

Counting rule: verified counts fully, items waiting only on human testing count 0.9, partial slices count 0.5, open work counts zero, and items gated on an owner decision are excluded from the mean and listed under their own heading. A slice that exists is not a feature that ships.

Section A

Local gameplay and demo

In harbor. The boat works; strangers have not sailed it yet.

81%

  1. A0

    Heat-game baseline awaiting humans

    Day/night, night searchlights, helicopter, customs impound implemented through v0.8.0. Human stealth and balance passes remain.

    v0.8.0-prototype
  2. A1

    Port intel contact verified

    Purchased, time-stamped patrol information with readable freshness. Quote, save, duplicate, expiry and guest-ownership tests pass.

    v0.9.0-prototype
  3. A2

    Boat loadout foundation verified

    Hull profiles, cargo placement, sensors and crew-station bindings. Solo, save/reload and co-op regressions pass.

    v0.10.0-prototype
  4. A3

    Three-boat roster with dealer awaiting humans

    Go-fast, fishing launch and RHIB with saved ownership, distinct handling, fuel, cargo and a 3D showroom. Human feel and balance testing remains.

    v0.11.0-prototype
  5. A3b

    2003 Liberty 42 Express partial

    Playable fourth hull with custom exterior, diesel loops and trolling. Cabin/upper helm, animated shaft gear, exact instruments and per-vessel tanks remain.

    LIBERTY-VALIDATION.md
  6. A4

    La Marea port meeting place partial

    Custom indoor intel and cargo broker with protected transactions and 24 solo / four crew-peer regressions. Original dock services remain.

    v0.12.0-prototype
  7. A5

    Demo polish and playtest package awaiting humans

    Custom engine/water audio, session guide and hashed packaging through v0.13.0. Human listening, boat feel, crew coordination and route balance remain open.

    v0.13.0-prototype

Section B

Shared-world foundations

Open water. Sixteen-to-thirty-two client cohorts verified locally; nothing is deployed.

95%

  1. B1a

    Hull construction and physics separation verified

    Reusable hull profiles and a graphics-free native three-hull physics check.

    v0.14.0-prototype
  2. B1b

    Shared static coast collision verified

    Coast collision and visual population verified headless and playable.

    v0.15.0-prototype
  3. B1c

    Explicit-time run state verified

    Transfer, repair and loss rules plus background timers separated from presentation and persistence IO.

    v0.16.0-prototype
  4. B1d

    Beam and perception separation verified

    Explicit beam state and graphics-independent surface/air perception with native terrain occlusion.

    v0.17.0-prototype
  5. B1e

    Patrol decision separation verified

    Explicit-time surface patrol suspicion, memory, boarding and route movement verified headlessly.

    v0.18.0-prototype
  6. B1f

    Aircraft decision separation verified

    Aircraft memory, orbit, flight and beam decisions independent of presentation, with native replay.

    v0.19.0-prototype
  7. B1g

    Headless world region verified

    An owned in-memory region combining physics, collision, run rules, patrols, beams and a world clock that survives restart.

    v0.20.0-prototype
  8. B2a

    Six identities, three crews verified

    In-memory players command three native vessels through revocable seat leases and bounded commands.

    v0.21.0-prototype
  9. B2b

    Real loopback clients verified

    Six real clients on three server vessels; disconnect/rejoin verifies neutral helms and world continuation.

    v0.22.0-prototype
  10. B2c

    Server-owned dock loop verified

    Dock walking with a usable contract/load/sale/deposit loop, exact-quote services and chart plotting.

    SHARED-RUNS-VALIDATION.md
  11. B2d

    Port preparation verified

    Server-approved appearance, boatyard inspect, refits, workshop upgrades and paid dated intel with replay guards.

    PORT-PREPARATION-VALIDATION.md
  12. B2e

    Shared effects and audio verified

    Shared foam trails, spatial engine layers and water ambience with native audio-output checks.

    SHARED-EFFECTS-VALIDATION.md
  13. B2f

    Checkpoint IO hardening verified

    Bounded busy-file checkpoint retries and failed-purchase no-replay checks. Hardens local saves; not durable shared accounts.

    CHECKPOINT-IO-VALIDATION.md
  14. B3a

    Authenticated identities verified

    SQLite-backed identities, stable crew/vessel bindings and transactional appearance/receipts across six clients.

    ACCOUNTS-VALIDATION.md
  15. B3b

    Account ledgers verified

    Captain-owned ledgers, atomic financial receipts and durable journals through crash/restart. Physical world recovery remains incomplete; boats restart at reserved berths.

    FINANCIAL-VALIDATION.md
  16. B4a

    Interest management verified

    Server-selected nearby groups with boundary hysteresis and atomic appearance baselines.

    INTEREST-VALIDATION.md
  17. B4b

    Remote motion interpolation verified

    Timestamped pose interpolation, recovery epochs and same-tick publication suppression.

    MOTION-VALIDATION.md
  18. B4c

    Own-helm prediction verified

    Bounded prediction with applied-input acknowledgements and authoritative rebase/replay.

    PREDICTION-VALIDATION.md
  19. B4d

    Spatial index batching verified

    Per-batch spatial index with cell-edge visibility differential-tested against full scans.

    SPATIAL-VALIDATION.md
  20. B4e

    Law interest records verified

    Per-observer surface/air interest with optional law pose records.

    LAW-INTEREST-VALIDATION.md
  21. B4f

    Reliable baselines verified

    Reliable baselines beside bounded replaceable motion chunks with faulted checks.

    DELIVERY-VALIDATION.md
  22. B4g

    UDP fault emulation verified

    Loopback UDP faults, bounded pre-welcome retries and durable restart checks.

    TRANSPORT-VALIDATION.md
  23. B4h

    Moving-boat collision proxies verified

    Bounded collision proxies with independent native contact/baseline replay.

    CONTACT-VALIDATION.md
  24. B4i

    Socket-contact measurement verified

    Dynamic socket-contact measurements and onboard crew pose authority.

    SOCKET-CONTACT-VALIDATION.md
  25. B4j

    Patrol collision motion verified

    Bounded patrol collision motion estimates with native verification.

    PATROL-PREDICTION-VALIDATION.md
  26. B4k

    Compact motion payloads verified

    Lossless indexed motion against reliable rosters with walking-payload checks.

    COMPACT-MOTION-VALIDATION.md
  27. B5a

    Sixteen-client load verified

    Initial 16-client/eight-boat local load under normal and two faulted cohorts.

    LOAD-VALIDATION.md
  28. B5b

    Five-minute soaks verified

    Normal/faulted soaks with four rolling reconnect waves and matched-roster memory evidence.

    SOAK-VALIDATION.md
  29. B5c

    Sixteen durable accounts verified

    Paired durable rosters through sixteen with migration and crash-restart audits.

    POPULATION-VALIDATION.md
  30. B5d

    Offline enrollment verified

    Recoverable crew enrollment with reader-version protection and unchanged originals.

    ENROLLMENT-VALIDATION.md
  31. B5e

    Thirty-two ephemeral clients verified

    Larger-server transport queues with dense/sparse driving under normal/faulted transport.

    FLEET32-VALIDATION.md
  32. B5f

    Thirty-two durable accounts verified

    Atomic capacity expansion preserving smaller worlds and account state.

    DURABLE32-VALIDATION.md
  33. B5g

    Live operator enrollment verified

    Live enrollment and client joins preserving original sessions and boats.

    LIVE-ENROLLMENT-VALIDATION.md
  34. B5h

    Live crash recovery verified

    Four live kill boundaries with original pending deposits replayed exactly once.

    LIVE-RECOVERY-VALIDATION.md
  35. B5i

    Underway enrollment verified

    Enrollment while three original crews retain motion and control.

    UNDERWAY-ENROLLMENT-VALIDATION.md
  36. B5j

    Memory observation verified

    Fifteen-minute normal/faulted memory observations and matched-roster samples.

    MEMORY-OBSERVATION-VALIDATION.md
  37. B50

    Stable local launch verified

    Byte-verified builds staged at one stable launch path with active-player refusal and interrupted-publication recovery.

    STABLE-LAUNCH-VALIDATION.md
  38. B4+

    B4 remaining gates open

    Per-actor scheduling, broader collision/correction acceptance and real WAN/security remain separate open gates. Neither B4 nor MMO capacity is complete.

  39. B5+

    Capacity and profiling remains open

    Native allocation attribution, longer production profiling and larger-world capacity remain open. A valid measurement is not a leak fix.

  40. B6

    Shared-world deployment owner gate

    Linux target, encrypted/authenticated transport, service isolation, backups and restore validation on the shared VPS. The 2026-09-28 delegated decision record (OWNER-DECISIONS-DELEGATED) explicitly defers deployment as an owner-act-only action with named revisit conditions. No VPS deployment has occurred.

    MMO-ROADMAP.md

Section C

Expansion systems

The archipelago. First playable slices are in; shared authority and the owner-gated systems are not.

42%

  1. C1

    Three-track standing partial

    Feared/known/clean local slice verified and staged with source-backed rewards and three-port history. Shared standing authority, further consumers and human weights/rates tuning remain.

    STANDING-RELEASE-VALIDATION.md
  2. C2

    Source relationships open

    Fresh reports, warnings when others buy information, refusal and source exposure. Queued behind C1.

  3. C3

    Law as a limited role open

    Officer contacts, evidence tips and contracted hunter/escort work. PvP and amnesty contracts wait for explicit rules and anti-abuse tests.

  4. C4

    Shared fuel assistance partial

    Consent, reserve, proximity/ownership guards and crash-safe atomic gifts verified and staged. Per-vessel tank/range tradeoffs and human balance tuning remain.

    FUEL-ASSISTANCE-VALIDATION.md
  5. C5

    Playable-law faction partial

    Declared-membership slice VERIFIED: four canon authorities plus unaffiliated, an account declares one membership and can reverse it, over two wire kinds where the request names only a faction and a revision, so identity is the authenticated connection and no payload byte can move another account. Optimistic concurrency with idempotent request-hash receipts; a durable realm-bound registry written only by the server (the account database is untouched on purpose). Native cohort PASS with a 37-check raw-log and registry audit (count corrected after the audit itself gained mutation tests); a verifier bug that ate its own event is retained and explained. Membership consequences, reversal cost (needs a named ledger row), contracted/sworn/burned states and player-law roles (behind C9) remain open.

    REGION-FACTION-VALIDATION.md
  6. C6

    Ownable fronts awaiting humans

    First front native-verified 2026-09-30 (FRONTS-LEDGER rows T1-T5, solo realm): one deed to one captain ever, the price burned; laundering queued against a clock-reset daily cap; a 15 percent night cut split half to the till and half to the fire; a morning trickle the till can actually pay; one back-room fitout tier; a buyback the till must fund; tamper-refusing receipts on the same atomic rails as every other purchase. The clean pool has no row that lets it spend anywhere, so the front is a net sink by construction. Two-process native scenario PASS, and the v18 save fixture migrated across the schema bump on the same battery. The owner playtest and the price-tuning pass gate staging; shared-world ownership stays behind the B6 conversation. No idle-presence rewards.

    STOREFRONT-VALIDATION.mdFRONTS-LEDGER.md
  7. C7

    Jet-ski experiment open

    Waits on M0 human boat-feel evidence and a distinct water role with proven access/cargo/exposure tradeoffs.

  8. C8

    Longer-term jurisdictions open

    Contested ports and cross-region careers need measured B/C5/C6 operation and explicit cross-region ownership design.

  9. C9

    Shared consequence model partial

    Retained-record foundation, the patrol-report storage slice and the archive vault are verified and live in the stable launcher: capacity, saturation, damaged-input, reopen and restore gates plus generation sealing with provenance-recorded reclamation, and the captain history view browses sealed generations in game with their hash and disclosure lines. The region now also records its own pursuit facts server-side into the archive of the pursued captain through the production queue, and delivers a watermark-only notice to that captain over the wire with acks bound to the authenticated connection and surviving restarts (no client payloads, no record content on the wire). The case ledger is verified: the region opens a server-recorded case per account from the same genuine pursuit edges it observed, band computed from evidence against the existing thresholds rather than a second heat dial, attribution kept as a recorded fact the wire never shows, and dismissal by age as the first honest outcome - a verdict that deletes nothing, verified across a region restart with the dismissal travelling the wire as its own push. Penalties, playable law authority and the remaining evidence families are later slices.

    PATROL-STORAGE-VALIDATION.mdPATROL-REPORTS-VALIDATION.mdPATROL-ARCHIVE-VALIDATION.mdREGION-EVIDENCE-VALIDATION.mdREGION-CASES-VALIDATION.md
  10. C10

    Jail opening and return flow partial

    C10-A holding location, contact and zero-cash release verified; C10-B kill-boundary publication and C10-C migration edges pass through v0.53. Account-owned custody, offline sentences and full character death are unimplemented.

    HOLDING-VALIDATION.mdHOLDING-CRASH-VALIDATION.md
  11. C11

    Legitimate maritime work partial

    Pot and rod fishing with orders, mixed holds, inspections, recognition and original-cargo salvage verified and staged. Human trip/economic tuning, shared buyer budgets and law-tier search policy remain.

    FISHING-VALIDATION.mdOWN-WRECK-VALIDATION.md
  12. C12

    In-game phones and calls partial

    First text-call slice VERIFIED: 120-byte calls over the authenticated routing where identity is the connection, the relayed caller seat is the server roster record, presence is authority-checked, a per-connection cooldown and honest delivered-means-handed-to-connection receipts. Native cohort PASS with a 31-check raw-log audit; the first cohort failure is retained and explained. No HUD, no ring/answer receipts, no contacts yet; voice stays deferred as account-linked SaaS. Never voice as evidence; never microphone-gated progression.

    REGION-CALLS-VALIDATION.md
  13. C13

    Abstract production partial

    First solo station-to-buyer slice verified and staged with finite demand, funded buyers and atomic saves. Human tuning, collected site evidence, shared production and atomic formula transfers remain.

    PRODUCTION-VALIDATION.md
  14. C14

    Bounded dockside robbery open

    Delegated decision recorded 2026-09-28 (OWNER-DECISIONS-DELEGATED): light scope pre-accepted (non-lethal, interruptible, witness-generating, authoritative item transfer, victim recovery path); implementation is sealed behind C9 case outcomes so a steal can never be consequence-free.

  15. C15

    Fictional weapons awaiting humans

    First weapon slice native-verified 2026-09-30 (WEAPONS-LEDGER rows S1-S4, solo realm): exactly two fictional tools, one of each per captain, each price burned to nothing; sealed twelve-round boxes as the only ammunition sink on a clock-forward daily cap; a fire intent that carries a receipt, a tool, a target and a distance and never a damage number, because the flat table is read by the authority alone; and one named destructible that pays nothing, walks down under the flat hits and refloats at the morning roll. No player hitbox is addressable anywhere in the seam, shot consequences stay whole for the witness slice, and player-versus-player damage remains sealed behind its own later decision. Two-process native scenario PASS: eight shots to the bottom, the ninth honestly refused, and a reload that replays a used shot paper without burning a round. The owner playtest and the price-tuning pass gate staging.

    ARSENAL-VALIDATION.mdWEAPONS-LEDGER.md
  16. C16

    Pawn broker and goods market partial

    First local NPC broker verified and staged with funded buyers, buyback and atomic saves. Human tuning, C9 collected history and shared goods authority remain; wagering and owned shops are separate decisions.

    GOODS-BROKER-VALIDATION.md
  17. C17

    Adult vice content awaiting humans

    First slice native-verified 2026-09-29: Company at the docks, solo realm. One night-only corner table inside La Marea, one independent named adult NPC, offer-then-consent interaction (the first word is never a charge, walking away lapses it unspent), a fixed 150-dollar price that burns banked cash and moves nothing else, and a bounded decaying heat spike that raises patrol attention but can never touch recorded evidence. Daylight does not close the table, it makes it absent. The two-process native scenario passed every assertion, the reload resuming exactly where the purchase process left the burn, the tally and the heat, and the whole table re-endorsed green on every schema bump since, most recently v22. Shared and server-side vice stay closed by decision; the player never operates, owns or profits from the trade; trafficking, sexual violence and minors remain absolute exclusions; zero explicit content ships, and the ledger row is named in the sinks table. The owner playtest and price tuning are required before staging.

    VICE-COMPANY-VALIDATION.md

Effort ledger

What the run has spent

Commits

663

61 release tags · latest v0.60.0-prototype · HEAD 1256999

Tooling tests green

2,579

The full Node test suite over build, release, staging and validation tooling, green at 2,579 and re-bound to a retained run log at each milestone handoff (latest 2026-09-30).

Stable launcher now carries

sealed-generation browsing build

The stable local launcher now carries the verified sealed-generation patrol-archive browsing build, with the previous rotation build kept as a hash-verified rollback. Tree fb972e97…, exe 7bc58a21…

Tokens measured

7,704,130

Lead 5,395,545 in / 768,435 out / 1,356,990 reasoning, 368,004,275 cache reads. Reviewer 173,834 in / 8,560 out. 12 sessions in the runtime store, cost $0 on subscription plans.

Measured from the local agent runtime store on the snapshot date, covering the sessions it still holds for this project. It is not a lifetime total: archived sessions and calls made through separate CLI subscriptions are outside this store and unmetered here. Cost is $0 because every model runs on a flat subscription plan, not because the work was free.

Acceptance runs are named native cohorts with fresh evidence directories. Killed-process restarts, raw save audits and reviewed screenshots back each claim. Failed cohorts are retained, never rerun under a new label.

Crew manifest

Which model does what

Qwen3.8 Flash-Next Lead agent

KK on the Sparks, over LAN · Local hardware. Free and private.

Plans and writes the C# and tooling, runs Unity editor checks, candidate builds and native acceptance cohorts, updates the roadmap and ships this site. Its tokens are the lead line in the ledger above.

GPT-6 Astra Design and security reviewer

ChatGPT subscription, OAuth · Flat subscription. Metered in the ledger above.

Adversarial design and security reviews before risky code ships, plus devlog prose polish. Six delegated sessions measured in the local runtime store.

Claude (Claude Code) Frontier coder, called when stakes are high

Anthropic Max subscription · Flat subscription. Outside the local meter.

Hard multi-file coding, subtle debugging and code review on the pieces where correctness matters most.

Kimi k3 Frontend and large-input pass

Kimi Code subscription · Flat subscription. Outside the local meter.

Web and interface work, research and reading very large inputs whole.

Every model runs on a flat-rate subscription OAuth login. There are no API keys anywhere in the pipeline, which is also why the dollar line in the ledger reads zero.

Methodology

The scored items are the numbered milestones of the game repository's ROADMAP.md sections A (local gameplay and demo), B (shared-world foundations) and C (expansion systems), each in the state its linked validation document supports. Evidence links point at the validation docs, tagged prototype builds and the shared-world engineering gates.

Percent is a ledger average under the counting rule printed with the overall bar. It is deliberately not a completion promise: human-acceptance passes, the deployment decision and the owner-gated systems stay visible as open, and a percentage cannot feel like a boat.

Token figures come from the local agent runtime store on 2026-09-30 and cover the sessions it holds for this project; the caveat beside the ledger says exactly what is outside that measurement. Commit and tag counts come from the game repository. This page is rebuilt from its data file with the site, so the numbers and the rule that produces them move together or not at all.

No storefront, no wishlist button

Get the demo when it drops

One email when the free demo is playable. One more when the game is out. That is the whole plan, and you can leave any time.

We will not sell your address, and this list is for the game only. No trading talk, no price talk. If we ever break that, unsubscribe and tell us why.

The devlog is where the honest version lives, including the parts that do not work. The roadmap shows what we are trying to prove and in what order.