Architecture

Workspace

• House — Vite-compiled TypeScript for transactional navigation, five typed category doors, eight game definitions, pure classic-study rules, one Salon lifecycle, same-tab active state, replaceable result provenance, adult acknowledgement, and its scoped worker.
• Session — Vite-compiled TypeScript for the pure Rasoi kernel, native tile interface, boundary clock, optional audio, Night state, and Dawn export.
• Site — Astro landing page and Starlight documentation built from verified product facts and rendered release media.
• Composition — one static root artifact containing the landing page, /docs/, /house/, /play/, and portable nindova.html.

House boundary

salon-catalog.ts owns the five-door/eight-game registry and total five-part metadata for every table. stack-architect.ts owns the complete three-plinth law and corrupt-board repair policy. classic-studies.ts keeps canonical board graphs and sowing rules private behind immutable semantic chapter views and one choice evaluator, so visual and nonvisual rendering cannot drift from the authored position.

house-navigation.ts commits one complete destination transaction: hash parsing/writing, History depth, unfinished-table consent, cancelled destinations, game teardown, scroll restoration, and focus return. salon-table-lifecycle.ts owns table opening, restore, meaningful-progress policy, kind-specific interaction, chapter advance, focus policy, runner synchronization, and active-table persistence. The shell renders House markup but does not mutate chapter, memory, plinth, resolution, or route-protocol state.

house-state.ts remains the only owner of Gallery and active-table browser storage, including v1→v2 fallback, copy-on-write completion, failed-write behavior, compact active records, fail-closed runner reload, and exact clearing. sector-sprint.ts owns the pure navigation mesh, movement, jump/dash physics, power-ups and authored encounters. sector-sprint-world.ts owns Canvas rendering. sector-sprint-table.ts owns the ten-minute foreground arbiter, cancellation, pause/hide/blur/exit suspension, narrated parity, sound, teardown guards and exactly-once terminal outcome. The House still consumes only start, view, afterRender, setExitSuspended, and close.

house.ts composes those modules into presentation, sound, celebration, and completion. A safety-boundary exit or runner document reload cannot create completion provenance. Every actual completion is permanently labeled mode: "entertainment"; no assessment scoring or population comparison is present.

assessment-readiness.ts is a source-only, fail-closed evidence contract. It is not imported by the House runtime and introduces no route, UI, storage, request, or scoring path. It rejects entertainment results as assessment inputs and keeps research collection and public cognitive output disabled.

The House links to but does not import the Night runtime. /house/ and /play/ have separate storage namespaces, manifests, service workers, and browser evidence contracts (window.__house and window.__ct).

Legality kernel

rasoi-core.ts owns motif identity, deterministic board creation, free-tile calculation, legal-pair enumeration, pair removal, help selection, completion, and exhaustive reachability verification. Rendering and input do not duplicate its legality rule.

The authored Gentle geometry has 24 base, 8 middle, and 4 top Tiles. Deeper has 20 base, 10 middle, 4 upper, and 2 crown Tiles. Its interleaved upper/crown motif order creates a three-step opening search: each step exposes at least four free candidates, includes unmatched decoys, and offers only one legal pair. Both use a half-Tile coordinate grid. A remaining Tile is free only when no higher-layer Tile overlaps it and at least one same-layer horizontal side is open. The verifier confirms 382 Gentle and 510 Deeper reachable states, one terminal state each, and zero dead states; every legal choice remains safe.

Browser and local state

session.ts renders semantic buttons and layered coordinates, applies the tonight-only profile, synthesizes optional deterministic audio, presents the paired bloom, qualitative path reflection, and optional response-free Image Drift, and maintains versioned window.__rasoi. window.__ct remains an alias for compatibility evidence. It applies the closure and resume decisions below rather than making them.

session-boundary.ts decides what every Session phase owes the person at one instant, from one threshold pair: an open board settles at the hidden twelve-minute wind-down, and settling, the end card, and Image Drift each give way to Rest at the fifteen-minute deadline, so no phase can outlive the cap. session.ts performs those outcomes and, per ADR 0005, completes a still-settling board’s final response so the Night is recorded before the return. active-session.ts owns version-4 same-tab resume validation — schema, Board profile, board-identity re-derivation, settled-Tile membership and reachability, phase-and-ending agreement, and the clock audit — returning either a rebuilt Session or one refusal reason.

night-core.ts owns Night ID and Dawn-record recipe version 3, v3 state sanitization, v1/v2 migration, preservation of recipe-two Rasoi Dawn data, and idempotent completion; it validates a stored completion against the Tile vocabulary rasoi-core.ts deals rather than keeping a second copy of it. rasoi-core.ts owns that vocabulary and board-geometry recipe version 5. dawn-core.ts owns captured-zone eligibility, the keepsake frame for both remembered Rasoi Nights and migrated legacy records, still/loop capability handling, sharing, and temporary URL leases.

Browser evidence boundary

tests/browser/evidence-harness.mjs owns preview startup, Chromium launch, contexts, explicit capability adapters, console and page failure capture, request capture, and teardown. All twelve browser journeys use it. Adapters may expose an unavailable local browser capability, such as deterministic animation frames or denied audio, but may not fulfill routes, invent product responses, suppress errors, or bypass product state.

The standalone Night HTML and installable Night PWA remain separate journeys. House and Night cache ownership, HTTP-cache-cleared cold entry, same-origin static requests, and zero app telemetry remain direct product assertions rather than harness assumptions.

Distribution boundary

The /house/ and /play/ builds register separately scoped versioned workers. The House nindova-house-v14 cache precaches its core hashed static graph; the full original Chandigarh world and character atlas are precached for the first offline walk. The Night standalone removes its manifest and worker registration during composition. None requires an account or third-party runtime service. A build-time QR generator still encodes the canonical direct /play/ route and adds no runtime request.

The deferred iOS Wall is a separate native boundary and is not implemented by the browser dismissal surface.