An item arrives
Add an issue from the Work page with Add work, or from a terminal withouterlayer work build --issue 42. Either way the item gets a number.
Build, or work build alone, asks a host to build the item. Build locally, or work build --local, leaves it for you to build yourself, and no host takes it.
That is the only way an item reaches the Work page. outerlayer work remove withdraws your request for it. The item leaves the Work page once no request for it remains, and its history is kept.
Sessions attach
A session attaches when you start it withOUTERLAYER_WORK set to the item’s number. The item must exist first: launching never creates one. Launch a session shows the command and what to type once the session opens.
The session shows up on the item’s page, with what it did and what it cost.
Pull requests join
A session on the item declares its pull request withouterlayer work pr 418. outerlayer work open-pr --title <text> --body-file <path> opens one and declares it in one step.
Checks build up
Checks are recorded on the item, so they hold across all its pull requests. A person’s own pass or fail is a review, recorded separately on the item page. Where checks come from:- Each validator file in
.outerlayer/validators/adds one check.outerlayer initwrites one,code-review: a code review result recorded. - The item’s recorded criteria count toward the verdict separately. An unproven criterion flags it.
- A missing criteria list flags it too, unless
criteria.missinglowers that.