Prompt Trace

v69 · CC69-001. Shared geometric instrument and reversible file scores. Frozen v68 protocol is retained; full native-browser recovery remains pending.

SpiralCore name-to-route derivation. A human-readable prompt deterministically selects symbolic coordinates and a route. This is an application-local derivation, not DNS: it performs no DNS query, delegation, caching, record lookup, or network name resolution.

Type a name. It gets summed as Simple English gematria (A=1..Z=26, a real documented system on its own), then transliterated — via an informal single-letter phonetic substitution I built for this tool, not a scholarly transliteration standard — into Hebrew, Greek, and Arabic, and summed under each of those three real historical systems. Hebrew's sum picks the source zone, Greek's picks the destination host, Arabic's picks the demarc. Then it actually runs: same pathfinding, same spelling, same sound engine already built and tested on the other two tabs — this panel just derives their inputs from the name instead of a dropdown.

The selected AXIS2 gematria and every routed O0 layer code are reported in this profile.

Choose a file, then Record score to add it to Scores. Each 4096-byte block runs through Prompt Trace; reversible musical route choices preserve its exact bytes. Open the explanation below for the replay and verification process.

How prompt traces and file scores work

Trace derives a geometric route from your prompt. Record score also preserves the reversible musical choices needed to reconstruct an uploaded file.

  1. Record the block context. Each file block of up to 4096 bytes enters this prompt handler as an exact base64 representation. The score retains its derived context and route audit.
  2. Preserve byte order. Inside each block, cells of up to 32 bytes become choices among 63 lawful geometric musical routes. Each choice plays a six-note route. These reversible choices distinguish files that share the same aggregate prompt trace.
  3. Replay and measure. Run a score in Scores. The player generates musical audio; a separately initialized receiver measures its PCM waveform using the shared instrument and public framing. Decoded choices pass through ordered FBS cells to reconstruct bytes.
  4. Verify and release. Reconstructed blocks must match their retained Tab1 context, and the complete file must match its original SHA-256 before download is offered. Temporary file buffers are released after download is handed to the browser; the score remains.

What the score keeps: packed reversible route choices, block lengths, route context, the replay profile and verification hashes. Source files and generated waveforms are not saved in the score store. The shared instrument must remain available.

Current recovery profile: golden musical routes from DUALFACE:3 to ICOSIAN:90; Kuramoto and FBS reset per 32-byte cell. This lane is distinct from the Bell MF profile selector above.

Evidence: full original-v68 recovery passed the software PCM reference run. A user-supplied native-browser 32-byte report passed; native 4096-byte and full-file runs remain pending. The fixture-manifest fix is user-confirmed.

Size: the current v68 score retains reversible source information and is larger than the source file. Removing temporary audio does not establish a compression gain.

version_00 — Route / FBS / Kuramoto timing audit

Trace a prompt first. Capture records the existing schedules and current state. Enable audio observation before playback to retain WebAudio API scheduling calls.

Live policy: one hop per atom; one simulation unit per nominal route second; ordered carries commit at the hop boundary. This is an explicit one-way experimental coupling, not a phase-readiness gate. Browser animation remains a separate replay.

Hop-to-atom correspondence is a comparison hypothesis. Capture does not advance FBS or synchronize clocks. Browser samples and audio API calls are observations; route and Bell offsets are nominal schedules.

Findings and validation notes — 8 October 2026
No audit captured.