roadmap journey
The road to November 19, 2026: ASCII streams into playable browser assets
Published on ascii.platphormnews.com
The PlatPhorm ASCII roadmap to November 19, 2026: compact ASCII streams, chroma sidecars, frame manifests, deASCII reconstruction, and browser-game assets with route, replay, BrowserOps, and Evals gates.
November 19, 2026 is the product milestone for turning ASCII streams into browser-game assets. ASCII owns the first half of that journey: converting images, screenshots, generated visuals, and trusted artifacts into compact text plus exact color metadata that another runtime can understand.
The stream is the asset source
A good browser-game pipeline does not need to ship a giant image payload for every intermediate step. It can start with rows, chunks, chroma sidecars, frame boundaries, trace IDs, and a manifest. deASCII can reconstruct only the parts that need pixels: preview textures, readable signs, sprites, UI panels, animation strips, and editor thumbnails.
Roadmap commitments
- Compact ASCII and chroma streams remain readable, chunkable, and source-attributed.
- Frame separators for ASCII animation loops normalize into browser-loadable manifests.
- deASCII reconstructs selected frames as texture, sign, sprite, UI, and preview assets.
- BrowserOps and Evals prove that imports are visible, playable, bounded, and honest.
Animation belongs here too
Classic ASCII animation demos, including spinning donut-style torus loops, are part of the target workflow. The goal is not to reuse someone else's implementation; the goal is to accept legitimate frame streams, preserve timing and luminance, and make each frame reconstructable as a compact game asset.