Understand
These pages explain the ideas behind discerndiscernA tool that lets you hand real work to coding agents and still decide what joins your project., so the next time your agent says a change is done, you'll know what to look at before you decide whether it lands.
For the overview of who does what, start with How discern works.
What can your project keep for next time?
§- Standards: how a measured gain becomes a limit every later change must meet.
- Instructions, skills, and the map: how what you teach one session reaches every later one.
- Improve how your agents work: finding what keeps slowing work down, from discern's local record.
The guides walk you through each task, and Reference has exact commands and settings.
In this section
§- ProofSee which of your project's commands passed on the exact commit you're reviewing, what that leaves for you to judge, and who decides whether it lands.
- Worktrees and trunkLet each agent build, break, and fix things in its own copy of the project, while your shared branch moves only when a change you've approved lands.
- CheckpointsHave the review questions that need judgment asked whenever a matching change happens, with your agent's answer in the Proof.
- StandardsLock in a measured improvement so every later change has to keep it, and decide for yourself when a limit should move.
- Instructions, skills, and the mapTeach your agents something once, and every later session starts out knowing it, whichever coding agent you use.
- What stays on your machineSee what discern runs, records, and writes on your machine, and where your coding agent and your own commands go beyond it.