For the judge · The WebMCP Challenge

Everything, on one page.

No signup, no keys, no clone. Every number below is one you can check in the next few minutes, and the last section is what this project has not proved.

01The claim

mace is a clerk's bench for a meeting under Robert's Rules where the registered WebMCP tool set is the motion stack — an action that is out of order does not exist to be called.

Most agent apps hand over every tool and reject illegal calls at runtime. mace removes the tool instead. The panel “What is in order now” renders its left column directly from document.modelContext.getTools() — the API's own return value — so the screen and the API cannot disagree.

02The 30-second path

1. Open pointoforder.netlify.app. The count next to In order reads 5.
2. Click Widest frontier → 17. Click The tangle → 15.
3. At the tangle, look for move_to_amend_the_amendment. It is not greyed out and not refused — it is absent, and the right column prints the rule that removed it: §12, a first-degree amendment must be the immediately pending question.
4. Type 4 into Members in the room and press Record attendance. Quorum is 5, so 17 → 9 on one integer. The phase never moves; the whole agenda does (§40).
5. Open the console and check the panel is not lying:
   (await document.modelContext.getTools()).length — it equals the badge, at every checkpoint.

03The receipts

Measured against the live deploy in Chrome 151.0.7922.171, not estimated.

04Reproduce it

The real path — the same suite CI runs on every push:

# 306 tests, no network, no keys
git clone https://github.com/edycutjong/mace.git && cd mace
npm install
npx vitest run

To run the bench locally, serve it statically — there is no build step:

python3 -m http.server 8000   # then open http://localhost:8000

A local copy needs Chrome's WebMCP flag rather than the origin-trial token: the token is bound to pointoforder.netlify.app and will not activate on localhost.

05What this has not proved

Recorded because the honest absence is worth more than a tick.

• Zero external users. No practitioner has run a meeting through this. Nothing in the submission claims adoption, and none of the numbers above are usage numbers.
• The ChatGPT in-app browser fires no toolchange. It is otherwise verified: on 2026-08-30 (GPT-5.6) tools registered, getTools() answered, and the agent executed set_members_present through executeTool — the page went from PRESENT 0 · QUORUM ABSENT (§40) to PRESENT 7 · quorum present. But that client's modelContext is not an EventTarget, so the event never arrives and the panel polls getTools() until the surface settles instead. Chrome 151 remains the only client where the event path itself is exercised.
• No benchmark suite. The search figures are single live measurements against the deploy, described as such — not p50/p95 over repeated runs.
• Germaneness is never ruled on. It is not computable from a table, so the chair rules and the ruling enters the minutes. That limit is the design, not a gap — and it means mace cannot claim to enforce all of Robert's Rules.
• No small-board mode (§49). RONR relaxes procedure for boards under about twelve members. mace models the full rules only. An HOA board member raised this when I asked r/HOA how procedure works in practice, and they were right: most HOA boards qualify, so mace is stricter than the rulebook requires for exactly the audience it names. It is a second data file, not a rewrite — but it is not written.
• The meeting is seeded. A fictional HOA board log. It is not a dressed screen — every checkpoint replays through the same reduce() the live bench uses, and you can drive it forward yourself from any of them.

06Links