docs: fix README Deep-lane routing rule to match the implementation - #1
Merged
Conversation
The lane table read "4+ signals, or architecture / parallel surfaces / EVAL / irreversibility" — the pre-risk-gate rule. skills/triage/SKILL.md, rules/lcd.md, docs/why-lcd.md (pillar 5) and docs/vs-sdd.md all specify risk-gated routing: any hard trigger goes Deep, otherwise 4+ signals go Deep only when a risk signal (irreversibility or multi-session cold-pickup) is among them, and pure soft-signal accumulation caps at Standard. A reader following the README would over-route accumulated-file-count work into the full pipeline — the case the three-lane model exists to keep light. Also drops the stale "Once published to a marketplace" conditional. Docs only; no skill/command/rule prose touched, so no eval rows needed. Verified: tests/run.sh 9/9, claude plugin validate PASS. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014CfxbekXCXLz6EeqckNq6b
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.
The contradiction
The README lane table and the actual triage logic disagree on when work routes to Deep.
README.md:38(before this PR)skills/triage/SKILL.md:59rules/lcd.md:34docs/why-lcd.md:139docs/vs-sdd.md:94The README is the only file carrying the pre-risk-gate rule — it looks like a leftover from
before routing became risk-gated. Everything else in the tree agrees.
This matters more than a typo: a reader who scores 4 soft signals (files, surfaces, local
architecture, cold-pickup) and follows the README lands in the full
spec → plan → tasks → test-gen → red-green → auditpipeline, when the implementation deliberately caps that atStandard. The front door inverts the methodology's own core claim on exactly the case the
three-lane model exists to keep light.
Changes
README.md— lane table now states the risk-gated rule, with one sentence under the signallist spelling out the cap (file count alone never buys the heavy pipeline).
README.md— "Once published to a marketplace:" → "From the marketplace:" (LCD is published).CHANGELOG.md—Unreleasedentry, per CONTRIBUTING.Testing
tests/run.sh— 9/9 passclaude plugin validate .— PASSbenchmark is not implicated.
Also reviewed, no drift found
Skills (6), commands (8), bundled rules (7 +
lcd.md), hooks (3 matchers, scripts present),why-lcd.md's eight pillars, doc/example cross-links, the no-dependencies claim(
lcd-hooklib.shdegrades jq → python3 → node → empty, fail-open),quickstart.md'sonboarding description vs
skills/onboard/SKILL.md,monorepos.mdkeys vstemplates/lcd-conventions.md, and a full sweep for residual pre-rename strings (none).🤖 Generated with Claude Code
https://claude.ai/code/session_014CfxbekXCXLz6EeqckNq6b