Skip to content

Next-version batch implementation review

Status: complete for the additive v0.13–v0.16 scope · Reviewed against the updated 58,209-byte handoff bundle

This review treats the five RFCs and Appendix A as one acceptance contract. The implementation remains product-neutral and preserves every v0.12 rename as a deprecated alias until the separately scheduled v1.0 boundary.

Requirement-to-evidence matrix

Requirement familyShipped implementationVerification evidenceResult
RFC-001 neutral contractsTurnReducer, neutral actions/views, solver and replay names; deprecated Grid* aliases; participation and ranked outcomestest/next-version.test.ts, test/information.test.tsComplete
Sequential disciplineImmutable turn rotation, reversal, FIFO extras, skips, elimination, reorder, wrap-aware rounds; protocol participation adaptertest/information.test.ts, test/protocol.test.tsComplete
RFC-002 addressing/layoutsTyped LocationRef keys; square, axial-hex, directed graph layouts; generic path/LOS/fields; keyed movement and footprintstest/next-version.test.ts, test/requirements-coverage.test.tsComplete
RFC-002 integration fixturesCube-oracle hex properties, axial collisions, authored graph paths, generic networks/reactions, cross-board settlement and replaytest/requirements-coverage.test.tsComplete
RFC-003 partitionsIndependent identity/order visibility, conventional seat-view derivation, board fog/shells, leak assertion, revelations, teams and spectator policytest/information.test.ts, test/zones-card.test.ts, test/requirements-coverage.test.tsComplete
Seat-aware agentsLegal actions derived only from viewFor; redacted observation transcript replay from the authoritative seedtest/information.test.ts, test/requirements-coverage.test.tsComplete
RFC-004 zonesValidated list/bag/slot configurations and presets; atomic plan/commit transfers; arrivals; seeded shuffle/draw; round-robin and batch dealstest/zones-card.test.tsComplete
RFC-004 compositionKeyword layers, three-seat response priority and timeout passes, LIFO unwind, bounded target choices, durations, phases, structured deck validationtest/zones-card.test.ts, test/agent-drivers.test.tsComplete
RFC-004 integrationThree-seat policy matrix, deck/hand/bag leak permutations, capacity failure, priority draft claims, open-hand solitaire solving, target replaytest/zones-card.test.ts, test/requirements-coverage.test.tsComplete
RFC-005 portalsAuthored/bidirectional edges, heterogeneous destination adapters, footprints, groups, multi-hop, cycle/pass bounds, claims contention, atomic transformation and arrival committest/portals.test.tsComplete
RFC-005 integrationHex → bag → graph chain, cycle, rider/mount failure, capacity-one all-fail/priority, ordering trace, visibility atomicity, transcript replaytest/portals.test.tsComplete
Pattern accommodationDeterministic maximal runs and authored motifs over arbitrary layoutstest/information.test.tsComplete
High-frequency accommodationSparse tick actions, canonical tick/seat/action order, empty-tick replay, rollback resimulation, state digests, reducer performance guidancetest/information.test.ts, docs/high-frequency.mdComplete
Frame skipRepeated or product-continuation actions, early illegal/terminal stop, every tick recorded, transcript v1.2 replay without double skippingtest/multi-agent.test.tsComplete
Multi-agent follow-upPer-seat redacted turns/legal actions, default wait, canonical atomic applyIntents, concurrent policies, per-seat rewards/outcomes, shared replayable transcripttest/multi-agent.test.tsComplete
Known-gaps registerTeam-ranked outcomes, team visibility, revelation records, seat lifecycle/time/id/spectator/P2P security guidancetest/information.test.ts, mechanism and high-frequency documentationComplete

Determinism and atomicity findings

  • Every mechanism consumes stable product ids and explicit seeds; none mints random identity or reads wall-clock time.
  • Zone and portal planning is mutation-free. Group/capacity failures do not partially apply, and arrival callbacks run only after a complete commit.
  • Hidden zone order remains canonical in authoritative state but is never exposed through conventional seat views.
  • Portal and simultaneous-intent arbitration use documented total ordering.
  • Target enumeration reports truncation. Generic agents and the solver reject a partial target surface rather than silently treating it as complete.
  • Replays preserve board, zone, seat, target, and tick addressing.

Compatibility and intentional boundaries

These are not implementation gaps:

  • Deprecated v0.12 aliases remain available through v0.16 exactly as promised. Removing them belongs to the breaking v1.0 release.
  • Product reducers own card meaning, legal actions, costs, effects, terrain, fog memory, portal activation, authoritative persistence, and serialization.
  • Wager pools, negotiation, adversarial search, continuous physics, schedulers, realtime transport, NAT/signaling, and cryptographic hidden-information protocols remain explicitly out of SDK scope.
  • Pure peer-to-peer lockstep cannot protect full hidden state from a modified peer. Optimistic P2P plus server replay provides deterministic integrity and dispute resolution, while competitive confidentiality requires an authoritative session resolver (for example, a per-match Durable Object) that sends only seat-redacted views.
  • Solver search remains defined for open-information, discrete decision spaces. Products may provide snapshots around mutable high-frequency state.

Final gap disposition

No unimplemented normative requirement remains in the current additive v0.13–v0.16 batch. The only scheduled work beyond this batch is the explicit v1.0 alias removal/package-boundary decision and future consumer-driven features that the RFCs list as out of scope.

Reusable mechanics in the toolkit. Product content stays in the product.