principle-encode-lessons-in-structure

What problem does it solve? Repeatedly writing the same instruction or correction wastes effort and fails to prevent recurrence, because textual guidance is easy to miss and requires readers to notice, remember, and comply. ## Core Features & Use Cases - Structural Encoding: Turns recurring fixes into lint rules, metadata flags, runtime checks, or scripts that enforce the rule without cooperation. - Strongest-Rung Selection: Guides choosing the strongest available mechanism, from unrepresentable states that cannot compile down to canonical helpers and runtime checks. - Feedback Loop Discipline: Captures every correction, routes it to the right layer (brain note, skill, lint rule, or principle), and closes the loop with concrete action. - Use Case: When you catch yourself telling an agent the same correction a second time, encode it as a CI lint rule or banned API instead of adding more documentation. ## Quick Start Apply this principle whenever you notice a recurring correction by asking whether it can become a lint rule, metadata flag, runtime check, or script, and encode it structurally instead of repeating the instruction.