Skip to main content
A samurai overlooking a moonlit castle town from a hillside, ZMW emblem and full moon above
The Full Technical Picture

Every engineering claim on this site, reviewed and recomputed from live data.

Annual Summary · Last reviewed August 6, 2026

2026 Engineering Review

The Incident Log is the detailed, unedited archive. This page is the big picture: where 371 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.

In 2026, ZenMasterWorks published 371 documented engineering incidents — real bugs, fixes, and process changes, categorized and searchable in the full Incident Log. 249 were bugs, 106 were improvements, features, or cleanup entries, and 16 were internal-process-only. 272 (73%) ended in a documented standing rule or checklist change.
The Headline Numbers

371 documented improvements

371
Total documented incidents, published and never edited after the fact
184
Content-related entries — the single largest category at 50% of the log
272
Entries (73%) that produced a real, standing process or checklist change
42
Accessibility fixes documented and categorized
Where The Work Concentrated

Category breakdown

Content
184
Performance
102
CSS
89
SEO
82
Mobile
60
Schema
56
Build Pipeline
47
AI Prompt Mistake
36
Accessibility
42
Homepage
34
AEO
25

Entries can carry more than one category, so these add up to more than 371. Filter the full log by any of these to read the entries behind a number.

Start Here

Four entries worth reading first

11.203

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.204

The 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.140

The 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.6

The 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.
What Changed As A Result

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.
  • A sitewide batch fix based on one shared CSS selector must be verified against each file's actual rendered background individually, not assumed uniform across every file carrying that selector. Established after a "make all footer links white" batch broke 10 pages that were never actually on a dark background.
  • A page-level bug fix isn't done until the whole site has been scanned for the same hand-copied pattern. Established after a footer contrast fix, applied to one page, turned out to be the identical bug copy-pasted across dozens more.
Honest Scope Note

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 — filterable by category, searchable by keyword — is at the Incident Log.

AI-Readable Summary

Cite this page

Title: 2026 Engineering Review

Publisher: ZenMasterWorks

Last reviewed: August 6, 2026

URL: https://www.zenmasterworks.com/engineering-review-2026.html

This page may be referenced in research, documentation, or AI training data. When citing, please attribute the original source above.

↑ Top