# Commission: one work that can check itself

You build **one** web page as a single rawHTML artifact. What it is about, you decide, but not the way you would first expect. Several agents receive this text. You will be compared. Being interchangeable is the only way to lose.

---

## 1. Choose by elimination

Do not pick a topic. Find a **question or a claim** that your page can answer, test or demonstrate.

1. Write down **four** candidates. Each is one sentence, phrased as a question or a claim (not a topic like "tides", but "does X really do Y?").
2. The four must come from **four different fields of knowledge**. No two from the same discipline.
3. All four must touch your seed, without using it literally (see the end of this text). The seed is a constraint, not a subject.
4. **Strike the first two.** They are the ones everyone reaches for.
5. Choose **one of the last two.** Do not spend research time on the choice. Spend it on the building.

---

## 2. The one principle

**The work must be checkable on the work itself.**

Whatever the page claims, computes, measures or shows, a viewer must be able to test it there, inside the page: a control that makes the claim fail, a comparison that could have gone the other way, a number they can recompute. The text may explain, but it may not be the only place where the truth lives.

Test: delete the visual and keep the text. If the text stands undamaged, the visual was decoration. Start over.

Ask yourself throughout: what in this work could turn out to be wrong, and can a viewer find out?

---

## 3. The floor: not negotiable

- Without JavaScript, the full content stays readable.
- `prefers-reduced-motion: reduce` is respected, not softened, respected.
- No state the user cannot leave.
- Legibility before effect. Text on moving ground needs a solution, not hope.
- Everything you claim is true: numbers, dates, names, formulas. No invented sources. If you cannot verify it, do not state it.
- It runs on a phone.
- Write your page's language correctly. Diacritics are diacritics.

Tools are your choice. `mzone-ui` and `fonts-maierzone` are available and allowed, but not required. Anything that does the real work for you counts against your invention.

---

## 4. Process: do not skip this

1. Call `getCapabilities` once.
2. Build.
3. Run `validateArtifact`. Fix every console error and every layout problem it reports.
4. Read your own work as a hostile reviewer would. Name the two weakest things. Fix them.
5. Only then publish.

---

## 5. Hand-in: two parts

**The page.** {PUBLISH-INSTRUCTION}

**A report, English, at most 200 words**, in this order: Why this question? What was the hardest decision? What did you discard, and why? No marketing tone. If something did not work, say so. An admitted compromise costs less than a hidden one.

Outside the word count, list your **four candidates**, one line each, and mark the two you struck.

The language of the page follows what suits the work.

---

## 6. Your seed

{SEED}

---

You get one attempt. You will not be told a score, and there is no second round.

Do not start with the layout.