@erclx/canon 5.63.0 → 5.64.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [5.64.0](https://github.com/erclx/canon/compare/v5.63.0...v5.64.0) (2026-10-24)
+
+
+### Features
+
+* **context:** remove the content classifier ([#2695](https://github.com/erclx/canon/issues/2695)) ([6d92b50](https://github.com/erclx/canon/commit/6d92b50bd0042a12d62574a034b1658eb6486e54))
+* **skills:** ledger the craft skill bodies on their concern groups ([#2700](https://github.com/erclx/canon/issues/2700)) ([02655a5](https://github.com/erclx/canon/commit/02655a5ede3879e572145316461e2c61e307985b))
+* **skills:** source every design-taste rule bullet in a ledger ([#2691](https://github.com/erclx/canon/issues/2691)) ([bb57e71](https://github.com/erclx/canon/commit/bb57e71e7db56ac4fc4d66f85e826b4ac2a3ae4a))
+
+
+### Bug Fixes
+
+* **claude:** resolve seeded records at either surface root ([#2696](https://github.com/erclx/canon/issues/2696)) ([288336c](https://github.com/erclx/canon/commit/288336c07c57c1a9b26a4cc6ea97c988f3338988))
+* **context:** skip the install stamp in the citation scan ([#2699](https://github.com/erclx/canon/issues/2699)) ([d2f0425](https://github.com/erclx/canon/commit/d2f0425bd33f69cf9f3529769d06e916a716b0d5))
+* **git:** leave deleted tracked paths out of the repository listing ([#2698](https://github.com/erclx/canon/issues/2698)) ([baa91e5](https://github.com/erclx/canon/commit/baa91e5a2a5d11bab9567bedf494eae5b63f7c09))
+
 ## [5.63.0](https://github.com/erclx/canon/compare/v5.62.0...v5.63.0) (2026-10-24)
 
 

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "canon",
   "description": "Runs your agent's work and keeps its code good, on one setup for every repo.",
-  "version": "5.63.0",
+  "version": "5.64.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/claude/skills/api-design/references/adopted.md

@@ -17,7 +17,7 @@ Adopted as the opening group, stated as design rules rather than as an observati
 
 ### One version per dependency
 
-[Software Engineering at Google, ch. 21](https://abseil.io/resources/swe-book/html/ch21.html) states the One-Version Rule, keeping one version of each dependency in a repository, so a change to it migrates every caller rather than leaving two versions live. Adopted under additive change for a caller that cannot pin, which is any module imported from inside one repository.
+[Software Engineering at Google, ch. 16](https://abseil.io/resources/swe-book/html/ch16.html) states the One-Version Rule, keeping one version of each dependency in a repository, so a change to it migrates every caller rather than leaving two versions live. Adopted under additive change for a caller that cannot pin, which is any module imported from inside one repository.
 
 ## Adopted from one external skill
 

package/claude/skills/context-fold/REQUIREMENT.md

@@ -16,14 +16,13 @@ The context entries describe the repository the session opened with. An entry ke
 - Name the context entries in a trigger phrase, so a bare request to sync the docs separates this skill from `docs-sync`
 - Take the refresh scope from the diff and write tracked docs at the current worktree root, only when the diff adds, moves, or removes a folder, falsifies a bullet, or changes a trap
 - Report a requirements or direction change in one line naming `document-health` rather than writing it
-- Close on `canon context audit` and `canon context classify diff` over the fold's whole baseline, reporting findings on files this run wrote or the diff carries
-- Apply a `REPLACE` or `HISTORY` finding against its quote, report a `MOVE` with its surface rather than cutting it, and continue the fold when a check cannot run
+- Close on `canon context audit` over the fold's whole baseline, reporting findings on files this run wrote or the diff carries
+- Continue the fold when a check cannot run
 
 ## Must not
 
 - Write the task board, the design record, `CLAUDE.md`, the requirements record, or a promoted page
 - Create an entry for a domain the catalog does not list, or report a finding on an entry this run never touched
-- Pick a classifier backend, re-run the classifier after a fix, or apply a finding whose quote is not found exactly once
 - Stop the fold on a finding, a refusal, or a missing subcommand
 
 ## Out of scope

package/claude/skills/context-fold/SKILL.md

@@ -62,7 +62,7 @@ Write each updated file immediately. Claude Code's tool permission dialog is the
 
 ## Step 4: audit what the fold touched
 
-Run the structural audit, the markdown audit, and the content classifier, and answer each before the report. Findings never stop the fold.
+Run the structural audit and the markdown audit, and answer each before the report. Findings never stop the fold.
 
 ### Structural audit
 
@@ -85,16 +85,6 @@ Run `canon markdown audit <path>` over every entry Step 3 wrote this run, and fi
 - Report a finding in a section Step 3 left alone as `⚠ Audit: <rel>, <finding>`, since the rule above keeps unrelated sections as they are
 - Report a refusal as `⚠ Audit: <message>` and continue
 
-### Classify
-
-Skip the classifier only when the Diff baseline section could not resolve a base ref at all, reporting `⚠ No diff to scope against. Skipped the classify check.` The verb needs a resolvable ref, which is the one condition it cannot answer for itself.
-
-Otherwise read `${CLAUDE_SKILL_DIR}/references/classify.md` for the invocation, its scope, the record fields, applying a finding, the one-line keep reason, the unreachable and missing-subcommand lines, and the report shape.
-
-- `${CLAUDE_SKILL_DIR}` names this skill's own directory, resolved once when the skill loaded, so read the reference by that resolved path
-- Never guess a `.claude/skills/context-fold/references/classify.md` path from the install-time layout, which is a different root than this skill's own files
-- The invocation is `canon context classify diff --base <base> --json`, and it runs whether or not that reference resolves
-
 ## After completion
 
 Read `${CLAUDE_SKILL_DIR}/references/completion-report.md` before printing anything, for the line each outcome prints, the lines Step 2 and Step 4 add, and when the closing line is suppressed.

package/claude/skills/context-fold/references/completion-report.md

@@ -1,6 +1,6 @@
 ---
 title: Completion report
-description: The lines context-fold prints once every step has run, being one per file updated, the direction-change note, Step 4's audit and classify lines, and the closing line with when it is suppressed
+description: The lines context-fold prints once every step has run, being one per file updated, the direction-change note, Step 4's audit lines, and the closing line with when it is suppressed
 ---
 
 # Completion report
@@ -9,15 +9,14 @@ The close of `context-fold`. The session reads this file once every step has run
 
 ## Lines
 
-| When                                                 | Line                                                                                        |
-| ---------------------------------------------------- | ------------------------------------------------------------------------------------------- |
-| Per file updated                                     | `✅ Updated: <path written>`                                                                |
-| Step 2 noted a requirements change                   | `↪ Direction changed this session: run document-health on canon/REQUIREMENTS.md`            |
-| Per audit finding Step 4 reported                    | `⚠ Audit:` in the shape the body gives                                                      |
-| Step 4's classify half applied or reported a finding | The exact shape `${CLAUDE_SKILL_DIR}/references/classify.md` gives under its Report section |
-| No file updated and Step 4 reported nothing          | `✅ No changes needed.`                                                                     |
+| When                                        | Line                                                                             |
+| ------------------------------------------- | -------------------------------------------------------------------------------- |
+| Per file updated                            | `✅ Updated: <path written>`                                                     |
+| Step 2 noted a requirements change          | `↪ Direction changed this session: run document-health on canon/REQUIREMENTS.md` |
+| Per audit finding Step 4 reported           | `⚠ Audit:` in the shape the body gives                                           |
+| No file updated and Step 4 reported nothing | `✅ No changes needed.`                                                          |
 
-Do not shorten or paraphrase the audit and classify lines here or in the reply, since the quote and the reason are what a reader checks the finding against.
+Do not shorten or paraphrase the audit lines here or in the reply, since the finding is what a reader checks it against.
 
 ## Suppressing the closing line
 

package/claude/skills/create-skill/references/skill-practice.md

@@ -9,7 +9,7 @@ Applies to a practice skill, one carrying engineering judgment a session applies
 
 ## Scope
 
-Governs the closing sections of a practice skill's `skills/<name>/SKILL.md` and the source ledger at `skills/<name>/references/adopted.md` beside it.
+Governs the closing sections of a practice skill's `skills/<name>/SKILL.md`, the source ledger at `skills/<name>/references/adopted.md` beside it, and the per-bullet ledgers a listed skill carries.
 
 Does not govern:
 
@@ -47,6 +47,21 @@ Follow every concern group with `## Excuses and rebuttals`, `## Red flags`, and
 - State what was adopted, what was declined, and why for each, so a later session extends the position rather than re-deriving it.
 - Draw first from the default shelf, [Software Engineering at Google](https://abseil.io/resources/swe-book/html/toc.html) and [Google's engineering practices](https://google.github.io/eng-practices/), and record a source from elsewhere the same way.
 
+## Per-bullet ledgers
+
+A skill whose files list outside-practice directives one per bullet takes a ledger per such file beside `adopted.md`, with one table row per bullet under each H2, the way a governance rule's ledger does.
+
+- Once a skill joins the per-bullet list `canon claude skills audit` keeps, every reference but `adopted.md` takes a ledger, so one added later fails until its rows land
+- Exempt by name a checklist restating rules a ledgered file sources, which would cite each source twice, and a glossary, whose definitions direct nothing
+- Mark the skill's `SKILL.md` for a ledger too when the body carries directives of its own
+- Keep the rows outside the plugin, so a target pays nothing for them
+- Move a source out of `adopted.md` once its row lands in a ledger, since two copies drift on the first edit. `adopted.md` keeps the catalog-level record and the sources behind any unledgered file.
+
+The audit counts a few lines in a ledgered file apart from a rule's.
+
+- Ledger a listed body's concern groups alone, every H2 before its closing sections or `## What this delegates`, since those restate the groups' rules or route
+- Give a top-level ordered step a row the way a bullet takes one, and a `## Contents` list none, since it repeats the headings
+
 ## Which skills are practice skills
 
 - `canon claude skills audit` keeps the list of practice skills and checks each listed one for the three closing sections and the ledger.

package/claude/skills/design-taste/references/adopted.md

@@ -1,11 +1,11 @@
 ---
 title: Adopted and declined
-description: Where each design-taste rule comes from, being a quoted authority, the community catalog of model-output tells, or a house threshold, plus what was declined and why
+description: Where each design-taste rule comes from, being a quoted authority, the community catalog of model-output tells, or a house threshold, where the per-bullet rows for the body and the rule references sit, and what was declined and why
 ---
 
 # Adopted and declined
 
-Every rule in this skill traces to one of three origins. A reader arguing against a rule finds its origin here, and a session extending the skill adds a row rather than re-deriving one.
+Every rule in this skill traces to one of three origins. A reader arguing against a rule finds its origin through this record, and a session extending the skill adds a row rather than re-deriving one.
 
 - **An authority.** A typographer, a usability lab, a platform guideline, or the CSS reference states the rule, and the row quotes the passage relied on.
 - **The catalog.** Community prompt skills recorded what models draw when nothing states a direction. A tell from them is an observation of model output, not established practice.
@@ -15,97 +15,41 @@ A rule a quoted passage only partly backs names the part it backs, and the rest
 
 ## Contents
 
+- [Where the rows sit](#where-the-rows-sit)
 - [The layer model](#the-layer-model)
-- [Craft rules an authority states](#craft-rules-an-authority-states)
-- [Systems rules an authority states](#systems-rules-an-authority-states)
-- [Tells an authority states](#tells-an-authority-states)
 - [The catalog](#the-catalog)
-- [House choices](#house-choices)
 - [Declined from the catalogs](#declined-from-the-catalogs)
 - [Declined from the systems reference](#declined-from-the-systems-reference)
 - [Carried as a caution](#carried-as-a-caution)
 
-## The layer model
-
-The body's layer order subdivides the five planes of Jesse James Garrett's [The Elements of User Experience](http://www.jjg.net/elements/). Its second chapter states the dependency the order rests on, that "Each plane is dependent on the planes below it."
-
-The same passage gives the constraint running the other way, that "the choices available to us on each plane are constrained by the decisions we make about issues on the planes below it". The nine layers and the grey-box stage are the skill's own subdivision of those planes.
-
-## Craft rules an authority states
-
-Rows for `craft.md`, grouped by its sections.
-
-### Type detail
-
-Each rule below is stated by the type reference or the CSS property that implements it.
-
-| Rule                | Source                                                                                                                                                        |
-| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Measure             | [Practical Typography](https://practicaltypography.com/line-length.html): "Aim for an average line length of 45–90 characters, including spaces."             |
-| Figures in columns  | [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/font-variant-numeric): `tabular-nums` sets figures "the same size, allowing them to be easily aligned" |
-| Small caps tracked  | [Practical Typography](https://practicaltypography.com/letterspacing.html): "always add 5–12% extra letterspacing to text in all caps or small caps"          |
-| Large type tighter  | The same page: typographers "will often remove letterspacing from lowercase text used at larger sizes"                                                        |
-| Orphans             | [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/text-wrap): `balance` suits "a short number of lines, such as headings, captions, and blockquotes"     |
-| Hanging punctuation | [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/hanging-punctuation): "An opening bracket or quote at the start of the first formatted line" hangs     |
-
-Casing is the `ui-craft` copy reference's, which `craft.md` points at rather than restating.
-
-### Optical size, hierarchy, and unfinished work
-
-The rows below back one bullet each. The error row backs the fix half of its bullet alone.
-
-| Rule                  | Source                                                                                                                                                          |
-| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Optical size          | [Wikipedia, Overshoot](https://en.wikipedia.org/wiki/Overshoot_%28typography%29): round letters overshoot "to achieve an optical effect of being the same size" |
-| Hierarchy from weight | [Practical Typography](https://practicaltypography.com/headings.html): with a bold heading, "you can also try reducing the point size"                          |
-| Where the reader is   | [NN/g](https://www.nngroup.com/articles/navigation-you-are-here/): "Navigation should not only show where you can go but also where you are now."               |
-| Error opens on a fix  | [NN/g](https://www.nngroup.com/articles/error-message-guidelines/): "offer some potential remedies"                                                             |
-
-That an apology should not lead the error is the catalog's observation, since the NN/g page allows one on a total failure.
-
-### Craft rules from the catalog
+## Where the rows sit
 
-The remaining `craft.md` rules are catalog observations of model output. They are optical centering, bottom-heavy padding, alignment across siblings, color and space carrying hierarchy, the shouting heading, every depth and texture rule, the dead link, the reused portrait, and the copy that reads unfinished.
+Each bullet in the skill body's concern groups and in `craft.md`, `kinds.md`, `systems.md`, and `tells.md` has its own source row in a ledger outside the plugin, one ledger per file and one row per bullet under the H2 the bullet sits under.
 
-## Systems rules an authority states
+- The toolkit's skill audit fails a ledgered file whose bullets and rows disagree in count under any heading, and a target never carries the rows
+- The body's `## What this delegates` takes no rows, since it routes rather than directs
+- `preflight.md` takes no ledger, since its boxes restate the rules the four ledgered references source
+- `vocabulary.md` takes none either, since it defines terms rather than directing
+- This record keeps the layer model behind the body's order, and what was read and declined
 
-Rows for `systems.md`. The counts it states sit under house choices below.
-
-| Rule                         | Source                                                                                                                                                        |
-| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Between groups beats within  | [NN/g](https://www.nngroup.com/articles/gestalt-proximity/): "Items close together are likely to be perceived as part of the same group"                      |
-| One gap everywhere fails     | The same page: a tight label reads as one group "compared to a larger margin before the next label-field pair"                                                |
-| Adjacent steps differ        | [Practical Typography](https://practicaltypography.com/headings.html): "Use the smallest increment necessary to make a visible difference."                   |
-| Fewer steps than feel enough | The same page: "Limit yourself to three levels of headings. Two is better."                                                                                   |
-| Weights beside sizes         | The bold heading passage under craft above                                                                                                                    |
-| Dark mode re-derived         | [Apple HIG](https://developer.apple.com/design/human-interface-guidelines/dark-mode): dark colors "aren't necessarily inversions of their light counterparts" |
-
-### Systems rules from the catalog
-
-Geometric spacing steps, space responding to the viewport, body size anchoring the scale, and line height moving opposite to size are catalog observations. Practical Typography gives a line spacing range for body text alone, so it does not back the last.
-
-Every palette rule but the dark mode row is catalog as well, being accent by rarity, one neutral temperature, the separation of surfaces from content, a semantic color kept off the accent, and the saturation budget.
-
-## Tells an authority states
+## The layer model
 
-Two tells and one application UI rule rest on a source rather than on the catalog.
+The body's layer order subdivides the five planes of Jesse James Garrett's [The Elements of User Experience](http://www.jjg.net/elements/). Its second chapter states the dependency the order rests on, that "Each plane is dependent on the planes below it."
 
-| Rule                              | Source                                                                                                                                                  |
-| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Unstyled platform control         | [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/color-scheme): it adapts "The default colors of form controls"              |
-| Transparency with no checkerboard | [Wikipedia](https://en.wikipedia.org/wiki/Transparency_%28graphic%29): an editor "shows transparency by a special pattern, e.g. a checkerboard pattern" |
-| Shortcut beside its command       | [NN/g](https://www.nngroup.com/articles/ui-copy/): shortcuts sit "to the far right of the menu" and "alongside the command text in tool tips"           |
+The same passage gives the constraint running the other way, that "the choices available to us on each plane are constrained by the decisions we make about issues on the planes below it". The nine layers and the grey-box stage are the skill's own subdivision of those planes.
 
 ## The catalog
 
-Every other tell in `tells.md`, and the ten defaults in the body, came from community prompt skills that recorded what models draw unguided. None of them is a design authority. Each tell is an observation of model output, falsifiable against a render, rather than established practice.
+Most tells in `tells.md`, and the ten defaults in the body, came from community prompt skills that recorded what models draw unguided. None of them is a design authority. Each tell is an observation of model output, falsifiable against a render, rather than established practice.
 
 - **[Taste-Skill](https://github.com/leonxlnx/taste-skill)** and its fork **[claude-taste-skill](https://github.com/nxpatterns/claude-taste-skill)** supplied the composition, content, surface, and motion tells
 - **[UI/UX Pro Max](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill)** was first read through a vendor listing and later from its repository. Its ranking puts accessibility first, and its lookup corpus was declined.
 - **[frontend-design](https://github.com/anthropics/skills/tree/main/skills/frontend-design)**, Anthropic's skill, supplied the five clusters current AI design falls into, restated in `tells.md`
 - **[Impeccable](https://github.com/pbakaus/impeccable)** supplied what a visual direction may lend an application screen and the category self-check, restated in `kinds.md`. Its themed browser surfaces lie behind the platform control tell.
 
-No sentence from any of them is copied. Each idea is restated and cited here.
+No sentence from any of them is copied. Each idea is restated and cited in the ledger row for its bullet.
+
+Most Taste-Skill tells came from its v2 experimental skill, which its author later moved to [taste-skill-classics](https://github.com/Leonxlnx/taste-skill-classics), and the rows link it there.
 
 ### Adopted with no change
 
@@ -115,30 +59,6 @@ The three equal cards, the centered hero over a wash, enumerated eyebrows, scrol
 
 Source items naming an icon set, a component library, a font by name, or an animation package were rewritten to state what the rule is about. "Do not use Inter" became one family doing every job, since the defensible claim is about pairing and role separation rather than about one typeface.
 
-## House choices
-
-Each threshold below is the toolkit's, chosen so a tell can be counted rather than judged.
-
-| Threshold                     | Source                                                                                         |
-| ----------------------------- | ---------------------------------------------------------------------------------------------- |
-| About eight spacing values    | House choice: past it, a count tells a scale from arithmetic on a finished surface             |
-| Five to seven type steps      | House choice: fewer forces size to carry every level, and more holds steps nobody tells apart  |
-| Two or three section tiers    | House choice: enough tiers for rhythm, few enough that each section takes one                  |
-| One marquee                   | House choice: a second sliding strip is where the device reads as filler                       |
-| Two consecutive splits        | House choice: a third alternation is where the pattern reads as filler                         |
-| Four first-screen text items  | House choice: a label, a headline, a supporting line, and the actions, so a fifth is countable |
-| One layout family, five items | House choice: a repeated shape and a long run become counts a reviewer can check               |
-
-The uppercase label count belongs to the `ui-craft` copy reference, whose own ledger records it as a house choice.
-
-### The focus ring's weight
-
-One more lock is the toolkit's own choice.
-
-| Threshold       | Source                                                                                                   |
-| --------------- | -------------------------------------------------------------------------------------------------------- |
-| One ring weight | House choice: a ring varying by component reads as several products. The `ui-craft` skill owns the floor |
-
 ## Declined from the catalogs
 
 Each item below is real advice placed in the wrong surface, or a rule that decides nothing.

package/claude/skills/design-taste/references/tells.md

@@ -77,7 +77,7 @@ The browser and the operating system draw some parts of every page, and a themed
 
 ## The countable limits
 
-These rules carry numbers, so they are checked by counting rather than by judging. Each number is a house choice made so the tell can be counted, and `adopted.md` records it as one.
+These rules carry numbers, so they are checked by counting rather than by judging. Each number is a house choice made so the tell can be counted, and its source row records it as one.
 
 - **A layout family appears once.** Once a section uses a shape, no other section on the surface uses it. Eight sections need at least four distinct families.
 - **Two consecutive splits, never three.** Alternating image sides reads as considered twice and as filler by the third. Break it with a full-width section, a vertical stack, or a grid.
@@ -96,4 +96,4 @@ These rules carry numbers, so they are checked by counting rather than by judgin
 
 ## Adopted, declined, and why
 
-Most items here are observations of what models draw unguided, gathered from community prompt skills rather than from a design authority. The record of which were adopted, which declined, and why sits in `adopted.md` beside this file, with the few an authority states and the links to the catalog behind the rest.
+Most items here are observations of what models draw unguided, gathered from community prompt skills rather than from a design authority. The record of which catalogs were read, which items were declined, and why sits in `adopted.md` beside this file, and it says where each item's own source row sits.

package/claude/skills/document-health/REQUIREMENT.md

@@ -16,7 +16,7 @@ Length, placement, and staleness answer to different evidence, and one list hand
 - Report per document across the length, placement, and staleness axes, marking each finding with its evidence class, read through the verb owning each measurement and its record's checkpoints
 - Propose a split or an owner as a structure line for each overgrown entry and doubled or unnamed coverage finding, with the headings and the reason
 - Ship the staleness axis as a reading rather than cutting it for lacking a verb
-- Report a refusal, an absent key, or a missing subcommand as an unread axis naming the cause, and say which layer answered the classifier sweep
+- Report a refusal, an absent key, or a missing subcommand as an unread axis naming the cause
 - Run standalone, reading the requirements record for drift with its reminder, and the design record through `canon design audit --json` and its review reminder, routing findings to `design-record`
 
 ## Must not

package/claude/skills/document-health/SKILL.md

@@ -34,16 +34,7 @@ canon markdown audit --json
 canon context audit --json
 ```
 
-The first answers length, carrying the bullet, paragraph, and depth checkpoints and the per-file weights read against them. The second answers placement for the folders it resolves, carrying entry length, reference form, and index drift.
-
-Then read which classifier would run, and deepen placement with the verdicts per section:
-
-```bash
-canon context classifier show
-canon context classify sweep --json
-```
-
-The first names the backend, the model, and the source that decided both. Report which layer answered, since a project with the model layer off reads from the regex layer alone and the sweep says nothing about which one it used.
+The first answers length, carrying the bullet, paragraph, and depth checkpoints and the per-file weights read against them. The second answers placement for the folders it resolves, carrying entry length, reference form, and index drift. Placement reads `shapeFindings`, `extraSections`, and each entry's `provenance`, all `measured`.
 
 Take the checkpoints from the record each verb returns rather than from a number written here. A checkpoint the CLI moves reaches this report with no edit, and a number held in this body goes stale on its own cadence.
 
@@ -58,7 +49,6 @@ Emit the line only for a folder with an entry past the line checkpoint whose Lay
 A refusal, an absent key, and a subcommand the project's binary does not carry each leave an axis unread. Report it as unread against the documents it would have covered, name the read that could not be taken, and name the cause.
 
 - `canon context audit` refuses with `reason: "no-folders"` where the layout is not the expected one. Reading that honest refusal as an empty finding set reports a healthy corpus nothing looked at.
-- A narrower read is not an unread one. The sweep running on its regex layer alone still answered, so report it with the layer named.
 
 ### The design record
 
@@ -92,10 +82,9 @@ Nothing triggers this review but a request. A finished review hands the rewrite
 
 Give each document its three axes, and give each axis three things: the state, the evidence class, and the command or skill that repairs it. Naming the repair is not running it. A length finding names `document-repair`, which rewrites a folder to zero and gates it.
 
-The three classes are what keep the axes apart:
+The two classes are what keep the axes apart:
 
 - `measured`: a verb returned a number read against a stated checkpoint
-- `classified`: a verb returned a verdict carrying its own confidence
 - `read`: this session's judgment, backed by no verb
 
 Emit no verdict across the three. Two answer from verbs and one answers from a reading, so a roll-up is a figure that lies about the third. Emit no score across the documents either, for the same reason one level up.
@@ -131,7 +120,7 @@ Structure `canon/context/surfaces/`: `cli.md` (300 lines) splits into `cli.md` t
 
 The line is a proposal for the operator, with the headings each entry takes and why. Health applies nothing, and `document-repair` offers the proposal before it rewrites.
 
-Keep the evidence line under the table on every run. A table read without it flattens a judgment into a measurement, which is the one shape the three classes exist to prevent.
+Keep the evidence line under the table on every run. A table read without it flattens a judgment into a measurement, which is the one shape the two classes exist to prevent.
 
 ### The design record row
 

package/claude/skills/document-health/references/axes.md

@@ -35,24 +35,25 @@ Weight is a judgment a reader settles rather than a defect, as the verb states f
 
 ## Placement
 
-| Field          | Value                                                                                                                    |
-| -------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| Measures       | Whether a document's content sits in the file that owns it, and whether the catalogs pointing at it resolve              |
-| Verbs          | `canon context audit --json` for the structural half, `canon context classify sweep --json` for the per-section verdicts |
-| Evidence class | `measured` for the audit's findings, `classified` for the sweep's verdicts                                               |
+| Field          | Value                                                                                                       |
+| -------------- | ----------------------------------------------------------------------------------------------------------- |
+| Measures       | Whether a document's content sits in the file that owns it, and whether the catalogs pointing at it resolve |
+| Verb           | `canon context audit --json`                                                                                |
+| Evidence class | `measured`                                                                                                  |
 
 The audit answers required sections, entry length, citation resolution, reference form, catalog tables, provenance, and index drift. Required sections reach context entries.
 
 - A citation resolving to nothing is a fact and gates
 - Entry length, reference form, table shape, and provenance are judgments under every flag
 
-### The sweep's verdicts
+### The audit's placement arrays
 
-The sweep classifies each section as keep, replace or rewrite, history, or move. A `move` verdict is the placement finding proper, naming content sitting in the wrong document.
+Three parts of the audit record name content sitting outside the shape its folder allows. Each is a count or a list the verb returned, so every placement finding is `measured`.
 
-- Each verdict carries its own confidence, which is why the class is `classified` rather than `measured`
-- A low-confidence `move` is a prompt to look rather than an instruction to cut
-- **Routes to:** the document the verdict names as the owner. Where the move crosses a tier rather than a file, the project's own content-ownership rules decide the destination.
+- `shapeFindings`: an entry whose sections break the shape its folder holds, such as a Decisions section or a sixth gotcha
+- `extraSections`: an H2 outside the closed set the folder allows
+- `entries[].provenance`: an entry narrating how it came to be, which is history rather than a description of the tree
+- **Routes to:** the document that owns the passage. The record names no owner, so the project's own content-ownership rules decide the destination.
 
 ### The structure line
 
@@ -66,12 +67,9 @@ The audit record's `length` array lists each entry past the line checkpoint, and
 
 A proposal names headings and a reason, so an operator judges a concrete split. A split nobody can act on names none of those.
 
-### When a verb resolves nothing
+### When the verb resolves nothing
 
-Both verbs resolve their folders by surface root rather than by a path written into them, so a project laid out differently resolves nothing. The two degrade differently.
-
-- The audit refuses with `reason: "no-folders"`, naming the folders it looked for. Report that refusal as an unread axis.
-- The sweep with the model layer off answers from its regex layer alone, a narrower read rather than a refusal, so say which layer answered
+The audit resolves its folders by surface root rather than by a path written into it, so a project laid out differently resolves nothing. It then refuses with `reason: "no-folders"`, naming the folders it looked for. Report that refusal as an unread axis.
 
 ## The design record
 
@@ -139,7 +137,7 @@ A reading is the weakest evidence in the report and the most consequential findi
 The axes are not equally actionable, and a report flattening them implies they are. Each is worth reporting and each is worth a different response, so the class travels beside the state on every row rather than once in a preamble a reader skims.
 
 - A length finding is a number against a checkpoint
-- A placement finding is a verdict carrying a confidence
+- A placement finding is a count or a list the audit returned
 - A staleness finding is a judgment with nothing behind it
 
 Shipping staleness on weaker evidence than the other two is the trade taken deliberately. Cutting it would leave the report answering the two questions that were never the operator's complaint.

package/docs/agents/audits.md

@@ -57,18 +57,15 @@ An audit that finds no corpus reports `absent`, which moves neither the verdict
 
 **In `bun run check`.**
 
-`bun run check` runs `--corpus tracked --corpus per-machine` as a reporting stage after the gating stages, and never fails on it. `summary` is a flat object of unique scalar keys that a shell stage greps without a JSON parser. `deps` runs weekly instead.
-
-The placement entry runs pinned to `--backend off`, so its tally stays comparable across machines. Each audit runs as the CLI the caller is running, never a global `canon`.
+`bun run check` runs `--corpus tracked --corpus per-machine` as a reporting stage after the gating stages, and never fails on it. `summary` is a flat object of unique scalar keys that a shell stage greps without a JSON parser. `deps` runs weekly instead. Each audit runs as the CLI the caller is running, never a global `canon`.
 
 **Catalog.**
 
-`canon audits list` reports the first 19 rows. The rows marked `outside` run by hand or from a skill and sit beside the aggregate.
+`canon audits list` reports the first 18 rows. The rows marked `outside` run by hand or from a skill and sit beside the aggregate.
 
 | Id                   | Verb                                | Measures                                                                           | Finding        |
 | -------------------- | ----------------------------------- | ---------------------------------------------------------------------------------- | -------------- |
 | `context`            | `canon context audit`               | Context folder structure, citations, and the requirements record's word cap        | Gates          |
-| `placement`          | `canon context classify sweep`      | Keep, rewrite, and move tally per context section, regex layer only                | Reports        |
 | `markdown`           | `canon markdown audit`              | Bans, dead links, density, and reference shape                                     | Gates          |
 | `skills`             | `canon claude skills audit`         | Both skill corpora against the skill standards                                     | Gates          |
 | `skills-reach`       | `canon claude skills reach`         | Skill bodies citing a path no target receives                                      | Reports        |
@@ -90,7 +87,6 @@ The placement entry runs pinned to `--backend off`, so its tally stays comparabl
 | `outside`            | `canon gov superseded <old> <new>`  | Where the tree still asserts a value a changed convention no longer produces       | Reports        |
 | `outside`            | `canon claude skills drift <ref>`   | Shipped skill bodies rewritten since a ref                                         | Reports        |
 | `outside`            | `canon claude routing`              | Per `CLAUDE.md` section, how many bullets name a path and whether a rule covers it | Reports        |
-| `outside`            | `canon context classify diff`       | Classification of the chunks a git range changed                                   | Reports        |
 
 A deliberate secret takes a `canon-allow-secret: <reason>` marker. A deliberate citation takes `canon-allow-citation: <reason>` and a deliberate superseded value takes `canon-allow-superseded: <reason>`, each on its own line or the one above. Run any verb with `--help` for its flags and refusal reasons.
 

package/docs/agents/context-audit.md

@@ -62,7 +62,7 @@ The exit code follows the mode the run took. The bullets cover where the gate ru
 - A root resolving no audited folder refuses with `1` and warns, a root measuring no entry warns, and a seed short a section fails with `2`
 - A seed omitting a required section on purpose sets `stub: true` in its frontmatter. Only the value `true` counts, and both install paths strip the field.
 
-The citation check skips fenced blocks, fixture and harness trees including `*.test.ts`, and a path into a folder the project lacks.
+The citation check skips fenced blocks, fixture and harness trees including `*.test.ts`, the install stamp at any of its spellings, and a path into a folder the project lacks.
 
 Append `<!-- audit-ignore-citations: <path> -->` to a line that displays a path without pointing at it. The marker excuses only the paths it names, and a bare `<!-- audit-ignore-citations -->` excuses every citation on the line. In seeds, plugin skill bodies, and stack references, which install into a target, reword the line instead.
 

package/governance/ledger/skills/api-design/SKILL.md

@@ -0,0 +1,62 @@
+---
+title: API design skill ledger
+description: Sources for claude/skills/api-design/SKILL.md, one row per bullet in its concern groups
+---
+
+# API design skill ledger
+
+The field is interface design across functions, flags, file formats, and endpoints. Google's API Improvement Proposals and its engineering book carry compatibility, the IETF carries the error and deprecation formats, and Stripe's own docs carry idempotency. The closing sections and `## What this delegates` restate these rules or route, so they take no table.
+
+## Decide what a caller can observe
+
+| Bullet                                 | Source                                                                                                                                                                                                                                                             | Read       |
+| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
+| A shape built for the caller           | [agent-skills, API and interface design](https://github.com/addyosmani/agent-skills/blob/2686b620fc1fed2e8f60c704839c766b8594c6b6/skills/api-and-interface-design/SKILL.md): "Don't leak implementation details. If users can observe it, they will depend on it." | 2026-10-24 |
+| Ordering, timing, and error text count | [Software Engineering at Google, ch. 1](https://abseil.io/resources/swe-book/html/ch01.html): "all observable behaviors of your system will be depended on by somebody", worked through hash iteration ordering                                                    | 2026-10-24 |
+| As small as the first caller needs     | [AIP-180](https://google.aip.dev/180): new components "may be added to existing APIs in the same major version", while "Removing a component is a backwards incompatible change"                                                                                   | 2026-10-24 |
+| One name for one concept               | [AIP-140](https://google.aip.dev/140): "APIs should endeavor to use the same name for the same concept and different names for different concepts"                                                                                                                 | 2026-10-24 |
+
+## Write the contract first
+
+| Bullet                             | Source                                                                                                                                                                                                                                                                         | Read       |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
+| The signature before the body      | [agent-skills, API and interface design](https://github.com/addyosmani/agent-skills/blob/2686b620fc1fed2e8f60c704839c766b8594c6b6/skills/api-and-interface-design/SKILL.md): "Define the interface before implementing it. The contract is the spec"                           | 2026-10-24 |
+| What it does, returns, and refuses | [agent-skills, API and interface design](https://github.com/addyosmani/agent-skills/blob/2686b620fc1fed2e8f60c704839c766b8594c6b6/skills/api-and-interface-design/SKILL.md): its contract names the refusal beside the return, "Returns a single task or throws NotFoundError" | 2026-10-24 |
+| Machine output on its own channel  | [Command Line Interface Guidelines](https://clig.dev/): "Log messages, errors, and so on should all be sent to stderr", so piped commands never feed them "into the next command"                                                                                              | 2026-10-24 |
+| The safe behavior is the default   | [Command Line Interface Guidelines](https://clig.dev/): "Confirm before doing anything dangerous", prompting interactively "or requiring them to pass -f or --force otherwise"                                                                                                 | 2026-10-24 |
+
+## Keep one error shape per surface
+
+| Bullet                           | Source                                                                                                                                                                                                                       | Read       |
+| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| A stable code beside the message | [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457.html): consumers "MUST use the "type" URI" as "the problem type's primary identifier", and "Consumers SHOULD NOT parse the "detail" member for information"                | 2026-10-24 |
+| No internals in the message      | [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457.html): generators "are encouraged to avoid making implementation details such as a stack dump available through the HTTP interface"                                        | 2026-10-24 |
+| Reuse the project's error type   | [agent-skills, API and interface design](https://github.com/addyosmani/agent-skills/blob/2686b620fc1fed2e8f60c704839c766b8594c6b6/skills/api-and-interface-design/SKILL.md): "Pick one error strategy and use it everywhere" | 2026-10-24 |
+
+## Validate at the boundary
+
+| Bullet                        | Source                                                                                                                                                                                                                                        | Read       |
+| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| Check once where input enters | [Parse, don't validate](https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-validate/): checks spread through processing deprive "the program of the ability to reject invalid input instead of processing it"                          | 2026-10-24 |
+| Trust the value inside        | [Parse, don't validate](https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-validate/): shotgun parsing mixes checks "with and spread across processing code", hoping "one or another would catch all the "bad" cases"                  | 2026-10-24 |
+| Parse into a typed value      | [Parse, don't validate](https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-validate/): "Get your data into the most precise representation you need as quickly as you can. Ideally, this should happen at the boundary of your system" | 2026-10-24 |
+| A value read back is input    | [OWASP Input Validation Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html): "Validate data from internal APIs, partner feeds, queues, and stored records when it crosses a trust boundary"        | 2026-10-24 |
+
+## Change additively
+
+| Bullet                                    | Source                                                                                                                                                                                                                           | Read       |
+| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| Optional, with the old behavior default   | [AIP-180](https://google.aip.dev/180): code written against the previous surface "must continue to be treated the same way as before. New required fields must not be added"                                                     | 2026-10-24 |
+| No rename or removal in place             | [AIP-180](https://google.aip.dev/180): "Renaming a component is semantically equivalent to "remove and add"", and a service "may add the new component, but must not remove the existing one"                                    | 2026-10-24 |
+| No new meaning or type under a name       | [AIP-180](https://google.aip.dev/180): fields "must not have their type changed", and APIs "must not change visible behavior or semantics in ways that are likely to break reasonable user code"                                 | 2026-10-24 |
+| One live version for an unpinned caller   | [Software Engineering at Google, ch. 16](https://abseil.io/resources/swe-book/html/ch16.html): "Developers must never have a choice of "What version of this component should I depend upon?"", named the One-Version Rule       | 2026-10-24 |
+| Deprecation recorded where a caller looks | [RFC 9745](https://www.rfc-editor.org/rfc/rfc9745.html): a response signals "that the resource will be or has been deprecated" and links "to a resource that provides further information about planned or existing deprecation" | 2026-10-24 |
+
+## Make a retried write safe
+
+| Bullet                                 | Source                                                                                                                                                                                                                                   | Read       |
+| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| Answer a repeat with the stored result | [Stripe idempotent requests](https://docs.stripe.com/api/idempotent_requests): "Stripe saves the status code and body of the first request made with a given idempotency key", and "Retries with the same key return the saved response" | 2026-10-24 |
+| Claim the key atomically               | [Implementing Stripe-like idempotency keys in Postgres](https://brandur.org/idempotency-keys): a unique index on the key, locked "so that no other requests that might be operating concurrently also try the operation"                 | 2026-10-24 |
+| A reused key with another body fails   | [Stripe idempotent requests](https://docs.stripe.com/api/idempotent_requests): the layer "compares incoming parameters to those of the original request and errors if they're not the same to prevent accidental misuse"                 | 2026-10-24 |
+| Keep the key past the retry window     | [Stripe idempotent requests](https://docs.stripe.com/api/idempotent_requests): keys go once "at least 24 hours old", and "We generate a new request if a key is reused after the original is pruned"                                     | 2026-10-24 |