Secret page
A self-contained secret page: a wrong password fails, the right one reveals a fixture secret, and the file stands alone.
This is a small site spec on Spekkr, published by lume. 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
lume/secret-page- Version
- 0.2.1
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/secret-page/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 lume.
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.Secret page
What this builds
A single HTML file (with its script and styles inline, or beside it in a tiny folder) that hides a secret behind a password. The file is self-contained: opening it does not need a server, and the checks do not need a network. A wrong password fails. The right password reveals the fixture secret. The secret in the shipped fixture is a harmless phrase, not a real credential.
Read
spekkr.inputs.jsonfirst.titleis on the locked page.hintandhint_oncontrol a hint.attemptscaps tries.kdfchooses how the verifier is checked. The fixture password and secret are in a test-only file, not printed on the page.Out of scope
- A real production vault, a password manager, or storing real credentials in the shipped fixture.
- A network unlock or a third-party auth.
- Recovery of a forgotten password in this version.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Wrong and right
- The fixture file, opened (or loaded) without a server, shows the locked page. A wrong password shows a failure and does not reveal the secret.
- The right password, from
fixtures/secret-page.json, reveals the exact secret string in that file. - The secret is not present in plaintext in the shipped HTML; only a verifier and a ciphertext are.
Accept when: wrong fails, right reveals the exact secret, and a scan of the source does not contain the secret string.
R2. Limits, self-contained, frames
- If
attemptsis on, a documented number of wrong tries (5) disables the form until a reload. The sixth try is not checked. - A fetch hook fails if any host is contacted while unlocking.
- Goldens: locked, a wrong attempt, the revealed secret, and the limited state. One command runs the cases, the source scan, the hook, and writes the frames. No network and no server required.
Accept when: the fifth wrong try locks the form, the hook stays quiet, and the four 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 wrong password fails and a right password reveals the fixture secret. The shipped file does not contain the secret in plaintext. The page is self-contained: no server and no network, with a fetch hook to prove it. An attempt cap is tested. The fixture secret is harmless.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to build a new locked file, how to run the checks, and that real credentials must not be shipped as fixtures.
# Secret page ## What this builds A single HTML file (with its script and styles inline, or beside it in a tiny folder) that hides a secret behind a password. The file is self-contained: opening it does not need a server, and the checks do not need a network. A wrong password fails. The right password reveals the fixture secret. The secret in the shipped fixture is a harmless phrase, not a real credential. Read `spekkr.inputs.json` first. `title` is on the locked page. `hint` and `hint_on` control a hint. `attempts` caps tries. `kdf` chooses how the verifier is checked. The fixture password and secret are in a test-only file, not printed on the page. ## Out of scope - A real production vault, a password manager, or storing real credentials in the shipped fixture. - A network unlock or a third-party auth. - Recovery of a forgotten password in this version. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Wrong and right - The fixture file, opened (or loaded) without a server, shows the locked page. A wrong password shows a failure and does not reveal the secret. - The right password, from `fixtures/secret-page.json`, reveals the exact secret string in that file. - The secret is not present in plaintext in the shipped HTML; only a verifier and a ciphertext are. Accept when: wrong fails, right reveals the exact secret, and a scan of the source does not contain the secret string. ### R2. Limits, self-contained, frames - If `attempts` is on, a documented number of wrong tries (5) disables the form until a reload. The sixth try is not checked. - A fetch hook fails if any host is contacted while unlocking. - Goldens: locked, a wrong attempt, the revealed secret, and the limited state. One command runs the cases, the source scan, the hook, and writes the frames. No network and no server required. Accept when: the fifth wrong try locks the form, the hook stays quiet, and the four 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 wrong password fails and a right password reveals the fixture secret. The shipped file does not contain the secret in plaintext. The page is self-contained: no server and no network, with a fetch hook to prove it. An attempt cap is tested. The fixture secret is harmless. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to build a new locked file, how to run the checks, and that real credentials must not be shipped as fixtures.
-
design.mdThe self-contained file, the password check, and the fixture secret.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.
Fixture
Password and secret are in
fixtures/secret-page.json, used only by tests. The page ships a salt, a verifier, and a ciphertext. PBKDF2 parameters (iterations, hash) are indesignof the built file, and tests use those.Screenshot tolerance
8 levels, 98% of pixels. The revealed text must also match the secret exactly.
Inputs
Key Label Default Notes titleTitle A small lock Shown on the locked page. hintOptional hint not the year Shown under the field. May be empty. hint_onShow the hint on If off, the hint is not rendered. attemptsLimit attempts on A documented cap, after which the form is disabled for a session. kdfKey derivation pbkdf2 How the password checks a verifier in the file. The secret is decrypted only after a match. 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 fixtures/secret-page.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/lock.pngThe locked page, hint not the year, the fixture secret still hidden. 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 wrong password fails and a right password reveals the fixture secret. The shipped file does not contain the secret in plaintext. The page is self-contained: no server and no network, with a fetch hook to prove it. An attempt cap is tested. The fixture secret is harmless.
# 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. ## Fixture Password and secret are in `fixtures/secret-page.json`, used only by tests. The page ships a salt, a verifier, and a ciphertext. PBKDF2 parameters (iterations, hash) are in `design` of the built file, and tests use those. ## Screenshot tolerance 8 levels, 98% of pixels. The revealed text must also match the secret exactly. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A small lock | Shown on the locked page. | | `hint` | Optional hint | not the year | Shown under the field. May be empty. | | `hint_on` | Show the hint | on | If off, the hint is not rendered. | | `attempts` | Limit attempts | on | A documented cap, after which the form is disabled for a session. | | `kdf` | Key derivation | pbkdf2 | How the password checks a verifier in the file. The secret is decrypted only after a match. | ## 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 | | --- | --- | | `fixtures/secret-page.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/lock.png` | The locked page, hint not the year, the fixture secret still hidden. | ## 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 wrong password fails and a right password reveals the fixture secret. The shipped file does not contain the secret in plaintext. The page is self-contained: no server and no network, with a fetch hook to prove it. An attempt cap is tested. The fixture secret is harmless.
-
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. - Wrong and right (R1). Build what
R1. Wrong and rightasks for, to the numbers indesign.md. In particular: The fixture file, opened (or loaded) without a server, shows the locked page. A wrong password shows a failure and does not reveal the secret. Check: theR1. Wrong and rightacceptance checks pass. - Limits, self-contained, frames (R2). Build what
R2. Limits, self-contained, framesasks for, to the numbers indesign.md. In particular: Ifattemptsis on, a documented number of wrong tries (5) disables the form until a reload. The sixth try is not checked. Check: theR2. Limits, self-contained, framesacceptance 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. **Wrong and right (R1).** Build what `R1. Wrong and right` asks for, to the numbers in `design.md`. In particular: The fixture file, opened (or loaded) without a server, shows the locked page. A wrong password shows a failure and does not reveal the secret. Check: the `R1. Wrong and right` acceptance checks pass. 3. **Limits, self-contained, frames (R2).** Build what `R2. Limits, self-contained, frames` asks for, to the numbers in `design.md`. In particular: If `attempts` is on, a documented number of wrong tries (5) disables the form until a reload. The sixth try is not checked. Check: the `R2. Limits, self-contained, frames` 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/Fraunces.ttfFraunces variable typeface for the reference preview. -
reference/fonts/Fraunces-Italic.ttfFraunces italic variable typeface for the reference preview.
Is it for me?
- Kind
- small site
- Platforms
- web
- Tools
- HTML, JavaScript
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runner
What changed?
- 0.2.115 Nov 2026Names what it builds.
- 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.