Skip to content

Latest commit

 

History

History
21 lines (16 loc) · 1.24 KB

File metadata and controls

21 lines (16 loc) · 1.24 KB

Ideas

Improvements this repo's work turned up for the tools it is built with, parked here because they belong in another repo. An entry leaves when it lands there.

writing-for-agents: name accretion as a pruning failure mode

Accretion — a clause added each review round, where the round's finding was that the site said nothing about some new case. Every round asks whether the sentence is right and none asks whether this site should carry the case at all, so an always-loaded description grows a paragraph of edge-case semantics while the field that owns them explains itself anyway. Duplication catches it only between files, never between a description and the thing it describes. The cure is the ladder: an always-loaded site states the gate ("unless X says otherwise"), and the lesson stays where the reader already is when it applies.

It belongs in the skill's Pruning section, beside director's commentary and snapshot.

Observed on the status tool's [Description] during the beacon-discovery review: four rounds each asked a prose site to state one new beaconFault/beaconListening distinction, and the description reached six lines about a state most sessions never see. Neither the duplication lens nor the conventions lens flagged it.