Language, Story & Culture
Prototype

OnTheMetareverse

A deterministic literary web experience that performs The Metareverse, analyzes its language, remembers the reader's choices, and returns them as later callbacks.

Category
Language, Story & Culture
Platform
Web
Status
Prototype

What exists beyond reading an electronic book?

Authored analysis, timed typography, text-machine imagery, interpretive decisions, and persistent memory make the page feel attentive without generative AI or alternate story canon.

User value

Read, interpret, and leave a trace in the story.

Encounter The Metareverse through a performed analysis that asks what words, signals, and evidence should remain.

01

Experience the analysis

Commentary acts through timing, replacement, fading history, page movement, blackout, and text-machine imagery instead of sitting beside the novella.

02

Make interpretive decisions

Choose a word, signal, fact, or piece of evidence at authored decision points throughout the available journey.

03

See earlier choices return

The experience remembers selected decisions and acknowledges them later while preserving the story's fixed outcome.

OnTheMetareverse visual prototype asking whether the intelligence should keep the word eyes or replace it with sight.View full size
The first interpretive decisionEarlier text remains as faded history while the reader decides which word the analytical intelligence may keep.

Features

A deterministic literary performance in the browser.

The current second prototype turns approved story material and analysis into a responsive, locally remembered reading experience.

  1. 01

    Three implemented phases

    Move through the P0.1 prologue, seven chapters of Part I: Visibility, and seventeen chapters of Part II: Witness through P2.17.

  2. 02

    Twenty-six authored decisions

    Make two prologue choices, seven Part I choices, and seventeen four-way Part II choices with no free-form input or hidden scoring.

  3. 03

    Deterministic callbacks

    Carry earlier choices into later approved wording and records while every branch converges on canonical events.

  4. 04

    Text as interface material

    Use timed presentation, visible revision, selectable history, text-machine illustrations, rotation, and blackout as part of the analysis.

  5. 05

    Reading controls

    Choose Instant, Fast, Measured, or Slow pace, reduce motion, reveal a complete current passage, or restart the experience.

  6. 06

    Local progress restoration

    Resume the correct phase and retained choices from a validated browser record without an account or remote narrative service.

How it works

Read the passage. Decide what remains.

Participation changes the analytical record and later language, not the canonical events of the novella.

  1. 01

    Begin the performance

    Activate the experience and let authored text, pauses, and visual transformations establish the analytical intelligence.

  2. 02

    Encounter an interpretation

    See the intelligence question a word, classification, signal, or piece of evidence inside the story itself.

  3. 03

    Choose explicitly

    Select from named interpretations without time pressure, free-form input, or a hidden correct answer.

  4. 04

    Carry the record forward

    Let the selected choice shape immediate wording and remain available to later deterministic callbacks.

  5. 05

    Resume locally

    Return through browser-stored progress or start over and delete the current narrative record.

In practice

The interface makes interpretation visible.

OnTheMetareverse first interpretive decision with the visual prototype controls panel open.View full size

Control the reading pace

A compact panel exposes pacing, reduced motion, passage reveal, restart, and the current absence of voice and sound.

OnTheMetareverse Part I decision asking what should remain visible from a large message field.View full size

Decide what remains visible

Part I turns a field of messages into a choice between preserving the count, holding one message, or clearing the field.

OnTheMetareverse available-material boundary stating that the next source line is not implemented and the story is not complete.View full size

Stop where approved material stops

The prototype identifies the P2.17 boundary and states that the current endpoint is not story completion.

Product concept

The book performs its own interpretation.

OnTheMetareverse combines a novella, literary analysis, interaction design, and deterministic narrative memory in one authored form.

01

Analysis becomes behavior

Words are retained, revised, faded, classified, and recalled through the page instead of explained in a separate commentary layer.

02

Participation remains interpretive

The reader influences language and evidence without rescuing George, earning a score, or creating an alternate canon.

03

Apparent intelligence stays authored

Attention, doubt, memory, and responsiveness come from prepared branches and callbacks rather than runtime generation.

Architecture

Typed authored content drives a repeatable browser runtime.

A separate React application resolves approved fragments against retained choices, presents timed sequences, and stores validated progress locally.

  1. 01Explicit Begin action
  2. 02Typed authored sequence
  3. 03Timed text and visual items
  4. 04Named interpretive decision
  5. 05Deterministic response and callback state
  6. 06Versioned local progress snapshot

Content remains deterministic

Typed declarations and resolver functions select the same approved result for the same state and reader choices.

Phases keep their own runtimes

The prologue, Part I, and Part II can change page behavior while sharing retained choices and local progress.

Progress stays in the browser

IndexedDB stores versioned narrative snapshots and localStorage stores pace and motion preferences.

The host only delivers files

The implemented experience uses no runtime model, narrative API, account, analytics integration, or cloud persistence.

Technology

Authored, local, and web-native.

Application

  • TypeScript
  • React 19
  • Vite 8
  • HTML
  • CSS

Narrative model

  • Typed content declarations
  • Deterministic resolvers
  • Phase-specific runtimes
  • Authored callbacks

Local state

  • IndexedDB progress
  • Versioned snapshots
  • localStorage preferences

Validation

  • Vitest 4
  • Playwright
  • Desktop Chromium
  • Mobile Chromium
  • Automated axe checks

Current boundary

  • No runtime generative AI
  • No account
  • No analytics
  • No cloud persistence
  • No service worker

Development

The visual prototype reaches P2.17.

The approved prologue, Part I, and available Part II material are implemented and tested. The experience is not narratively complete or approved for canonical publication.

Stage
Prototype
Current scope
P0.1 through P2.17
Automated checks
16 focused · 3 end-to-end
Publication
Not yet canonical

Implemented in the second prototype

  • Nine prologue sequences, 57 Part I sequences, and 149 Part II sequences across the currently approved material
  • Two prologue decisions, seven Part I decisions, seventeen four-way Part II decisions, later callbacks, and canonical convergence
  • Timed text, text-machine visuals, history treatment, page rotation, blackout, responsive layouts, and selectable reading pace
  • Reduced motion, complete-passage reveal, keyboard focus paths, live-region equivalents, resume, and restart
  • Isolated IndexedDB progress, local visual preferences, snapshot validation, and graceful storage failure behavior
  • Unit, integration, TypeScript, production-build, desktop Chromium, mobile Chromium, and automated axe validation

Before a complete published experience

Continue only after P2.18 and later material are approved. Supply the required font, recorded voice, and authored sound assets, then complete manual creative, cross-browser, accessibility, publication-rights, and canonical release review.