Skip to main content

Module walkthrough

Module walkthrough 

Source
Expand description

The walkthrough: the agent’s own reading order for a review, one stop per real decision, each a span of code and a short reason. A stop is an agent comment carrying a title and an anchor, so the reader replies to it, the comments pane lists it and the card renderer draws it with no second system beside the first. A walkthrough is a review source of its own (ReviewSource::Walkthrough): every comment in that source’s session is this walkthrough’s, so nothing tracks ownership beyond stops itself.

Structs§

Receipt
Walkthrough

Enums§

Located
The outcome of pointing a target at a file’s current contents.
ReceiptCode
Target
Where a figure’s node, or a stop’s anchor, points. Resolution happens when it is drawn, never when it is written, so it keeps pointing at the right code after an edit moves it.

Constants§

BODY_MAX_BYTES
MAX_STOPS
A rail against dumping the diff, not a target: the skill asks for one stop per real decision, which lands well under this.
TOTAL_MAX_BYTES