2026 Engineering Review
The Incident Log is the detailed, unedited archive. This page is the big picture: where 203 documented improvements actually concentrated this year, and the standing rules they produced. Every number below is computed directly from the published log — nothing here is a separate claim.
203 documented improvements
Category breakdown
Entries can carry more than one category, so these add up to more than 201. Filter the full log by any of these to read the entries behind a number.
Four entries worth reading first
The AI-grading exercise that exposed how these tools actually grade
Four AI tools graded the same live pages the same day and produced four contradicting scores — then every "your schema is missing" claim among them turned out to be checkably false.
11.204The stale duplicate pages hiding inside our own /blogs/ folder
A routine schema check turned up three files quietly serving outdated copies of real pages at their own live URLs — invisible until someone checked file by file instead of trusting the nav.
11.140The zero-padding touch target that became a standing rule
A new footer button shipped too small to tap reliably. Every new interactive element added to a shared header or footer now gets touch-target-checked before it ships, not after.
11.6The fix that never got sent
Edits were made across several turns and never actually delivered. Every edit now ends with the file actually being shared — no exceptions.
Standing rules introduced this year
- No AI-generated grade or "you're missing X" claim gets acted on without checking the real file first. Established after five separate AI tools independently made false schema claims about pages that had the schema live and validated the whole time.
- Every new interactive element added to a shared header or footer gets touch-target-checked before it ships, not after. Established after a footer button shipped with a zero-padding touch target.
- Every edit ends with the updated file actually being delivered — no exceptions. Established after several turns of edits were made without the file-sharing step ever happening.
- A studio brand update or new checklist item must be audited across every page the studio owns, immediately — not just applied going forward. Established after a palette rollout and a new checklist rule each silently skipped existing pages.
- Any live, continuously-growing count (like this log's own entry count) gets re-synced sitewide as the very last step of a session that changes it — not just checked at the start. Established after the homepage's own incident-count stat drifted stale multiple times within the same session it was supposedly just fixed in.
What this page doesn't claim
This summary only includes what the incident log actually tracks today. Average time-to-resolution and a "percentage of bugs prevented by checklist items" rate aren't measured per entry — adding either would need a new tracked field going forward, not a retroactive estimate, so both are left out rather than guessed at. The full, unedited archive of all 203 entries — filterable by category, searchable by keyword — is at the Incident Log.