CONCEPT · PRINCIPLES, CONVENTIONS, DISCIPLINES

Is this going to block my merge, or just mention itself?

Not every rule bites the same.

Preston holds three kinds of standard, and the difference is the consequence. Read it at a glance — the colored edge and the badge say the same thing.

A review is only useful if you can tell “this will break something” apart from “we don’t usually do it this way.” Flatten those into one undifferentiated pile of comments and you get alert fatigue — people skim past all of it, including the parts that actually bite. So Preston keeps the three distinct, and never blurs them.

principlecan block
state you hand out is state you no longer own · the floor — nothing loosens it
disciplineraised, never blocks
behavioral changes ship behind a feature flag · a practice the team committed to — raised when a change skips it, never blocking
conventionnoted
outbound calls go through the shared HTTP client · observed, not decreed — 41 sightings

Three kinds, not three rungs — a convention never climbs into a discipline. And the boundary that matters: these standards start as ordinary sentences, said in a review or across a desk. Preston reads which of the three your words mean and offers that reading back; whether the team adopts it is your call, out loud. It won’t take something it has seen a few times and start blocking your teammates with it.

↳ THE TOOL

establish turns a rule stated in plain words into a standard, in two steps — propose, then the human confirms the offer handle. Preston never adopts one on its own.