Web Work run · September 23, 2026 · fictional inputs
One group question.
One working board.
Ergod made this self-contained decision board in its signed-in web Work surface. A person tested it, asked for a visual revision, found a display bug, and requested a final correction. The result remains open for you to try.

The request
For five fictional people, compare Friday and Saturday availability, count three game votes without inventing individual preferences, and recommend a time and game. The board needed live availability toggles, an honest tie state, a copyable channel announcement, a one-page A4 run sheet, and keyboard and phone support.
“Build a self-contained interactive HTML decision board for a fictional five-person community game night. This is a real usable page, not a mockup screenshot.”
The complete prompt and follow-up wording are preserved in the run notes.
What changed during the run
- First version. Ergod caught and fixed a game-vote tie bug during its own review. Independent checking found the logic worked, but the print view used two pages and the screen repeated too much process detail.
- Quality revision. The follow-up asked for a stronger decision summary, visible 4-versus-3 comparison, compact vote bars, and one-page print view. The revised file had blank bars because their width was applied to inline spans.
- Final correction. Ergod reattached the corrected file. Tests at 1280 and 390 pixels found no script errors or horizontal overflow. The vote bars displayed, the print view fit one A4 page, and turning off Eli's Friday availability changed the recommendation, announcement, and run sheet to a 3–3 tie.
Inspect each stage
First attached board ↗ · Revised board with the blank-bar bug ↗ · Corrected final attachment ↗ · Reviewed glyph fix ↗
Phone screenshot ↗ · One-page A4 print ↗ · Reproducible interaction check ↗ · Reviewed derivative note ↗
What this proves
The final file is a usable artifact that can be opened and changed. It also shows the normal shape of agent work: a first attempt, human feedback, a correction, and a checked result. This was a web Work run with fictional people and event details; it was not a Discord-room recording. The clipboard success message follows the browser copy call or fallback, but the system clipboard was not checked independently.