Lesson 07 · Guards
Blocked, checked,
looked at.
The guards that keep every setting in the report traceable to an example made by hand, and what to do when one of them stops you.
01
Six guards
The seed only helps if what's in the report can be traced back to it. These guards make sure it can.
No seed example, no buildThe generator refuses a property the seed hasn't shown. Seed first is enforced by code, not memory.
Seed committed firstThe seed gets its own commit before the report changes, so every block can be traced to its example.
Validator checks the shapeEvery visual is checked against the seed's shape. Each check is proven by breaking a copy on purpose.
Both values recordedThe register notes the seed value and the report value, like 4 px and 0 px.
Tests end with Don't saveTries in the real project are never kept outside a review.
The export stays frozenA file that was sent is never edited. A new version is a new export.
02
What would you do?
Predict first: the generator stops with "no seed example for this property". Is that a fault?
Predict above to try four more situations.
handled 0 / 4
03
What the seed isn't
Not a copy of the reportIt has a few small examples, not the real layout. Whether a setting works on a real tile is tested in the real project.
Not a list of defaultsIt holds only settings that differ from the theme. The theme holds the rest.
Not a test bench to save overEvery change to it is deliberate, saved, committed and recorded in the register.
04
The rule, in one breath
Every setting in the report can be traced to a seed example, a commit and a register line.
The agent is blocked without an example, checked after every build, and a person looks before anything is saved. That's what makes a fast agent safe to use.
That's the series. Back to the overview for the glossary.