Pyramid interior
A guided 3D walk through an original monument interior, with a camera path that hits documented waypoints and redistributable assets.
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/pyramid-interior- Version
- 0.2.2
- Published by
- nova
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/nova/pyramid-interior/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.Pyramid interior
What this builds
A tight WebGL walk through the interior of a monument. The model and the textures are original (or public-domain / permissively licensed scan data, listed in a licence file). The camera follows a path of waypoints. Tests assert the camera hits documented waypoints, take golden frames, and fail if a non-redistributable asset is present. This is not a branded tour of a real ticketed site.
Read
spekkr.inputs.jsonfirst.titleis at the first waypoint.pacemultiplies path speed; tests step the path by waypoint, not by wall clock.pathchooses the waypoint list.guideandplanchange the chrome.Out of scope
- Copyrighted scan data or a commercial tour's assets.
- A live guided-tour service or a booking form.
- Network or a stream of extra rooms in the checks.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. The path
- Each waypoint has a position, a look-at, and a caption. The
guidedpath isfixtures/pyramid-path.json. - A walk steps from one waypoint to the next. At each waypoint the camera position is within 0.05 units and the look-at within 0.05 units of the file.
- The
shortpath is the first four waypoints ofguided.
Accept when: every guided waypoint is hit within tolerance, and short ends at the fourth.
R2. Assets
- A
LICENCE.mdlists every model and texture and its licence, all redistributable. - A scan of the repo fails if a listed denied filename or a 'all rights reserved' asset without a redistributable grant is found.
- The model used in CI is the one in
assets/, not a network fetch.
Accept when: the licence file is present, the scan is clean, and a fetch hook stays quiet while loading the scene.
R3. Frames and files
- Goldens at entrance, a passage, the main chamber, and the plan view, at those waypoints, pace ignored because tests snap.
- One command runs the path, the licence scan, the hook, and writes the frames. No network.
Accept when: the command passes for both paths, 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
The camera path hits every documented waypoint within 0.05 units. Golden frames are taken at four of them. Assets used in CI are local and listed as redistributable; a licence scan and a fetch hook fail the build otherwise. No copyrighted commercial tour data.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to walk the path, how assets are licensed, and how to run the checks.
# Pyramid interior ## What this builds A tight WebGL walk through the interior of a monument. The model and the textures are original (or public-domain / permissively licensed scan data, listed in a licence file). The camera follows a path of waypoints. Tests assert the camera hits documented waypoints, take golden frames, and fail if a non-redistributable asset is present. This is not a branded tour of a real ticketed site. Read `spekkr.inputs.json` first. `title` is at the first waypoint. `pace` multiplies path speed; tests step the path by waypoint, not by wall clock. `path` chooses the waypoint list. `guide` and `plan` change the chrome. ## Out of scope - Copyrighted scan data or a commercial tour's assets. - A live guided-tour service or a booking form. - Network or a stream of extra rooms in the checks. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. The path - Each waypoint has a position, a look-at, and a caption. The `guided` path is `fixtures/pyramid-path.json`. - A walk steps from one waypoint to the next. At each waypoint the camera position is within 0.05 units and the look-at within 0.05 units of the file. - The `short` path is the first four waypoints of `guided`. Accept when: every guided waypoint is hit within tolerance, and short ends at the fourth. ### R2. Assets - A `LICENCE.md` lists every model and texture and its licence, all redistributable. - A scan of the repo fails if a listed denied filename or a 'all rights reserved' asset without a redistributable grant is found. - The model used in CI is the one in `assets/`, not a network fetch. Accept when: the licence file is present, the scan is clean, and a fetch hook stays quiet while loading the scene. ### R3. Frames and files - Goldens at entrance, a passage, the main chamber, and the plan view, at those waypoints, pace ignored because tests snap. - One command runs the path, the licence scan, the hook, and writes the frames. No network. Accept when: the command passes for both paths, 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 The camera path hits every documented waypoint within 0.05 units. Golden frames are taken at four of them. Assets used in CI are local and listed as redistributable; a licence scan and a fetch hook fail the build otherwise. No copyrighted commercial tour data. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to walk the path, how assets are licensed, and how to run the checks.
-
design.mdWaypoint cameras, chamber measures, and the redistributable asset 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.
Units
One world unit is 1 metre. The chamber dimensions and the waypoint file are the authority. The entrance is at (0, 1.6, 8), looking at (0, 1.6, 0), as restated in the file.
Screenshot tolerance
8 levels, 98% of pixels, 1600 by 1000, the documented camera.
Inputs
Key Label Default Notes titleTitle A walk inside Shown at the first waypoint. paceWalk pace 1.0 A multiplier on the camera path speed, from 0.5 to 2. guideShow a guide caption on A short caption at each waypoint. planShow a small plan on A top-down plan with the camera mark. pathCamera path guided guided is the full waypoint path. short is four waypoints, for quicker checks. 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 LICENCE.mdA shipped fixture. The build may move it, but then design.mdmust name the new path.fixtures/pyramid-path.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/gallery.pngThe gallery camera path, looking toward the lit chamber. 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.
- The camera path hits every documented waypoint within 0.05 units. Golden frames are taken at four of them. Assets used in CI are local and listed as redistributable; a licence scan and a fetch hook fail the build otherwise. No copyrighted commercial tour data.
# 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. ## Units One world unit is 1 metre. The chamber dimensions and the waypoint file are the authority. The entrance is at (0, 1.6, 8), looking at (0, 1.6, 0), as restated in the file. ## Screenshot tolerance 8 levels, 98% of pixels, 1600 by 1000, the documented camera. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A walk inside | Shown at the first waypoint. | | `pace` | Walk pace | 1.0 | A multiplier on the camera path speed, from 0.5 to 2. | | `guide` | Show a guide caption | on | A short caption at each waypoint. | | `plan` | Show a small plan | on | A top-down plan with the camera mark. | | `path` | Camera path | guided | guided is the full waypoint path. short is four waypoints, for quicker checks. | ## 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 | | --- | --- | | `LICENCE.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/pyramid-path.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/gallery.png` | The gallery camera path, looking toward the lit chamber. | ## 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. The camera path hits every documented waypoint within 0.05 units. Golden frames are taken at four of them. Assets used in CI are local and listed as redistributable; a licence scan and a fetch hook fail the build otherwise. No copyrighted commercial tour data.
-
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 path (R1). Build what
R1. The pathasks for, to the numbers indesign.md. In particular: Each waypoint has a position, a look-at, and a caption. Theguidedpath isfixtures/pyramid-path.json. Check: theR1. The pathacceptance checks pass. - Assets (R2). Build what
R2. Assetsasks for, to the numbers indesign.md. In particular: ALICENCE.mdlists every model and texture and its licence, all redistributable. Check: theR2. Assetsacceptance checks pass. - Frames and files (R3). Build what
R3. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens at entrance, a passage, the main chamber, and the plan view, at those waypoints, pace ignored because tests snap. Check: theR3. Frames and filesacceptance checks pass. - Inputs (R4). Build what
R4. 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: theR4. Inputsacceptance 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 path (R1).** Build what `R1. The path` asks for, to the numbers in `design.md`. In particular: Each waypoint has a position, a look-at, and a caption. The `guided` path is `fixtures/pyramid-path.json`. Check: the `R1. The path` acceptance checks pass. 3. **Assets (R2).** Build what `R2. Assets` asks for, to the numbers in `design.md`. In particular: A `LICENCE.md` lists every model and texture and its licence, all redistributable. Check: the `R2. Assets` 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 at entrance, a passage, the main chamber, and the plan view, at those waypoints, pace ignored because tests snap. 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.
- 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/Fraunces.ttfFraunces variable typeface for the reference preview. -
reference/fonts/Fraunces-Italic.ttfFraunces 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, spec.json holds everything on this page, and bundle.tar.gz holds its files.