mellions-delegationlisted

<!-- Mellions Engineer | LetA Tech Ltd. | leta@letatech.ca --> # Running a session A session is a competent engineer who arrived this morning, has no memory of the programme, and cannot see your record. It has the repository, its own judgment, and whatever you tell it. That is the whole gap a dispatch has to close. ## What a dispatch carries ``` objective what must be true when this is finished repository the checkout, and the branch to work from authority what it may decide alone; what it must bring back scope what is in, and explicitly what is out invariants the few things that would be serious to break where the path it works in, cut before the dispatch is written current state what you already established, with the evidence skills by name — it reads the bodies itself references issue, file:line, prior PR — pointers, not pasted content evidence which claims will need what proof completion the condition, not the steps to reach it ``` **High specificity about the problem and the boundary. Near-zero prescription of how to think.** A dispatch that scripts the reasoning gets you a worse engineer than the one you have. Say what "done" looks like and let it find the route. ## The boundary is a path, not a paragraph Cut the tree before writing the dispatch: ``` mellions assign open -id <id> -repo <repo> -objective "..." ``` It prints a worktree on a branch of its own. That path is what the di