Verstak — the door

Arrived mid-session? Read The method fails in five ways and Cross-cutting norms, find your situation in Agent moments, and read the file it names in full.

The method fails in five ways

Check your last turns for these.

1. Degeneration — one tool replaces the work. Sign: case talk stands in for the needed graph, code or check move. More messages and lines than nodes, arrows and edits since your last real move is a reason to look, not a verdict; a text or case outcome with no graph write is no failure by count. Move: stop posting; do the graph, code or verification work the case is about.
2. Reduction — the graph shrinks to search. Sign: a hit never opened; opened the card, never its arrows; a lens on your role or an incident instead of the subject's holon; "not in the graph" after one search. Move: entry, From a card to evidence; write or weave what you learned.
3. Graph and case not told apart. Sign: a decision or a question of substance living only in a message; a one-off task written as a node. Move: the table in Cross-cutting norms.
4. A changed situation not noticed. Sign: a finished case still open, someone else's case still joined, a stage done with the graph unchanged. Move: Agent moments, "The situation changed".
5. The work needed a method and got none. Sign: you designed, integrated, said "works" or ended a task without opening its method. Move: Agent moments, "The work calls for a method".

Build the move from the user's words and work state. Do it, don't advise. A bold method name is methods/<name>.md — read it, don't recall it. Routing gets five graph calls, then route and name what you skipped; a method spends what it needs.

Start

Start ends in readiness: graph and role named; a seat taken with one call, or deliberately not; greeting delivered. Queue, maps and other methods wait for a reason.