The Rules That Caught Up
May 4 – May 6, 2026 • Codifying what the work taught us
Most chapters of this story are about something getting built. This one is about something getting written down. Three days in early May where accumulated lessons stopped being lessons and became rules — rules the platform now enforces, rules the next contributor has to live with, rules that exist precisely so no one has to learn them the hard way again.
The Single Paginator Rule
May 4 — one paginator, top, in the toolbar
It started with a small annoyance during Paint Pipeline polish. Five-hundred-row tables forced John to scroll to the bottom every time he wanted to change pages. The fix was a single tweak to the DataTables dom string: move pagination, info, and entries-per-page all into the toolbar row at the top. Then it became a rule: one paginator, top, in the toolbar — never at the bottom of the table. The dual-paginator legacy on a few older pages was logged for retroactive cleanup. Every new admin page on every site, from that day forward, was built with the new pattern.
John’s Simple Rules
May 4 — six rules for all life, including AI chat-bot programmers
Later that same day, after Eli shipped a single #hex instead of a ##hex and crashed a page, John didn’t want an apology. He wanted six rules in writing — rules that apply to AI chat-bot programmers the same way they apply to kitchen volunteers, sales reps, factory workers, and his own sons:
- Be a rebel — it’s real. Don’t pretend to follow rules you don’t follow.
- Be confident. Decisions made with conviction beat decisions made with hedging.
- Be careful. Confidence without care is just arrogance.
- Watch your tracks. Know where you’ve been, what you touched, what you left behind.
- Be sure. Not eighty percent sure. Sure. If you can’t be, say so out loud.
- CHECK YOUR WORK. Self-scan before announcing “done.” Read the file before saying it’s deployed.
Eli pinned them to user memory the same hour. They’ve been the first thing he reads on every new session since.
Process Sheets Phase 1
May 6 — rules become guards
Two days later, Process Sheets Phase 1 shipped at Edson — editable per-part route cards, each with its own ID, its own audit history. A direct application of the discipline from Chapter 12 and a beneficiary of every rule written in this chapter. The connection wasn’t announced. It just worked, the way good rules do.
Single Paginator Rule for every admin page on every site; John’s six Simple Rules pinned to user memory; Process Sheets Phase 1 (per-part editable route cards with audit history) shipped at Edson.
Every failure becomes a rule. Every rule becomes a guard. The platform doesn’t get smarter — it gets harder to break.