docs(prompts): date the lane rationales that restate overview-owned model facts - #1915
Merged
Conversation
…x discipline
The Models section justified two lane assignments with facts the models
overview page owns: `opus` for implementers ("the freshest knowledge
cutoff of the four") and `haiku` as a per-dispatch override only ("200k
context and an old cutoff"). Both resolve correctly against the live page
today, but they were restated with no citation, no as-of date, and no
recheck trigger — the one surface in the repo doing so outside the boris
vendor mirror.
Drop the bare `200k` in favour of the comparison it was standing in for,
and add the shape `docs/PLUGIN-PHILOSOPHY.md` already uses for its
tier-to-model mapping: figures declared upstream-owned and deliberately
not restated, a dated resolution, and a trigger. The trigger names the
failure mode specific to these two claims — they are derived orderings,
not quoted figures, so either can flip while every underlying number on
the page still reads correctly.
Verified against
https://platform.claude.com/docs/en/about-claude/models/overview,
fetched 2026-08-04 (HTTP 200, 29,119 bytes). Both orderings confirmed by
script off that capture rather than by eye: Opus 5 (May 2026) is the
freshest cutoff of the four current models, and Haiku 4.5 holds both the
smallest context window (200k against 1M) and the oldest cutoff
(Feb 2025).
No plugin touched, so no version bump and no changelog entry.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Contributor
|
Claude finished @kyle-sexton's task in 2m 19s —— View job Code review — PR #1915
Scope: single file, What changed:
Assessment: no defects found.
One minor, non-blocking observation: the trigger covers a new model family reaching GA or an alias re-resolving, but not an existing model's cutoff/context being revised in place (e.g., a dated snapshot update without a new family). This is a pre-existing gap in the mirrored |
|
Claude has reviewed this PR 1 time. The lane skips further automatic reviews after 5; deleting this comment resets the count. |
kyle-sexton
added a commit
that referenced
this pull request
Aug 4, 2026
… the tier ladder lacked (#1916) ## Summary Doc-alignment roster row 9: **Choosing the right model** (live page byte-identical to the archived slice — MD5 confirmed by producer and verifier independently against both the capture and today's live page). Row dispositions: - **IA-6 (vet-delta triggers): closed, nothing owed here.** Its mechanism half already shipped as criteria I21/I22 via the Q8 ownership carve-out (I22 carries all four trigger shapes, the delta-not-re-run discipline, and consumer-supplies-baseline); the instance half is dotfiles-owned. The targeted delta check was run anyway against the executed 2026-07-29 vet (issue #1697): no trigger fired. - **DOC-40 (four-question second lens): not shipped, correctly still routed to the dotfiles routing-doctrine seam** per its recorded disposition. - **OQ-6 (fast mode): deferral holds** — zero latency-first lanes exist, and model-config now documents `/fast` refusing to toggle under an allowlist that excludes the target, one more availability constraint on a research preview. **What ships (+15 lines, `docs/PLUGIN-PHILOSOPHY.md` only, no version bump per this file's precedent):** an enterprise `availableModels` dispatch-seam consequence the Model-tiers section lacked. Upstream (model-config, quoted character-exact): the allowlist reaches subagent/skill/command `model` frontmatter; a pin naming an excluded model "falls back to the inherited or default model rather than failing the request"; under `enforceAvailableModels` the Default remaps to the first *allowed, available* allowlist entry, and that remap reaches "the fallback used when an excluded selection is dropped". Consequence: a blocked pin can silently land **below** the session tier — the section's own invariant (consequential verdict at session tier or above) is not self-enforcing under an allowlist, and no error is raised. The paragraph states the failure mode, the operator action, and a non-vacuous recheck trigger. This is a dispatch-seam consequence, not a second selection checklist — DOC-40's declined shape. ## Test plan - Single file, +15/−0; markdownlint clean; parity scripts green; merge-tree clean vs current main. - Producer ran a two-round adversarial loop before handoff: a fresh Fable verifier falsified an advisor-recall claim (the paragraph's first draft asserted the *opposite* direction) against the primary source, and caught a vacuous recheck trigger; both fixed, then a second adversarial pass returned SHIP with one precision fix (the "allowed, available" qualifiers restored). - Orchestrator-commissioned Fable verifier: live-page sentence fidelity (three quotes character-exact, qualifiers present, anchor resolves), step-by-step reconstruction of the invariant-breakage scenario including the alias-resolution subtlety, IA-6 closure evidence (I21/I22 on main; carve-out record; delta-check spot-checks), contested-call boundary (no factor checklist restated), OQ-6 spot-checks, hygiene — **6/6 PASS, empty defect list**. ## Related - No linked issue. - Doc-alignment loop, roster row 9. Predecessors: #1908–#1915. Recorded for later: playbooks:boris transcribes "fast mode 3× cheaper" (Opus 4.8-era third-party claim) while this page's era has it premium-priced — third-party transcription, exempt from first-party staleness detection by I22's own fence; noted on the roster row, not patched inside a vendor mirror. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_019gaVX25Txd6GXdiu9HEH3X Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.
Summary
Doc-alignment roster row 8: Models overview — the docpage-digest profile's canonical model-fact freshness source. First repo capture of the page (29,119 bytes, MD5 recorded); systematic ten-dimension sweep of every repo surface stating a fact this page owns.
Sweep verdict: the repo is clean — pointer-not-copy holds everywhere except one surface. The single fix:
prompts/loops/loop-lane-prompts.mdjustified two lane assignments with bare, undated page-owned facts (opusfreshest-cutoff;haiku200k/oldest-cutoff). Both were true; the defect was discipline. The rationales now carry the sanctioned dated-matrix shape already used bydocs/PLUGIN-PHILOSOPHY.md's tier table: figures upstream-owned and not restated, a dated resolution (2026-08-04), and a recheck trigger naming the derived-ordering failure mode (either comparison can flip while every underlying figure stays correct). Operational instructions unchanged.Also verified in passing: the profile's canonical-freshness claim is structurally true (current matrix + legacy accordion in one fetch); #1911's three enqueue negatives re-confirmed against the live page; all agent
model:frontmatter still aliases; legacy placements and tier orderings consistent repo-wide. Component opportunity (a stored capture-and-diff freshness probe) declined: no upstream sync path for a hand-copied materialization, a one-consumer count, and the lightweight trigger shape already proved itself by producing #1912 — deferred with a trigger recorded on the roster row.Test plan
git merge-treeconflict-free against current main, decline-soundness and scope-call review — all PASS, empty defect list.Related
🤖 Generated with Claude Code
https://claude.ai/code/session_019gaVX25Txd6GXdiu9HEH3X