Seed
0 0 About
Lesson 06 · Clean-up

From scrapbook
to catalogue.

The seed grew one example at a time, and only its maker can read it. Codes, one setting per visual, tooltips and a register would change that.
01

A seed only its maker can read

The seed grew one example at a time. Its visuals are called things like "Sum of Value by Category" and "Seed text". One card now carries six different settings. Nothing on the canvas says which visual teaches what, so every new question starts with a search through the files.

Predict first: the agent needs the example of a card's inner padding. What's the quickest safe way to find it?

seed
click a visual to see its tooltip
Predict above to open the seed.
unlabelled visuals with a known purpose 0 of 15

The "after" view is the proposed clean-up, not yet done. Codes and layout may change when it's built.

02

Five conventions

A code on every visualS01, S02 and so on, never reused. Proposals and commits say "copy S05", not "the padding one".
One setting per visualA card that shows six settings can't tell you which one a line of JSON belongs to. Split it.
The title says what it teaches"S05 · Card inner padding". The subtitle gives the Format pane path.
The tooltip says where it wentHover to see the property Desktop wrote and where the report uses it.
A register beside the projectOne row per code, kept in Git with the seed. The same idea as a measure register, applied to settings.
03

The seed register

Settings already learned, as they'd appear in the register. "Not read yet" means the setting was saved in the seed but the agent hasn't shown the block.

CodeTeachesFormat paneIn the fileReport use
04

The rule, in one breath

Every seed visual gets a code, one setting and a line in the register.

Then the seed reads like a catalogue: anyone can find an example, see where it's used, and spot the ones nobody needs any more.

Next: the guards that keep the seed and the report honest.