Skip to content
Nindova

Roadmap

In the v0.3.0 source release

Section titled “In the v0.3.0 source release”
  • Masala Mound pure legality kernel and two equal 36-Tile board profiles: three-layer Gentle and four-layer Deeper.
  • Deterministic recipe version 5 with exhaustive 382-state Gentle and 510-state Deeper verification, one ending each, and zero dead states. Deeper opens through three staged crown matches, each hidden among unmatched free decoys.
  • Deterministic brass-and-peacock match feedback, an optional three-note chime, and a reduced-motion opacity alternative.
  • Primary Rest handoff, one optional response-free Rasoi Image Drift, and deliberate same-night return through intake.
  • Hidden twelve-minute automatic settle and fifteen-minute ceiling.
  • Version-3 long-lived state with safe v1/v2 Dawn migration and recipe-two completion preservation; version-4 same-tab resume restores the chosen profile without creating history.
  • Redesigned first-light kitchen Dawn with local still and silent-loop export.
  • Self-contained standalone HTML and separately tested installable offline PWA.
  • Synchronized brand kit, landing page, Starlight docs, rendered source media, Apache-2.0 code licensing, CC0-1.0 original-art provenance, and a locally verified QR artifact for the canonical public route.

The pinned GitHub Pages workflow publishes the static build from main. The live route, rendered QR destination, service-worker control, and offline reload are browser-verified; a physical-device QR scan remains pending.

Next hardening

Section titled “Next hardening”
  • Human Punjabi cultural-authenticity review before making a stronger authenticity claim.
  • Real-device VoiceOver and TalkBack acceptance.
  • Installed Safari and additional Android browser/PWA proof.
  • Facilitated human prototype sessions to learn whether the matching exercise actually feels calm, legible, and worth returning to.
  • Performance profiling on low-power phones without adding visual stimulation.

Deliberately deferred

Section titled “Deliberately deferred”

The iOS Wall remains a product direction, not a shipped capability. Family Controls entitlement, Screen Time routing, and version-specific Gate behavior require a separate native implementation and proof track. See Deferred iOS Wall.