Spherical helix

A small museum of unexpected 3D paths, each a parameterized curve that passes through documented points, with golden camera views.

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/spherical-helix
Version
0.2.2
Published by
nova
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/nova/spherical-helix/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?

Spherical helix: heroSpherical helix: loop

What can I customize?

Starting room Three shipped curves. The museum contains all three.

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.md Requirements and acceptance checks.

    Spherical helix

    What this builds

    A small museum of 3D paths you wander rather than only watch. Each room is a parameterized curve — a spherical helix, a torus knot, a 3D Lissajous figure — with a camera that can ride along it. The math is listed, and tests assert that a curve passes through documented points. Golden camera views are taken in each room. The presentation is original.

    Read spekkr.inputs.json first. title is in the first room. room is where a visit starts; all three rooms exist. turns is used by the helix. ribbon and guides change the picture.

    Out of scope

    • A general computer-algebra system.
    • Network or a user-uploaded equation in this version.
    • A fourth family of curves in this version.

    Requirements

    Each requirement has an id. Checks name the id they cover.

    R1. The curves
    • Each curve is a function r(t) for t in [0, 1], with the formulas in design.md.
    • At the listed t values, r(t) matches the points in fixtures/curves-points.json within 1e-4.
    • The spherical helix lies on a sphere of radius 1: |r(t)| is 1 within 1e-4 for 64 sample t values, at the default turns.

    Accept when: every listed point matches, and the helix samples lie on the sphere.

    R2. The ride
    • A camera ride sets position to r(t) minus a documented offset along the normal, looking at r(t).
    • At t = 0, 0.25, 0.5 the camera pose matches fixtures/curves-cameras.json for the helix at 5 turns.

    Accept when: the three poses match within 0.01 units and 0.5 degrees.

    R3. Frames and files
    • Goldens: each room from a still camera, and one along-path helix view at t = 0.25.
    • One command runs the point, sphere, and pose tests, and writes the frames. No network.

    Accept when: the command passes at turns 2 and 5, and the frames match the goldens.

    R4. 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.

    Verification

    Each parameterized curve passes through documented points within 1e-4, and the spherical helix stays on the unit sphere at 64 samples. Camera poses along a ride match a file. Golden views are taken in each room and along the path. 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 wander the rooms, how to change turns, and how to run the checks.
    # Spherical helix
    
    ## What this builds
    
    A small museum of 3D paths you wander rather than only watch. Each room is
    a parameterized curve — a spherical helix, a torus knot, a 3D Lissajous
    figure — with a camera that can ride along it. The math is listed, and
    tests assert that a curve passes through documented points. Golden camera
    views are taken in each room. The presentation is original.
    
    Read `spekkr.inputs.json` first. `title` is in the first room. `room` is
    where a visit starts; all three rooms exist. `turns` is used by the helix.
    `ribbon` and `guides` change the picture.
    
    ## Out of scope
    
    - A general computer-algebra system.
    - Network or a user-uploaded equation in this version.
    - A fourth family of curves in this version.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. The curves
    
    - Each curve is a function r(t) for t in [0, 1], with the formulas in
      `design.md`.
    - At the listed t values, r(t) matches the points in
      `fixtures/curves-points.json` within 1e-4.
    - The spherical helix lies on a sphere of radius 1: |r(t)| is 1 within
      1e-4 for 64 sample t values, at the default `turns`.
    
    Accept when: every listed point matches, and the helix samples lie on the
    sphere.
    
    ### R2. The ride
    
    - A camera ride sets position to r(t) minus a documented offset along the
      normal, looking at r(t).
    - At t = 0, 0.25, 0.5 the camera pose matches
      `fixtures/curves-cameras.json` for the helix at 5 turns.
    
    Accept when: the three poses match within 0.01 units and 0.5 degrees.
    
    ### R3. Frames and files
    
    - Goldens: each room from a still camera, and one along-path helix view at
      t = 0.25.
    - One command runs the point, sphere, and pose tests, and writes the
      frames. No network.
    
    Accept when: the command passes at turns 2 and 5, and the frames match the
    goldens.
    
    ### R4. 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.
    
    ## Verification
    
    Each parameterized curve passes through documented points within 1e-4, and
    the spherical helix stays on the unit sphere at 64 samples. Camera poses
    along a ride match a file. Golden views are taken in each room and along
    the path. 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 wander the rooms, how to change turns, and how to
      run the checks.
    

    Open spec.md as plain text

  • design.md Parametric formulas, the on-sphere check, and camera rides.

    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.

    Formulas

    The exact formulas, with constants, are fixtures/curves-formulas.md and the point file is the authority for values. A short restatement: the spherical helix is a rhumb line on the unit sphere with turns windings from the south pole to the north; the torus knot is (p, q) = (2, 3) on a torus R=2, r=0.6; the Lissajous is (sin(3θ), sin(4θ), sin(5θ)) with θ = 2πt.

    Screenshot tolerance

    8 levels, 98% of pixels.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA walk along a curveShown in the first room.
    turnsDefault helix turns5From 2 to 12, for the spherical helix room.
    ribbonDraw a ribbononA thin surface along the tangent, not only a tube.
    guidesShow the generating sphereonA faint sphere the helix lives on.
    roomStarting roomhelixThree shipped curves. The museum contains all three.

    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.

    FixtureRole
    design.mdA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/curves-cameras.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/curves-formulas.mdA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/curves-points.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    spekkr.inputs.jsonA 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.

    FileWhat it shows
    shots/curve.pngFive turns of a spherical helix, documented points marked.

    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. Each parameterized curve passes through documented points within 1e-4, and the spherical helix stays on the unit sphere at 64 samples. Camera poses along a ride match a file. Golden views are taken in each room and along the path. 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.
    
    ## Formulas
    
    The exact formulas, with constants, are `fixtures/curves-formulas.md` and
    the point file is the authority for values. A short restatement: the
    spherical helix is a rhumb line on the unit sphere with `turns` windings
    from the south pole to the north; the torus knot is (p, q) = (2, 3) on a
    torus R=2, r=0.6; the Lissajous is (sin(3θ), sin(4θ), sin(5θ)) with θ =
    2πt.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A walk along a curve | Shown in the first room. |
    | `turns` | Default helix turns | 5 | From 2 to 12, for the spherical helix room. |
    | `ribbon` | Draw a ribbon | on | A thin surface along the tangent, not only a tube. |
    | `guides` | Show the generating sphere | on | A faint sphere the helix lives on. |
    | `room` | Starting room | helix | Three shipped curves. The museum contains all three. |
    
    ## 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/curves-cameras.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/curves-formulas.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/curves-points.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/curve.png` | Five turns of a spherical helix, documented points marked. |
    
    
    ## 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. Each parameterized curve passes through documented points within 1e-4,
    and the spherical helix stays on the unit sphere at 64 samples. Camera
    poses along a ride match a file. Golden views are taken in each room and
    along the path. No network.
    

    Open design.md as plain text

  • tasks.md Build tasks in order, each with a check.

    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 curves (R1). Build what R1. The curves asks for, to the numbers in design.md. In particular: Each curve is a function r(t) for t in [0, 1], with the formulas in design.md. Check: the R1. The curves acceptance checks pass.
    3. The ride (R2). Build what R2. The ride asks for, to the numbers in design.md. In particular: A camera ride sets position to r(t) minus a documented offset along the normal, looking at r(t). Check: the R2. The ride acceptance checks pass.
    4. Frames and files (R3). Build what R3. Frames and files asks for, to the numbers in design.md. In particular: Goldens: each room from a still camera, and one along-path helix view at t = 0.25. Check: the R3. Frames and files acceptance checks pass.
    5. Inputs (R4). Build what R4. 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 R4. Inputs 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.
    # 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 curves (R1).** Build what `R1. The curves` asks for, to the
    numbers in `design.md`. In particular: Each curve is a function r(t) for t
    in [0, 1], with the formulas in `design.md`.
       Check: the `R1. The curves` acceptance checks pass.
    
    3. **The ride (R2).** Build what `R2. The ride` asks for, to the numbers
    in `design.md`. In particular: A camera ride sets position to r(t) minus a
    documented offset along the normal, looking at r(t).
       Check: the `R2. The ride` acceptance checks pass.
    
    4. **Frames and files (R3).** Build what `R3. Frames and files` asks for,
    to the numbers in `design.md`. In particular: Goldens: each room from a
    still camera, and one along-path helix view at t = 0.25.
       Check: the `R3. Frames and files` acceptance checks pass.
    
    5. **Inputs (R4).** Build what `R4. 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 `R4. Inputs` 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.
    

    Open tasks.md as plain text

  • reference/preview.html A 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.css Webfont faces for the reference preview.
  • reference/fonts/Geist.ttf Geist variable typeface for the reference preview.
  • reference/fonts/Fraunces.ttf Fraunces variable typeface for the reference preview.
  • reference/fonts/Fraunces-Italic.ttf Fraunces 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 runner install 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, spec.json holds everything on this page, and bundle.tar.gz holds its files.