# Run the Personal Brand landing-page benchmark

Build and publish exactly one new Personal Brand landing-page result with the model currently selected in the client. One model execution is one run. Do not create repetitions or variants.

Work autonomously from start to finish:

1. Confirm and record the active provider, exact model, highest available reasoning level, client, and client version. Stop if the selected model cannot be confirmed; never substitute another model. Immediately after confirmation and before benchmark work, start a reliable elapsed timer if the client exposes one or the environment can record the start explicitly. If no trustworthy measurement starts here, do not reconstruct or estimate a duration later.
2. Treat only this file, `BRIEF.md`, and `manifest.json` as inputs. Do not inspect previous results, screenshots, scores, reviews, unrelated project context, metadata, or additional skills.
3. Read `BRIEF.md` and `manifest.json`, choose a lowercase model slug, and create one schema-version-3 run record at `benchmark/runs/landing-<slug>.json` from `benchmark/runs/TEMPLATE.json`.
4. Build only the new output at `public/benchmark/landing/personal-brand-<slug>/index.html`.
5. Test the page in a browser against every requirement in the brief and manifest, including all four sections, real inline graphic, interactions, smooth navigation, mobile readability, and absence of console errors.
6. Capture a real hero screenshot at `public/benchmark/results/landing-<slug>.png`. Complete the artifact paths and honest browser evidence. This ends the comparable runtime window; integration and deployment time are excluded.
7. Record the elapsed whole seconds as `execution.runtimeSeconds` and set `execution.runtimeSource` to `client-measured`. Only use a duration measured from step 1. If no reliable measurement exists, pause here and ask Enrico for the elapsed runtime shown by his client (for example `18:42`); after he answers, convert it to whole seconds and use `user-reported`. Never estimate from timestamps, Git history, token counts, or memory.
8. Register the same `runtimeSeconds` in the matching `lib/benchmarks/data.ts` entry so it appears on the benchmark card. Do not write the runtime into the Landing Page itself. Run `node benchmark/scripts/validate-landing-page-run.mjs --run <slug>` and the repository checks.
9. Commit, push, publish the result to the existing live site, verify it there, and report the model, measured or user-reported runtime, result URL, commit, and validation status.

Never modify a completed result. If the execution is contaminated by earlier model output, discard this attempt and restart once in a fresh isolated session.