PRESTON · IN CONCEPT

How Preston carries engineering judgment into every review.

Preston learns a repository once — the code, and the people responsible for it — and then reads every pull request against what it knows. The agent you already work with can ask it what it knows, over one endpoint, before you write a line.

These pages are about the second half of that: every finding, and every deliberate silence, traces back to its reason.

the codebase

what the code does, and the conventions it keeps

your team

decisions, promises, the standards you confirm

every change

read against all of it, so nobody has to remember any of it

a review

each finding, and each silence, with its reason

and back around: what you confirm, affirm or challenge is carried into the next one.

Color carries meaning across these pages, and you can pick it up as you go: red is the one that bites.

THE IDEAS

Standing
five values, and what each one lets Preston say
Corroboration
independent support, not repetition
Tension
both claims stand; the conflict is a third thing
Revision
a correction that names what it corrected
Grounding
a sentence points at what makes it true
Restraint
a decision not to say a true thing
Audience
the same position, said differently in different rooms
Composition
one sentence, every claim still addressable
What Preston won’t say
silence on purpose — the ledger, and the refusals
What Preston flags
a tension is a decision, not a defect
Principles & disciplines
an ordinary sentence becomes a team standard
Absence isn’t a gap
the same absence, three verdicts
Why does Preston think that?
every belief is one question deep

REFERENCE

The vocabulary
the words behind the words — look one up when you hit it
Connect
point any agent at Preston
What you can tell Preston
six things you can say, and what each one moves
The tools
one endpoint, a handful of verbs
The design system
the face, measured off the app that draws it