chore(knowledge): remove the resources-overview entry from the docpage-digest queue - #1872
Merged
Merged
Conversation
…e-digest queue The platform.claude.com/docs/en/resources/overview slice ran end to end — raw-md fetch, per-unit digests, correction rounds, and dual verification on identical SHA-256-pinned bytes. Both verification arms returned PASS with no MAJOR findings, so the entry leaves the queue under the remove-on-completion rule. The "Supplementary references" heading stays: the system-prompts release-notes page sits under it as a separate concurrent run, and its own queue PR removes the heading once it empties. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Claude finished @kyle-sexton's task in 51s —— View job Review: PR #1872
Summary: Small, mechanical, well-scoped change. All three files are internally consistent and match the PR description.
Confirmed no other repo references to CLAUDE.md fresh-docs mandate: not triggered here — this edit touches doc-queue prose in a skill's context file, not a manifest/schema/hook-contract surface, so no live WebFetch verification was required for this change. No correctness, error-handling, or maintainability issues found. Nothing to flag for the security lane either (no code execution, no new external surface). |
|
Claude finished @kyle-sexton's task in 35s —— View job Security review complete
Scope reviewed: the 3 files in this PR's diff ( No security issues found. Details:
No GitHub Actions workflows, hook contracts, secrets/token handling, or authorization logic are touched by this PR. |
|
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 1, 2026
…ocpage-digest queue (#1873) The `claude.com/blog/building-verification-loops-in-claude-code-with-skills` slice ran end to end and reached dual verification, so its entry leaves the `docpage-digest` Anthropic doc queue under the queue's remove-on-completion rule. It was the last entry under **"Blog posts"**, so that heading is removed too. ## What ran - Raw-md fetch, per-unit digests (6 digests, 78 claim rows, **0 `api-only`** — every row is positive-tagged), correction rounds, and Phase 5 interview handoff. - **Dual verification on identical SHA-256-pinned bytes**: arm A and cross-vendor arm B both returned `VERDICT: PASS` with **no MAJOR findings**. - Arm B's coverage: 78/78 rows examined including all 44 `vendor-claimed` rows; 7/7 pin hashes matched; 50 commands replayed with every count agreeing; 78/78 source quotes exact including ellipsis placement; a structural platform-scope sweep over 68 candidate paragraphs found no unscoped absence claim remaining. ## Why this slice took extra rounds It exercised the **vendor-blog attestation rule** (profile 0.10.9) at scale. The rule's predicate names two properties — an assertion exists only in the blog when *"no harness **or platform** doc states the same assertion"* — so a `code.claude.com`-only search never establishes it. All 44 `vendor-claimed` rows now carry a **targeted row-local `platform.claude.com` check**, using `curl -sSL` for pages outside the snapshot subset per DIGEST-BRIEF §5. Exhaustiveness language stays scoped to `code.claude.com`; the platform half is stated as the check performed, never as corpus-wide platform absence. Residual MINOR findings are disclosed in the slice's `interview-handoff.md` as Open questions for the batched dispositions interview. ## What this PR changes - Removes the blog entry and the now-empty "Blog posts" heading from the profile's Doc queue. - Bumps the `knowledge` plugin `0.10.12` → `0.10.13`. - Adds the matching CHANGELOG entry. No linked issue ## Related - Second of three serialized run-11 queue PRs; follows #1872 (resources overview). All three touch the same profile file, so they merge one at a time. - Same queue-drain pattern as #1868, #1842, #1816. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
kyle-sexton
added a commit
that referenced
this pull request
Aug 1, 2026
…ge-digest queue (#1874) The `platform.claude.com/docs/en/release-notes/system-prompts` slice completed. It is the **last entry in the doc queue** — after this merges, the queue section holds only the deferred task-budgets trigger entry, which was never queued. ## What ran The largest slice this pipeline has processed: **18 digests over a 2,548-line source, 659 claim rows, 561 `api-only`.** - Seven correction rounds and five dual-verification rounds, each on SHA-256-pinned bytes with the frozen-tree rule enforced — both arms re-hash before *and* after auditing, and no correction runs while a verifier holds the tree. - Final state: both arms `VERDICT: PASS`, with a confirming round after the last corrections. - Final gates: **1,895 recorded command/count pairs replay with 0 mismatches**, 0 `<corpus>` placeholders, 659/659 rows parse with `N. Quote (line` count equal to `- Tag:` count in all 18 digests, every stated tally equal to its anchored `grep -c`, `check-quotes.py` clean. ## What the run found worth carrying forward - **Narrow-slug false absences** remained the dominant defect — a basis testing one literal while the corpus documents the same concept in other words. Rows now disclose near-misses by name and line, each produced by a command recorded in that row. - **Prose is unparsed by every gate.** Summary paragraphs, Implications bullets and Open questions carried stale counts and false statements across several rounds; two sweeps (one whitespace-normalized with an offset map back to physical lines) closed the class. - **A contested tag-ordering question is escalated, not decided** — whether selecting a positive tag requires first establishing harness applicability. It is written up as a candidate profile amendment with both readings, the evidence, and a recommendation, for the dispositions interview. Residual MINOR findings are disclosed in the slice's `interview-handoff.md` as Open questions, per the run's stopping rule. ## What this PR changes - Removes the system-prompts entry and the now-empty "Supplementary references" heading from the profile's Doc queue. - Bumps the `knowledge` plugin `0.10.13` → `0.10.14`. - Adds the matching CHANGELOG entry. No linked issue ## Related - Third and final of the serialized run-11 queue PRs, after #1872 (resources overview) and #1873 (verification-loops blog). All three touch the same profile file, so they merged one at a time. - Completes the queue drain begun in #1752 and continued through #1756, #1761, #1765, #1775, #1779, #1788, #1816, #1842 and #1868. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
kyle-sexton
added a commit
that referenced
this pull request
Aug 2, 2026
…d pipeline amendments (#1875) Applies the evidence-forced profile and pipeline amendments the docpage-digest campaign produced, and nothing else. `knowledge` 0.10.14 -> 0.10.15. ## What this ships Eleven normative rules across `SKILL.md` and `context/anthropic-docs-profile.md`, each mapping to a triage row marked `evidence-forced`: - **PA-A** row-local reachability — a cited `file.md:NN` counts as disclosed only when a command recorded in that same row produces it, plus the `| wc -l` and sampled-set corollaries. - **PA-B** a mechanical gate reports only what it parsed, and only the fields it checks; unrecognized input becomes a hard error *before* the gate is made required. - **PA-C** every correction round leaves an applied record, and its "New findings" section is a required input to the next round's brief; a verdict lands in `verification/` or it did not happen. - **PA-D** commands are replayable in every pipeline artifact, not just digest rows. - **PA-E** reconcile the digest set against itself before Phase 5. - **PA-G** every non-zero result names its match sites; a sampled hit set states that scope at the row. - **PA-R** absence-establishing fetches use the raw `.md` channel via `curl` and record the retrieved length. - Plus the frozen-tree rule (no tree moves until every dispatched arm has reported) and the `api-only` exact-command-and-raw-count basis. Both were forced by the record but had no triage row, because the triage never ingested the process-failure file; rows `PA-AL` and `PA-AM` were added to close that classification gap. ## Verification Two independent verifier arms, one adversarial, audited whether any amendment here is really a judgment call. Both concluded no: every rule maps to an `evidence-forced` row, nothing from the judgment-amendments file is present, and the escalated Decision-A ordering amendment (PA-AI) is untouched. Both arms then failed the branch on its *supporting evidence* — five parentheticals that misattributed an instrument, compressed defects spanning three jobs into "a single round", reported a written-but-unconsumed record as "left no record", blended a run-9 figure into a run-10 slice, and asserted a reconstruction the record does not describe. All five are corrected against primary sources and re-verified by two fresh arms. Rules were proven untouched mechanically rather than by eye: stripping every balanced parenthetical span and normalizing whitespace yields byte-identical remainders against the pre-correction commit (15,210 and 5,838 chars). No linked issue ## Related - Follows the three merged doc-queue PRs #1872, #1873, #1874, which emptied the digest queue. - Triage and judgment classification live in the campaign's memory tier under `.work/_harness-snapshots-2026-07-31/`, which is deliberately not committed. --------- Co-authored-by: Claude Opus 5 (1M context) <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.
The
platform.claude.com/docs/en/resources/overviewslice ran end to end and reached dual verification, so its entry leaves thedocpage-digestAnthropic doc queue under the queue's remove-on-completion rule.What ran
api-only), correction rounds, and Phase 5 interview handoff.VERDICT: PASSwith no MAJOR findings.llms.txthits mechanically verified; 57/57 quote anchors, row/tag parity, stated tallies and placeholder scans all clean.Residual MINOR findings are disclosed in the slice's
interview-handoff.mdas Open questions for the batched dispositions interview, per the campaign's stopping rule.What this PR changes
knowledgeplugin0.10.11→0.10.12.No linked issue
Related
🤖 Generated with Claude Code