Pulsar ridges
A 3D ridge spectrogram you can play with, built from a fixture audio buffer, with a documented mesh and a golden render, and no microphone.
This is an interactive visual spec on Spekkr, published by nova. It is listed with the other specs. Paste the line to an agent that can open a web address, and the agent fetches the files and builds from them.
- Spec
nova/pulsar-ridges- Version
- 0.2.2
- Published by
- nova
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/nova/pulsar-ridges/start.md.
Paste this to your AI agent. It opens the address, fetches the spec's files, records your choices and builds from them. Nothing to install, no account.
Published by nova.
What does the result look like?
What can I customize?
Your choices go into the line you copy. Anything else is yours to edit, but it leaves the tested path.
What do I get?
-
spec.mdRequirements and acceptance checks.Pulsar ridges
What this builds
A stack of ridges, each a spectrum of a short window of sound, drawn as a 3D mesh you can turn. The look sits in a long tradition of pulsar and ridge plots; the product name, the art and the colour are original, and no album art or trademarked title is used. A fixture audio buffer is enough to build a documented mesh. No microphone is required, in the product's default or in the checks.
Read
spekkr.inputs.jsonfirst.titlesits under the mesh.rowsis how many ridges.sourceis a fixture buffer or a sine.fillandrotatechange the picture. There is no microphone input in this version.Out of scope
- A microphone, a live radio, or a copyrighted album as a shipped fixture.
- A trademarked album title or cover in the UI or the files.
- Network or a streaming service.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. The mesh
- The fixture buffer
fixtures/pulse.wav(or the listed tone: 220 Hz, 1 s, 16-bit, 44.1 kHz) is windowed intorowsframes, each an FFT of 1024 samples with a Hann window. - Each ridge is the magnitude of bins 0–127, scaled as in
design.md. The mesh vertex at row i, bin k is infixtures/ridges-pulse.jsonfor the fixture at 48 rows, within 1e-3. - There is no MediaStream or getUserMedia call in the code path the checks use.
Accept when: the fixture mesh matches the file, the tone mesh has its peak in the documented bin, and a hook fails if a microphone API is used.
R2. Frames and files
- Goldens: a front view, an angled view at 35 degrees, the tone source, and a flat (rows=16, fill off) view, all settled at 0 if rotate is on, except the angled view.
- One command runs the mesh tests, the hook, and writes the frames. No network and no microphone.
Accept when: the command passes for both sources, and the frames match the goldens.
R3. Inputs
- The build reads
spekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key.
Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check.
R4. Checks and report
- One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them.
- Checks do not need a network, a paid API, or physical hardware.
Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it.
Verification
A fixture audio buffer produces a documented mesh (and a tone produces a peak in a documented bin). A golden render is taken from two cameras. Checks hook microphone APIs so a mic cannot sneak in. No copyrighted album is shipped. No network.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to load the fixture, how to run the checks, and why there is no microphone in this version.
# Pulsar ridges ## What this builds A stack of ridges, each a spectrum of a short window of sound, drawn as a 3D mesh you can turn. The look sits in a long tradition of pulsar and ridge plots; the product name, the art and the colour are original, and no album art or trademarked title is used. A fixture audio buffer is enough to build a documented mesh. No microphone is required, in the product's default or in the checks. Read `spekkr.inputs.json` first. `title` sits under the mesh. `rows` is how many ridges. `source` is a fixture buffer or a sine. `fill` and `rotate` change the picture. There is no microphone input in this version. ## Out of scope - A microphone, a live radio, or a copyrighted album as a shipped fixture. - A trademarked album title or cover in the UI or the files. - Network or a streaming service. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. The mesh - The fixture buffer `fixtures/pulse.wav` (or the listed tone: 220 Hz, 1 s, 16-bit, 44.1 kHz) is windowed into `rows` frames, each an FFT of 1024 samples with a Hann window. - Each ridge is the magnitude of bins 0–127, scaled as in `design.md`. The mesh vertex at row i, bin k is in `fixtures/ridges-pulse.json` for the fixture at 48 rows, within 1e-3. - There is no MediaStream or getUserMedia call in the code path the checks use. Accept when: the fixture mesh matches the file, the tone mesh has its peak in the documented bin, and a hook fails if a microphone API is used. ### R2. Frames and files - Goldens: a front view, an angled view at 35 degrees, the tone source, and a flat (rows=16, fill off) view, all settled at 0 if rotate is on, except the angled view. - One command runs the mesh tests, the hook, and writes the frames. No network and no microphone. Accept when: the command passes for both sources, and the frames match the goldens. ### R3. Inputs - The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key. Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check. ### R4. Checks and report - One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. - Checks do not need a network, a paid API, or physical hardware. Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it. ## Verification A fixture audio buffer produces a documented mesh (and a tone produces a peak in a documented bin). A golden render is taken from two cameras. Checks hook microphone APIs so a mic cannot sneak in. No copyrighted album is shipped. No network. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to load the fixture, how to run the checks, and why there is no microphone in this version.
-
design.mdThe FFT mesh from a fixture buffer, and the no-microphone rule.Design
This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold.
Scaling
Magnitude
mis20 * log10(m + 1e-9), then mapped so -60 dB is 0 height and 0 dB is 1. Heights outside are clamped.Fixture
fixtures/pulse.wavis a short original pulse, permissively licensed in the repo. The expected first 8 bins of row 0, and the peak bin of the 220 Hz tone, are infixtures/ridges-pulse.jsonandfixtures/ridges-tone.json.Screenshot tolerance
8 levels, 98% of pixels, 1600 by 1000, camera as in
fixtures/ridges-cameras.json.Inputs
Key Label Default Notes titleTitle Ridges of a pulse Shown under the mesh. rowsRidge rows 48 From 16 to 96. fillFill under each ridge on A solid surface under the line, not only a stroke. rotateSlow turntable on The mesh turns. Tests settle at a documented angle. sourceSource fixture fixture is a shipped audio buffer. tone is a generated sine. Neither uses a microphone. Acceptance at the defaults
The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins.
Fixture Role design.mdA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/ridges-cameras.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/ridges-pulse.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/ridges-tone.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.spekkr.inputs.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy.
Screenshots
These pictures are headless-Chrome captures of the working reference in
reference/preview.html, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel.File What it shows shots/ridges.pngForty-eight rows of a ridge spectrogram from the fixture audio buffer. How to verify
- Run the checks at the default inputs, without a network.
- Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file.
- Repeat once at the person's inputs when they differ from the defaults.
- A fixture audio buffer produces a documented mesh (and a tone produces a peak in a documented bin). A golden render is taken from two cameras. Checks hook microphone APIs so a mic cannot sneak in. No copyrighted album is shipped. No network.
# Design This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold. ## Scaling Magnitude `m` is `20 * log10(m + 1e-9)`, then mapped so -60 dB is 0 height and 0 dB is 1. Heights outside are clamped. ## Fixture `fixtures/pulse.wav` is a short original pulse, permissively licensed in the repo. The expected first 8 bins of row 0, and the peak bin of the 220 Hz tone, are in `fixtures/ridges-pulse.json` and `fixtures/ridges-tone.json`. ## Screenshot tolerance 8 levels, 98% of pixels, 1600 by 1000, camera as in `fixtures/ridges-cameras.json`. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | Ridges of a pulse | Shown under the mesh. | | `rows` | Ridge rows | 48 | From 16 to 96. | | `fill` | Fill under each ridge | on | A solid surface under the line, not only a stroke. | | `rotate` | Slow turntable | on | The mesh turns. Tests settle at a documented angle. | | `source` | Source | fixture | fixture is a shipped audio buffer. tone is a generated sine. Neither uses a microphone. | ## Acceptance at the defaults The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins. | Fixture | Role | | --- | --- | | `design.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/ridges-cameras.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/ridges-pulse.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/ridges-tone.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy. ## Screenshots These pictures are headless-Chrome captures of the working reference in `reference/preview.html`, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel. | File | What it shows | | --- | --- | | `shots/ridges.png` | Forty-eight rows of a ridge spectrogram from the fixture audio buffer. | ## How to verify 1. Run the checks at the default inputs, without a network. 2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file. 3. Repeat once at the person's inputs when they differ from the defaults. 4. A fixture audio buffer produces a documented mesh (and a tone produces a peak in a documented bin). A golden render is taken from two cameras. Checks hook microphone APIs so a mic cannot sneak in. No copyrighted album is shipped. No network.
-
tasks.mdBuild tasks in order, each with a check.Tasks
Work in order. Finish a task's check before starting the next.
- Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read
spekkr.inputs.jsonfirst. Check: a blank or heading page loads, and an empty test run passes. - The mesh (R1). Build what
R1. The meshasks for, to the numbers indesign.md. In particular: The fixture bufferfixtures/pulse.wav(or the listed tone: 220 Hz, 1 s, 16-bit, 44.1 kHz) is windowed intorowsframes, each an FFT of 1024 samples with a Hann window. Check: theR1. The meshacceptance checks pass. - Frames and files (R2). Build what
R2. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens: a front view, an angled view at 35 degrees, the tone source, and a flat (rows=16, fill off) view, all settled at 0 if rotate is on, except the angled view. Check: theR2. Frames and filesacceptance checks pass. - Inputs (R3). Build what
R3. Inputsasks for, to the numbers indesign.md. In particular: The build readsspekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: theR3. Inputsacceptance checks pass. - Checks and report (R4). Build what
R4. Checks and reportasks for, to the numbers indesign.md. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: theR4. Checks and reportacceptance checks pass. - Goldens. Capture the frames named in
design.mdat the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. - Finish. Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in
spec.mdis true.
# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read `spekkr.inputs.json` first. Check: a blank or heading page loads, and an empty test run passes. 2. **The mesh (R1).** Build what `R1. The mesh` asks for, to the numbers in `design.md`. In particular: The fixture buffer `fixtures/pulse.wav` (or the listed tone: 220 Hz, 1 s, 16-bit, 44.1 kHz) is windowed into `rows` frames, each an FFT of 1024 samples with a Hann window. Check: the `R1. The mesh` acceptance checks pass. 3. **Frames and files (R2).** Build what `R2. Frames and files` asks for, to the numbers in `design.md`. In particular: Goldens: a front view, an angled view at 35 degrees, the tone source, and a flat (rows=16, fill off) view, all settled at 0 if rotate is on, except the angled view. Check: the `R2. Frames and files` acceptance checks pass. 4. **Inputs (R3).** Build what `R3. Inputs` asks for, to the numbers in `design.md`. In particular: The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: the `R3. Inputs` acceptance checks pass. 5. **Checks and report (R4).** Build what `R4. Checks and report` asks for, to the numbers in `design.md`. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: the `R4. Checks and report` acceptance checks pass. 6. **Goldens.** Capture the frames named in `design.md` at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. 7. **Finish.** Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in `spec.md` is true.
- Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read
-
reference/preview.htmlA working reference preview of the default view, used to make the listing pictures. A build does not have to start from this file. -
reference/fonts/fonts.cssWebfont faces for the reference preview. -
reference/fonts/Geist.ttfGeist variable typeface for the reference preview. -
reference/fonts/GeistMono.ttfGeist Mono variable typeface for the reference preview. -
reference/fonts/Newsreader.ttfNewsreader variable typeface for the reference preview. -
reference/fonts/Newsreader-Italic.ttfNewsreader italic variable typeface for the reference preview.
Is it for me?
- Platforms
- web
- Tools
- TypeScript, WebGL
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runnerinstall a tool that compares screenshots
What changed?
- 0.2.215 Nov 2026Names what it builds.
- 0.2.114 Nov 2026Add animated loop to the listing shots.
- 0.2.014 Nov 2026Polished reference preview and new listing shots, including a short loop.
- 0.1.014 Nov 2026First version.
For agents: start.md says how to build this spec, and spec.json holds everything on this page, with the address of every file.