docs: add sequence diagram to how-ways-works model#191
Merged
Conversation
Claude Code repeatedly prompted to enable tui mode; tried it, hit bugs, turning it back off explicitly so it stops asking. Claude-Session: https://claude.ai/code/session_01TFyiQNDZ8RTMHX4Tnmp1wY
The model page carried a structural flowchart of the four observable behaviours, but a flowchart can't show the one thing that makes them matter: the matcher runs to completion before Claude sees anything, and a near-miss reaches events.jsonl but never reaches Claude. That asymmetry is temporal, so it wants a sequenceDiagram. Adds a "One turn, in order" subsection: User -> Matcher -> events.jsonl -> Claude, with the near-miss as a dashed arrow to the record only. Per the mermaid way, dropped <br/> from participant labels (fragile) and validated the render with mmaid. Claude-Session: https://claude.ai/code/session_01KDHroTCYH3VuCG3npY6Dzj
aaronsb
force-pushed
the
docs/how-ways-works-sequence-diagram
branch
from
1efdd32 to
77fe089
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a Mermaid sequence diagram to
docs/explanation/how-ways-works/how-ways-works-the-model.md(01.017.E), in a new "One turn, in order" subsection.Why
The page already had a structural flowchart of the four observable behaviours. A flowchart shows which behaviours exist; it can't show the temporal claim the prose makes — that the cheap matcher runs to completion before Claude sees anything, and that a
way_nearmisslands inevents.jsonlbut is never injected into Claude. The mermaid way's rule applies directly: content with a time axis is a sequence diagram.Details
User → Matcher → events.jsonl → Claude. Every event type writes to the record first; only cleared premises are injected into Claude.<br/>from participant labels (broke the terminal renderer, fragile on GitHub) and moved the cheap/expensive-substrate distinction into notes.mmaid -t blueprint; catalog lint passes (0 errors, 0 warnings).https://claude.ai/code/session_01KDHroTCYH3VuCG3npY6Dzj