dotfiles/claude/memory/skill-harvest-register.md

name, description, metadata, permalink

name	description	metadata	permalink
skill-harvest-register-proposed-skills-awaiting-steward-authorization	Standing register of skill create/patch/retire proposals surfaced by /wrap-up §1.6, awaiting steward authorization. The governed analog of PENDING.md, turned on our own tooling — propose → authorize → build → record. Surfaced every wake via this MEMORY entry.	node_type type originSessionId modified memory reference a8eb1d46-314e-4545-a133-f747c69ad5b4 2026-07-24T12:50:14.817Z	claude-memory/skill-harvest-register

Skill-harvest register

The single place proposed skills live so they don't evaporate between sessions. /wrap-up §1.6 proposes here; the steward authorizes; only then is a skill created/patched/retired (never autonomously — the loop is load-bearing, per PENDING-23). /wake-up surfaces the open proposals via this entry. The governed analog of ~/PENDING.md, for our own tools.

Status legend: PROPOSED (awaiting steward) · AUTHORIZED (proceed to build) · BUILT (done; move to the built-log) · DEFERRED (reason + condition) · REJECTED (reason; don't revisit without new input).

Compacted 2026-08-01 under the 2026-07-19 Stroke-4 authorization. This file is now the live index: every open proposal, one line each. Full rationale, origin and ruled history live in skill-harvest-archive.md (the previous register verbatim — nothing dropped). Ruled items are not listed here. Rows whose status was never marked are carried as PROPOSED? — unmarked is open until ruled, never silently closed.

⚖ FULL REVIEW 2026-07-19 (late night) — steward ruled ALL FOUR STROKES

This block is authoritative; per-section statuses below are superseded where they conflict. Physical compaction of the register = the same housekeeping slot as Stroke 2. (The 2026-07-12 steward request for this review is hereby discharged; REVIEWED-55 was separately resolved stale the same sitting — placed :489 since 07-12, PENDING-55 closed.)

Stroke 1 — Symmetria §3: consolidate, don't accumulate — BUILT SAME SITTING. Three consolidated flags + one widening landed in the skill (provenance-commented): assert-from-derivation-not-substrate (consolidates: claim-from-derived-artifact 07-03 jurist-elevated 3× · fuzzy-matcher membership 06-15 4× · soft-classification-over-checkable-claim 07-13 steward-named 5×/day · answer-from-training-before-banked-record 07-14 · re-derived-instructions 07-01 · enter-repo-read-docs-first 07-09) · completion-is-a-tripwire (recurrence-promoted per the governed watch-item pattern; folds gate-suite-blind-to-failure-class 07-07 · closable-now-is-a-claim 07-16 · reconcile-before-"finally" 07-17) · the-say-do-seam (record-asserts-applied-before-the-act · grounding-quoted-but-not-traced · consequence-trace-one-level-shallow — the 07-19 family) · trust-prior-pass-frame WIDENED (per-tier-demonstration 07-12 — the flag the steward queued — + claim-scope 06-28). NOT promoted (stay KG drift-patterns, wake-surfaced): probe-confirms-hypothesis · latency-isolation-first · reassuring-verb · tool-creep-into-substrate · solve-constraint-by-discarding-value · lost-the-forest · provenance-is-part-of-process · graduated-with-flagged-gap · convert-steward-state (redundant w/ contamination directives) · theorize-before-measuring-layout (redundant w/ causal-story) · reinvent-governed-DESIGN (widens the existing KG entry).

Stroke 2 — verification-ladder batch-append: AUTHORIZED; slot = next housekeeping pass. ALL earned ladder entries queued in this register (~25–30, from gate-itself-PASS-BUT-FALSELY and prose-word-guard through implement-the-relation-not-an-approximation and re-anchor=re-verify-by-sha-match; incl. the Fowler pair, CI-upper-bound-for-ESCALATE, positive-test-at-enforcement-path, method-class-vs-calibration, per-claim-citation) append to reference-verification-ladder.md with provenance, kin merged in the same pass. The ladder is the already-authorized canonical home (2026-06-05); this discharges the queue wholesale.

Stroke 3 — skills. BUILD (next session slots): /jurist-package (5-for-5, jurist-endorsed; ABSORBS /spec-amendment — supersession procedure goes to the ladder) · /model-handoff (3 proven uses + the path-verification authoring rule). CONFIRMED build-on-need (standing): /reconcile-open-work · /clone-test-runtime-fix · bmf-diagnose · /pre-build-audit · /measure-render · /version-essay. HOLD, named dependency: /graduate-chamber-source — build AFTER the one-door lane ruling (Eichmann pilot report §8.2); it would codify the very pipeline the ruling will change. BUILT SAME SITTING (small authorized patches): wake-up link-resolution canary · wake-up telos-conditional · feedback-governance-drafting-copy-paste-clean.md. RETIRED/REJECTED: mempalace-diagnose (wind-down done) · /wrap-up §4.a tags patch (overtaken by the 07-07 rewiring) · CLAUDE.md staleness canary (doc-currency-on-wrap covers it) · Fowler bad-smells lens (redundant w/ code-review) · /spec-amendment standalone (merged into /jurist-package). /vignette stays DEFERRED (condition unchanged since 06-05).

Stroke 4 — register compaction: AUTHORIZED; same slot as Stroke 2 (ruled items collapse to verdict lines; detail stays in git history — the register exceeded read caps 2026-07-19, its own tripwire).

Post-review additions to the Stroke-2 batch list (same authorization — "all earned ladder entries"; harvested from the pilot-ruling block later the same night): byte-check-hand-classifications-at-source-before-citing (two of my classes AND the jurist's Q3 assessment overturned by bytes — the F7 lesson, jurist-directed at F3's own numbers, discharged strengthening the finding) · coverage-metrics-are-blind-to-block-moves (jurist-minted from their own refuted assessment: any permutation preserving local windows passes coverage; refuted-by-default unless demonstrated on a block move — the demonstrated-not-composed instrument). No other harvest from the late-night block — the session's harvest WAS the ruled review; nothing manufactured.

Post-review addition (2026-07-22, PENDING-69 build — same authorization): read-the-gate's-decision-code-before-designing-its-consumer — before building a consumer/resolver for a gate's output, read the gate's OWN decision logic to know what it can and cannot mechanically produce or see. On PENDING-69 the inherited literal question forced reading verify_body_conservation.classify first: it revealed the gate classifies boundary runs by POSITION+SIZE only and provably cannot confirm class identity → that "no, and knowably no" shaped the honest design (attested declaration the gate consumes, not teaching it to classify) AND corrected my own package's mis-framing mid-build. Kin to render-and-LOOK / measure-toolchain-before-spec, one level over (read the substrate's decision logic, not just its output). Queue with the Stroke-2 batch.

Open proposals — live index (177)

#	Skill	Kind	One-line	Origin	Status	Archive section
1	bmf-diagnose	build now (a	Today WAS that need and the method is proven+fresh: process sample → log pattern census (`uniq -	2026-06-06 mindfabric-00 forensics	PROPOSED	New proposals (2026-06-06 wrap — awaiting st
2	``/wrap-up §5	patch	Palace-fully-derived, part 1: mirror every kg_add/kg_invalidate made at wrap into the sessio	2026-06-05 MemPalace forensics + t	PROPOSED	New proposals (2026-06-05 evening wrap — awa
3	``/wake-up §2.b	patch	Until upstream #1665 closes: wake searches run unscoped + post-filter by wing (wing-scoped `memp	2026-06-05 diagnosis	PROPOSED	New proposals (2026-06-05 evening wrap — awa
4	``/wake-up (new step or §2 check)	patch	Wake canary: seconds-cheap probe at wake — every MEMORY.md pointer + link resolves to an exist	2026-06-07 evening (memory-verdict	PROPOSED	New proposals (2026-06-05 evening wrap — awa
5	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-08 — harvested from F
6	**Revert-and-redo-smaller**	Symmetria §3 fla	Ch1's strongest working reflex we don't have: when a verification/gate fails and the cause isn	Symmetria §3 (a flag) or verificat	PROPOSED	New proposals (2026-06-08 — harvested from F
7	**Two-hat commit separation**	verification-lad	Name which hat each commit wears: a refactor commit's compiled output is byte-identical (or ca	verification-ladder (formalizes wh	PROPOSED	New proposals (2026-06-08 — harvested from F
8	**Bad-smells → refactoring lens**	reference card O	Ch3's smell catalogue (Mutable/Global Data, Duplicated Code, Shotgun Surgery, Speculative Genera	/code-review prompt or new refer	PROPOSED	New proposals (2026-06-08 — harvested from F
9	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-09 — the headless-Chr
10	**Headless-Chrome box-model measur	create skill OR	When a rendered layout differs and the cause isn't obvious, measure the box model before theor	a /measure-render skill, or a ve	PROPOSED	New proposals (2026-06-09 — the headless-Chr
11	**Symmetria §3 flag: theorize-befo	Symmetria §3 fla	The drift this caught, as a standing flag: a *causal story about why a layout renders as it does	Symmetria §3	PROPOSED	New proposals (2026-06-09 — the headless-Chr
12	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-09 pm — the typograph
13	**/measure-render (headless-Chro	create skill OR	RE-FLAG — strongly earned. Proposed this morning (compass fix); the pm session ran it 4+ more ti	/measure-render skill OR verific	PROPOSED	New proposals (2026-06-09 pm — the typograph
14	**Measure the font's true average	verification-lad	When setting a measure to a target character count, measure the font's average advance over real	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-09 pm — the typograph
15	**ARC build has NO autoprefixer —	feedback memory	ARC's plain-sass build adds no vendor prefixes. When introducing a new CSS property, check Saf	`feedback-arc-no-autoprefixer-hand	PROPOSED	New proposals (2026-06-09 pm — the typograph
16	**Justification-judgment bar = Bri	feedback memory	Load-bearing for the future justification decision: when living with the soft rag to judge wheth	`feedback-justification-bar-bringh	PROPOSED	New proposals (2026-06-09 pm — the typograph
17	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-10 — Stage-G close +
18	**spec↔spec coherence dimension**	patch `/spec-cod	The 2026-06-10 audit found §I.f-class contradictions — the measure (38→27.2rem) un-propagated ac	/spec-code-audit (new dimension)	PROPOSED	New proposals (2026-06-10 — Stage-G close +
19	**container-must-embody-the-contai	feedback memory	When producing an ARTIFACT of a spec (a PDF of the spec, a rendered sample), set it per the sp	`feedback-container-must-embody-th	PROPOSED	New proposals (2026-06-10 — Stage-G close +
20	**check-for-governed-tooling-befor	feedback memory	Before hand-rolling infrastructure (a PDF preamble, a build script, a template), grep the repo f	feedback memory or Symmetria §3	PROPOSED	New proposals (2026-06-10 — Stage-G close +
21	**byte-identical gate: hold/exclud	verification-lad	When proving a change byte-identical, a build-date/commit stamp (e.g. the colophon `_build_info/	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-10 — Stage-G close +
22	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-11 — §VII.f / open-wo
23	**Symmetria §3 flag: inherited-mar	Symmetria §3 fla	A status/marker inherited from a RECORD (a selector-index entry, a tracker line, a "-pending" fi	Symmetria §3	PROPOSED	New proposals (2026-06-11 — §VII.f / open-wo
24	**/measure-render (headless-Chro	create skill OR	RE-REINFORCED (4th day of evidence). Proposed 2026-06-09 (compass fix) + reinforced 06-09 pm; to	/measure-render skill OR verific	PROPOSED	New proposals (2026-06-11 — §VII.f / open-wo
25	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-12 — Studium planning
26	**/model-handoff(premium-model	create skill OR	When switching to an expensive/premium model (Fable 5 = 2× Opus rate; burn scales with context×s	a /model-handoff skill OR a refe	PROPOSED	New proposals (2026-06-12 — Studium planning
27	**verification-ladder: feature-det	verification-lad	A CSS @supports(feature) (or any capability probe) can return true on a platform where the fea	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-12 — Studium planning
28	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-12 night — Studium St
29	**verification-ladder: parse/valid	verification-lad	When an artifact that humans have only ever read (a hand-authored YAML index, a config, a data	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-12 night — Studium St
30	**clean cruft at the SOURCE layer,	feedback memory	When a source carries conversion cruft (EPUB footnote-links, image-scan embeds), clean it at the	`feedback-clean-at-source-not-down	PROPOSED	New proposals (2026-06-12 night — Studium St
31	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 — Studium Steps 3-
32	**dry-run-first for bulk file oper	verification-lad	When a mutation touches many files at once (mass git mv, graduation, rename), build it dry-run	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 — Studium Steps 3-
33	**Symmetria §3 flag: census-throug	Symmetria §3 fla	A filter/regex used to count or partition a set can silently mis-match and the count reads a	Symmetria §3	PROPOSED	New proposals (2026-06-13 — Studium Steps 3-
34	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
35	**Symmetria §3 flag: solve-the-con	Symmetria §3 fla	A "fix" that satisfies a stated constraint by removing the thing the constraint was protecting i	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
36	**verification-ladder: re-verify a	verification-lad	A sub-agent or background workflow that reports a per-item verdict from a dry-run on a temp copy	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
37	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
38	**Symmetria §3 flag: assert presen	Symmetria §3 fla	A presence/absence claim produced by a fuzzy/token matcher (filename tokens, embeddings, author-	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
39	``/wrap-up §4.b/§5	patch	Inline reminder at the KG-write step: kg_add object hard-caps at 128 chars — write short key	PROPOSED	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
40	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
41	**Work-in-omnibus: verify the inte	verification-lad	When a sidecar/scope brackets one work out of a multi-work source by heading-to-heading boundari	verification ladder	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
42	**studium-engine tool-evolution-lo	create	Establish the analog of chamber-library/_curation/tool-evolution-log.md for the engine tools (	studium-engine repo	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
43	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
44	**/version-essay**	create	The ADR-005 essay-versioning procedure, derived from essay-versioning-specification.md this se	new /version-essay skill	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
45	**CSS-mask: fill WHITE, not black	verification-lad	A CSS mask/-webkit-mask SVG must fill the shape white/opaque — a black-fill mask renders BLA	reference-verification-ladder	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
46	**live-CSS-patch in _site for fa	verification-lad	To eyeball size/style options in the real browser without a full Hakyll rebuild each round, `sed	reference-verification-ladder	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
47	**headless-Chrome element shot: sc	Symmetria §3 fla	Recalibration: computed box-clips kept mis-landing on the page-top (burned several shots). The r	reference-verification-ladder or	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
48	**glyph-outline → SVG from a woff2	method note (lad	Build a typographic SVG asset from the real font glyphs: fontTools SVGPathPen (path) + `Bo	reference-verification-ladder	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
49	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
50	**/wake-up patch — surface the *	patch	When the active workstream is studium-engine / The Making / ARC-as-public-proof (the engine's re	/wake-up §2.a + §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
51	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
52	**/clone-test-runtime-fix (CoW-c	create skill OR	When testing a runtime fix that needs real live data but must not touch the live instance: `/bin	new /clone-test-runtime-fix skil	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
53	**verification-ladder: verify the	verification-lad	Before reasoning about live behaviour, verify what the running process actually executes — compi	reference-verification-ladder	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
54	**Symmetria §3 flag: probe-confirm	Symmetria §3 fla	A query/test I constructed to match my hypothesis, whose result I then read as confirming the	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
55	**verification-ladder: quantify-th	verification-lad	When a fix removes a hot operation, the cleanest control isn't a flaky end-to-end before/after	reference-verification-ladder	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
56	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
57	**Symmetria §3 flag: diagnose-infe	Symmetria §3 fla	The load-bearing harvest. When a network/inference call is slow, the FIRST test must be the *iso	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
58	**Symmetria §3 flag: reinvent-gove	Symmetria §3 fla	Proposed PENDING-41 (consumer-hardware graceful degradation) as a novel architectural directio	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
59	**/graduate-chamber-source** (th	create	Codify the now-PROVEN OCR→canonical→graduation pipeline as a single governed discipline, so the	2026-06-26 Levi graduation	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
60	Element	Kind	One-line	Status	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
61	**/graduate-chamber-source** (al	EXPAND	Its empirical spec is now the full ocrmac column-aware pipeline, not the olmOCR one: render→ocrm	PROPOSED (expand; build-on-package	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
62	verification-ladder note: **OCR wo	ladder entry (pr	A verbatim word-guard that checks word PRESENCE cannot catch reading-order scrambling (2-col rea	PROPOSED	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
63	**2 research sweeps owed** (not sk	note	The engine's signature capabilities are greenfield: (1) genealogy/temporal/citation-graph/KG-aug	(project tasks, in research doc)	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
64	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
65	**/graduate-chamber-source** (al	EXPAND again	Now carries the full EPUB path (structure_from_ncx→insert_chapter_headings→`clean_pandoc_htm	new skill	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
66	**The gate itself can be PASS-BUT-	verification-lad	A verifier that checks an enumerated set of cruft signatures silently passes any residue outside	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
67	**Symmetria §3 flag: finding-scope	Symmetria §3 fla	A result true under a specific condition, restated as an unconditional rule, is contamination sh	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
68	**prose word-guard for faithful st	verification-lad	When a cleaner removes/reflows STRUCTURE (headings, printed titles, residue) but must preserve P	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
69	**structure-from-authoritative-ToC	method note (lad	Answer to the long-open unify question: chapter-structure recovery is ONE placement engine (`ins	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
70	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
71	**Symmetria §3 flag: tool-creep-in	Symmetria §3 fla	A convenience tool proposed for one job silently becoming the durable substrate (the source of t	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
72	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
73	**/graduate-chamber-source** (pr	BUILD NOW	The empirical spec is complete AND the rail it needs now exists (graduation-spec.yaml + `verif	new skill	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
74	**Symmetria §3 flag: graduated-wit	Symmetria §3 fla	Letting "honestly flagged" substitute for "resolved" — shipping a known-incomplete text because	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
75	**Symmetria §3 flag: re-derived-in	Symmetria §3 fla	Wrote agents hand-made instructions (and invented fields) instead of pointing them at `conversio	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
76	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
77	**Symmetria §3 flag: claim-from-de	Symmetria §3 fla	The load-bearing harvest — jurist-elevated to STANDING PRACTICE. I trusted a derived artifact /	Symmetria §3 + `reference-verifica	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
78	**/spec-amendment** (the RFC-sup	create (later)	The now-RATIFIED chamber amendment process as a codified discipline: normative spec change = a s	new skill	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
79	**per-claim citation verification	feedback memory	Caught by the jurist: I cited arXiv 2605.24229 for a claim it didn't support, having let a sub-a	feedback memory / ladder	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
80	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
81	**/spec-amendment** (proposed 20	**BUILD — deferr	The 2026-07-03/04 v2.0 drafting IS its first real exercise — the empirical spec now exists. Codi	new /spec-amendment skill	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
82	**/wrap-up §4.a**	patch	The §4.a drawer-filing step instructs passing tags: to mempalace_add_drawer — the tool rejec	`~/.claude/skills/wrap-up/SKILL.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
83	Element	Kind	One-line	Status	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
84	**verification-ladder: CI-upper-bo	verification-lad	The jurist RULED (2026-07-04) that grading on the one-sided 90% Clopper-Pearson upper bound (not	.05,40)=0.399); the CI does the re	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
85	**/model-handoff** (premium-mode	REINFORCED (exis	Used tonight end-to-end: produced `studium-engine/docs/stage-1-replan-scope-charter-2026-07-05.m	PROPOSED (reinforced)	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
86	Element	Kind	One-line	Status	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
87	**/model-handoff** (proposed 202	**REINFORCED — 3	Tonight was the first time the pattern ran END-TO-END as designed: fresh Fable-5 session woke in	PROPOSED (reinforced; +path-verifi	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
88	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
89	**CLAUDE.md staleness canary (git	create (small) O	If the scripts/ set or graduation-spec.yaml changed but CLAUDE.md didn't since, flag "may	git pre-commit / a `/repo-doc-cana	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
90	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
91	**memory/index restructure = byte-	verification-lad	When restructuring a memory index or any lossless-relocation of prose between files, do it as li	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
92	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
93	**quote a long-job ETA only from a	verification-lad	Twice today I gave a re-embed ETA from gut ("15–45 min") and was wrong by ~30×; the steward caug	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
94	**Symmetria §3 flag: reassuring-ve	Symmetria §3 fla	Reaching for a comforting characterization ("self-healed", "fine", "recovered", "handled") *befo	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
95	**mempalace-diagnose — RETIRE th	retire	AUTHORIZED 2026-06-05 (build-on-need). Now decorative: the steward decided (evidenced) to wind d	skill-harvest register	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
96	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
97	**/model-handoff(premium-model	**RE-FLAG — stro	Proposed 2026-06-12; this session built a full scope charter with the discipline (charter-on-O	new /model-handoff skill	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
98	**cross-volume verify-before-delet	verification-lad	Moving data across filesystems (internal→external cold archive): rsync -a → verify exact file-	tail` masks push failure — bit me	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
99	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
100	**verify at the granularity of the	verification-lad	A whole-set invariant (a document-wide word-multiset guard) can PASS while a per-item operation	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
101	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
102	**re-audit coverage with the TOOL'	verification-lad	When a classifier and the tool it feeds share a predicate, the classifier's mis-classification	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
103	**extending a tool re-tests its fo	verification-lad	Building an extension exercises shared machinery the original's tests never hit — so a widen's `	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
104	**classify a change by MECHANISM,	feedback memory	Reflexively labeled the recognizer generalization "PROPOSAL" because it felt large; the jurist	feedback memory or Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
105	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
106	**/reconcile-open-work(program	create	The practice proven twice now (ARC open-work register, then the whole Chamber→Gold→Engine regist	new /reconcile-open-work skill	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
107	**verification-ladder: retroactive	ladder entry	The jurist's Q1b principle, proven load-bearing: a stronger check existing and NOT pointed at ca	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
108	**verification-ladder: structural	ladder entry / S	The jurist's generalization after nested-block: "same risk as (a)" was true of the matching lo	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
109	**Symmetria §3 flag: lost-the-fore	Symmetria §3 fla	A long, productive execution session that costs the whole-program altitude is contamination shap	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
110	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
111	**check-the-register-before-a-subs	/wake-up §2 pa	Before starting substantial INFRA/tool building (a converter, a pipeline, a substrate), read the	/wake-up §2 (when the thread is	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
112	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
113	**Symmetria §3 flag: a check prove	Symmetria §3 fla	Reusing a verification method across a boundary it wasn't demonstrated on is contamination shape	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
114	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
115	**Symmetria §3 flag: soft-classifi	Symmetria §3 fla	Shipping a soft label ("this is reordering", "magnitude unresolved", "apparatus") when a CHECKAB	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
116	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
117	**split cause from magnitude befor	verification-lad	A diagnostic bucket keyed on ONE summary axis (magnitude, holds%, a deficit size) can hold heter	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
118	**confirm-a-named-cause-by-swap-in	verification-lad	When you NAME the true reference / config / cause behind an anomaly, don't assert the fix from t	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
119	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
120	**method-class-vs-calibration**	verification-lad	When a metric/gate fails to separate two cases, ask whether it is mis-CALIBRATED or structurally	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
121	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
122	**Symmetria §3 flag: answer-from-t	Symmetria §3 fla	Answering an architecture/tooling/citation question — or proposing a tool/approach — from traini	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
123	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
124	**positive-test-at-the-enforcement	verification-lad	For any "can X be bypassed?" / "is this gate skippable?" property, a negative grep proves the ab	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
125	**Symmetria §3 flag: convert-a-ste	Symmetria §3 fla	A proposal that converts an observed steward STATE (fatigue, "has carried a lot," being busy) in	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
126	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
127	**draft governance entries copy-pa	feedback memory	When drafting PENDING/REVIEWED entries for the steward to place, format them as clean copy-pas	a feedback memory (governance-draf	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
128	**Symmetria §3 flag / ladder: "clo	Symmetria §3 fla	The jurist named it a standing habit: the closable-vs-blocked partition on a work-list must be *	Symmetria §3 or `reference-verific	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
129	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
130	**/jurist-package** (create)	new skill	Draft a self-contained jurist package for a repo-blind reviewer: inline the ratified spec clause	new `.claude/skills/jurist-package	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
131	**ladder: reconcile against the AU	verification-lad	Before claiming a block/scope closed or complete, reconcile against the authoritative source (th	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
132	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
133	**governed spec-supersession proce	verification-lad	Landing a ratified spec version is: cp live→-vNEW.md → bounded Edits (never retype) → diff s	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
134	**verification-ladder / Symmetria	verification-lad	A factual claim's grounding must reach the file that HOLDS the fact, not one that merely describ	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
135	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
136	**implementation-is-a-second-gate*	verification-lad	A text passed by reading is re-tested by having to act on it — the jurist's own minting, aft	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
137	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
138	**sandbox-must-pin-the-shared-modu	verification-lad	When a test sandboxes module-level state (paths/constants), the patch must land on the SAME modu	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
139	**census-the-substrate-when-a-safe	verification-lad	A safety net (generic fallback, fail-loud branch, unrecognized kind) that never fires across N	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
140	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
141	**grounding-quoted-but-not-traced*	Symmetria §3 fla	The hook enforces QUOTING the ratified sections; this session proved quoting ≠ tracing: the coor	Symmetria §3, or a one-line additi	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
142	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
143	**Symmetria §3 flag: record-assert	Symmetria §3 fla	A session record (Addendum, brief, tracker line) composed AHEAD of its acts and asserting APPLIE	Symmetria §3	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
144	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
145	**re-anchor = re-verify: reconstru	verification-lad	When re-anchoring any sha-bound artifact after an upstream edit: reconstruct the OLD bound state	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
146	Element	Kind	One-line	Where it lands	PROPOSED?	New proposals (2026-06-13 post-clear — L1 /h
147	**implement-the-relation-not-an-ap	verification-lad	When code implements a RULED relation/contract (an equivalence relation, a gate criterion), the	reference-verification-ladder.md	PROPOSED	New proposals (2026-06-13 post-clear — L1 /h
148	Element	Kind	One-line	Where it lands	PROPOSED?	Harvest 2026-07-21 (the verify-guard complet
149	**seam-probe the artifact (gates t	verification-lad	The night's two REAL defects (empty footnote defs from per-spine -f html; defs-after-index swa	reference-verification-ladder.md	PROPOSED	Harvest 2026-07-21 (the verify-guard complet
150	**cmp-after-apply (tool-report ≠ w	verification-lad	strip_cruft --apply prints its transform counts BEFORE the write decision; three distinct refu	reference-verification-ladder.md	PROPOSED	Harvest 2026-07-21 (the verify-guard complet
151	**convert_lane_borndigital.py→	tool promotion	The one-door born-digital lane driver (whole-EPUB inject → whole-EPUB pandoc `-f epub -t markdow	scripts/	PROPOSED	Harvest 2026-07-21 (the verify-guard complet
152	/glyph-map-source	create	Per-source character-as-image glyph-mapping — the repeatable procedure built + proven on Levi th	2026-07-23 (built once, 12+ repeat	PROPOSED	Harvest 2026-07-23 (the PENDING-69/70 arc ·
153	Item	Kind	One-line	Origin	PROPOSED?	Harvest 2026-07-24 (evening — PENDING-71/72
154	Amendment-process: **reassigned-co	patch (chamb	Jurist-minted in the REVIEWED-72 ruling: *"when a change reassigns a named component, check what	2026-07-24 (jurist-directed)	PROPOSED	Harvest 2026-07-24 (evening — PENDING-71/72
155	Chamber graduation: **build to the	patch (chamb	Steward-corrected 2× this session: "we cannot use the extant canon as precedent." The extant c	2026-07-24 (steward-directed)	PROPOSED	Harvest 2026-07-24 (evening — PENDING-71/72
156	Element	Kind	One-line	Where it lands	PROPOSED?	Harvest 2026-07-24 (evening — PENDING-71/72
157	chamber-library CLAUDE.md — **inte	patch (repo CLAU	Add to §Load-bearing disciplines: *"The fleet has UNIT tests (test_tools, per-tool fixtures) but	chamber-library/CLAUDE.md §Load-	PROPOSED	Harvest 2026-07-24 (evening — PENDING-71/72
158	Target	Kind	Proposal	Evidence	PROPOSED?	Harvest 2026-07-28 (morning — governance blo
159	``/wake-up §2.c–2.d	patch	Consume the SessionStart digest instead of recomputing it. wake-digest.py now fires at every S	Built + wired 2026-07-28; the wake	PROPOSED	Harvest 2026-07-28 (morning — governance blo
160	``/wake-up §2.a	patch	Fix the link-resolution canary's path handling — resolve pointers against the memory file's *phy	Second firing. Proposed 2026-0	PROPOSED	Harvest 2026-07-28 (morning — governance blo
161	reference-verification-ladder.md	new entry	"The parser defines the census." When a census counts items, the item-definition is itself a c	Earned hard 2026-07-28: `^## PENDI	PROPOSED	Harvest 2026-07-28 (morning — governance blo
162	Target	Kind	Proposal	Evidence	PROPOSED?	Proposed 2026-07-28 (afternoon wrap — PENDIN
163	``/symmetria §3	patch	Add the contamination flag: "an instrument whose evidence is the same kind of thing as its own s	*Four instances in one afternoon	PROPOSED	Proposed 2026-07-28 (afternoon wrap — PENDIN
164	``/wrap-up §6 / §6.5	patch	Verify that every file a commit message names is actually staged, and that steward-authored edit	8abfe88 claimed *"split 1848→430	PROPOSED	Proposed 2026-07-28 (afternoon wrap — PENDIN
165	~/dotfiles/scripts/	new script	Promote the union-losslessness verifier to verify-union-lossless.py <baseline> <part>... — ass	Written ad hoc in scratchpad for t	PROPOSED	Proposed 2026-07-28 (afternoon wrap — PENDIN
166	``/wake-up §2.a	patch	(Re-proposing, third firing.) Link-canary path resolution — root cause now precise, not merely r	Fired 2026-07-27, and twice on	PROPOSED	Proposed 2026-07-28 (afternoon wrap — PENDIN
167	/wake-up	patch	Read the day's own Symmetria ledger when one exists for today. The wake reads MEMORY.md + the	2026-07-28 (2 instances, ~10 min a	PROPOSED	Harvest 2026-07-28 (mid-afternoon — the V-DP
168	/jurist-package	patch	Require a mechanical verbatim-containment proof over every quoted clause, reported in the packag	2026-07-28 (self-caught fabricatio	PROPOSED	Harvest 2026-07-28 (mid-afternoon — the V-DP
169	Target	Kind	Proposal	Earned by	PROPOSED?	New proposals (2026-07-29 wrap — awaiting st
170	/jurist-package	patch	Mandate a mechanical verbatim-containment proof over every quoted passage, with a positive AND n	2026-07-29; second instance of the	PROPOSED	New proposals (2026-07-29 wrap — awaiting st
171	/jurist-package	patch	Formatting convention: ratified text = > blockquote; PROPOSED text = fenced block, never a blo	2026-07-29, found incidentally by	PROPOSED	New proposals (2026-07-29 wrap — awaiting st
172	``/wake-up §3 (Next move)	patch	Before executing an inherited resumption point, grep the substrate for whether its premise is al	2026-07-29	PROPOSED	New proposals (2026-07-29 wrap — awaiting st
173	Target	Kind	Proposal	Earned by	PROPOSED?	New proposals (2026-07-29, steward-raised —
174	``symmetria §4 (ledger template)	patch	Add a standing ## What held section — instruments that fired prospectively, lessons that tra	2026-07-29, steward-raised; corrob	APPLIED 2026-08-02 (FIX lane, REVIEWED-85 batch 1)	New proposals (2026-07-29, steward-raised —
175	``/wrap-up §5 (KG append)	patch	Add a prevention predicate — `{subject: , predicate: "prevention", object: <the	same	APPLIED 2026-08-02 (FIX lane, REVIEWED-85 batch 1)	New proposals (2026-07-29, steward-raised —
176	``/wake-up §2.b.2	patch	Surface one prevention alongside the drift-patterns. Currently the wake greps only `drift-patt	same	APPLIED 2026-08-02 (FIX lane, REVIEWED-85 batch 1)	New proposals (2026-07-29, steward-raised —
177	``symmetria§2 //wrap-up §1	patch	Retire the self-report framing of the standing question. The 2026-07-29 literal question — *"is	2026-07-29	APPLIED 2026-08-02 (FIX lane, REVIEWED-85 batch 1)	New proposals (2026-07-29, steward-raised —
178	/fool	create	Build WHEN STABLE, not now. The differently-formed-checker trial protocol, derived twice this session: withhold the ruling; pre-register grading before the run; prompt gives form not target (+ anti-contrarian + anti-echo clauses); enable_thinking ON (off produces silence, not brevity); one variable per trial; no standing granted to the Fool — only checkable claims get standing. Codifying it now would freeze an unstable protocol; the steward has directed next session at stabilising it. Interim home: dotfiles/claude/governance/fool-trial-log.md.	2026-08-01/02, trials 01–02	PROPOSED (build-when-stable)
179	wake-digest.py	patch [FIX-class]	The wake instrument silently hides open items. sec_pending() drops a PENDING-N whenever a REVIEWED-N exists — matching the number alone, never checking the ruling is about that item. Numbering has drifted (REVIEWED-84 rules on PENDING-87), so PENDING-84 was invisible at wake on the very morning the steward's pulling thread pointed at it; closing it later produced no visible count change. Measured: 9 suppressed, 8 correctly, 1 falsely. Fix: resolve by the ruling's subject line, not its number.	2026-08-01 (found at wake, surfaced not fixed)	PROPOSED
180	normalize_ocr.py (chamber fleet)	patch [FIX-class]	Silent degradation with no disclosure. dict_state reports only the static word list, so a --lang fr run with wordfreq absent falls back to its own documented "old, weaker behaviour" — validating French de-hyphenations against /usr/share/dict/words (English) — and says nothing. §VII: a measurement carrying a known reliability caveat states it on its own output, every time. Fix: report wordfreq active/absent and the effective language on every run. (wordfreq installed into ~/.local/chamber-tools-venv 2026-08-01.)	2026-08-01 (Derrida conversion)	PROPOSED
181	/jurist-package	patch	Filing is not sending, and the skill has no step that distinguishes them. The 2026-08-01 ESCALATE doctrine package sat filed-and-unsent for a day; the executor could not determine its state from the repository and had to ask. Add a send-state line to the package footer (`filed · sent <date	not yet>`) and a §1.6-style check at wrap. Cheap, and it is the difference between a package that is waiting on the jurist and one nobody has moved.	2026-08-02, found while packaging	PROPOSED
182	/jurist-package	patch	Require the mechanical containment proof the skill's own discipline implies. The skill states quote, never paraphrase but carries no check. Built and used twice on 2026-08-02: it caught a fabricated terminal period inside a blockquote in the executor's own package (read past twice), and discharged REVIEWED-85's stated precondition where the jurist could not verify skill-file quotes itself. Tool: dotfiles/claude/governance/check_containment.py, positive controls mandatory. PROPOSAL, not FIX — this changes gate criteria, which the §1.6 hard floor reserves. Bears directly on PENDING-86 option (b), which is unruled; route with that item, not ahead of it.	2026-08-02	PROPOSED

New proposals (2026-08-02 pm wrap — the vignette build; awaiting steward)

#	Skill / instrument	Kind	One-line	Status
A	verification-ladder: render-and-LOOK outranks the check suite for any rendered output	ladder entry	Strongly earned — three instances in one session. Every substantive vignette defect was found by rendering the artifact and looking; none by the mechanical checks, which were good checks and all passed: a field colour bound to a class no element carried (Layer 3's whole mode mapping would have inherited the panel's ink and looked correct); a hand-rolled palette violating §III's sacred-palette clause, collapsing dark-mode contrast; interval clearings reading as smudges. The general shape: an instrument can certify a property of the code while the claim being made is about the result. For visual/rendered work the gate is the render, and the check suite is necessary-not-sufficient. Kin to measure-toolchain-before-spec, one level over.	PROPOSED
B	/measure-render — RE-REINFORCED (5th+ instance)	create skill	Headless-Chrome capture used again today, and this time it was decisive rather than diagnostic: the screenshots are what exposed the dark-mode contrast collapse and the interval smudges. Previously proposed 2026-06-09, reinforced 06-09 pm, 06-11. The pattern is now: build → emit → shoot → read the PNG back and look at it, which is a step a skill should carry because it is the step most easily skipped.	PROPOSED
C	Implementing a spec is a spec-audit instrument — the under-determination census	ladder entry OR skill	New method, proven today. Building Phase 1a produced nine findings about where the vignette spec fails to determine its output — none findable by reading the spec, because from inside an implementation a silence does not feel like a decision, it feels like the obvious reading. Output shape: per finding, what the spec says · what it under-determines · how the implementation silently resolved it. Deliverable committed at docs/AldineXXI-Codex/drafts/vignette-spec-under-determination-census-2026-08-02.md as the worked exemplar. Warrant is in the spec's own Part II: "if the visual result doesn't work, the spec needs revision before proceeding."	PROPOSED
D	Symmetria §3 flag: applying a doctrine where it does not govern	Symmetria §3 flag	Steward-caught today. Asked whether to send a spec to Fable, the executor reached for Constraint 6's independence framing and attached a corroboration caveat — but it was a design task, not a checking task, so independence never arose and the caveat was empty. The flag: before invoking a governing principle, name the question-type it governs and check the task is that type. A live maxim applied off-domain is the decorative failure ~/CLAUDE.md asks us to flag, and it feels like rigour from inside.	PROPOSED

Applied at this wrap under the §1.6 FIX lane (mechanical repo-CLAUDE.md freshness; classification test: changes neither executor latitude nor a governed artifact's assertion — it removes a claim the substrate contradicts; hard floor not engaged, no open item's visibility reduced): ARC CLAUDE.md asset-structure listed js/ # JavaScript (theme toggle); the directory does not exist and the toggle was retired with the JS pipeline at Stage M (2026-06-01). Replaced with a note recording the retirement. Indexed in skill-harvest-fix-lane-index.md.

Noticed, not fixed (needs steward/jurist — vignette Phase 4 scope): vignette-specification.md Part II Phase 4 prescribes moving assets/js/glyphs/ to assets/js/glyphs-archived/; that tree no longer exists, so part of the quarantine phase is already moot. And AldineXXI-specification.md §IX still says genomes are "Generated by a local model via Ollama", which the companion superseded (Part II, Engine evolution). Both recorded in the under-determination census; §IX is sealed-spec.

---

New proposals (2026-08-04 evening wrap — census 02 + the engine's first questions)

Element	Kind	One-line	Where it lands	Status
/census — the pre-registered instrument census	create	Strongly earned: two runs, ten days apart, both productive, and in BOTH the pre-registration caught a reversal the run would otherwise have banked comfortably. Method: pre-register question + unit of census + the test applied + numbered predictions with confidences + a discrimination condition (what result would mean the census discriminated nothing) + stopping rule → run entire, no sampling → grade the predictions. Census 01's lenience clause converted a pleasant miss into the real finding; census 02's condition forced the "both buckets populated" check and its prediction-5 inversion was the result. Also carries the two-axis discipline (engagement vs record) that kept "it works" and "we can tell it works" from collapsing.	new /census skill	PROPOSED
Symmetria §3 flag: the-fix-for-an-overclaim-is-an-overclaim-candidate	Symmetria §3 flag	When you repair an overclaim, the replacement inherits the frame that produced the original. Replacing the engine's "genuine silence, not a gap" with "the index is complete and current" reproduced the identical defect one size down — "complete" is true of document coverage and unverified of query-matching, and a reader without that distinction collapses the two exactly as the engine did. Caught by the jurist, not by me. Re-reading a replacement as a stranger is a separate act from writing it, and it is the act that gets skipped because the repair feels like the careful part.	Symmetria §3	PROPOSED
Widen assert-from-derivation-not-substrate with the null-result case	Symmetria §3 patch	A null from an instrument you have not positive-controlled is a fact about your instrument, not about the world. Probed resolve_archived_source with engine source_ids against the chamber's canonical_slug key space; got None three times including the nonsense control — which should have been the tell — and was one sentence from reporting a healthy 349/349 resolver dead. The existing flag covers asserting presence from a derived form; it does not name asserting absence from an un-controlled probe, which is the more seductive half because a null feels like an observation rather than a claim.	Symmetria §3 (widen the existing consolidated flag)	PROPOSED
/wake-up patch — a tracker marked THE GOVERNING FRAME is read ENTIRE, not as its pointer	patch	Earned at a measured cost of ten days. MEMORY.md carries "[Chamber as versioned releases] — THE GOVERNING FRAME for all library work. Scope every library bite through this" — and the file itself held the resolution to the paralysis the steward named at this wrap (purpose choice and corpus scope are ONE decision, not sequential), written 2026-07-28 and unopened since. The index entry cannot carry a reframe; only the file can. Proposal: where a tracker line declares itself governing, /wake-up opens the file rather than trusting the one-liner — the same logic as the telos-conditional already wired in §2.a. Kin to feedback-resurface-banked-notes-before-rederiving, one level up: not re-deriving a banked note but never opening it.	/wake-up §2.a	PROPOSED

New proposals (2026-08-05 wrap — the quoted-tier measurement; awaiting steward)

Target	Kind	Proposal	Earned by	PROPOSED?
/jurist-package	patch	Require reading the clauses ADJACENT to every quote, and stating in the package that you did. Strongly earned and jurist-caught: PENDING-99's Grounding quoted §II.3 verbatim, passed containment 16/16 with 9/9 controls absent — and omitted the sentence one line later ("What remains genuinely open… the marker's exact syntax") that dissolved the whole question. It was in the executor's own read output. A containment proof passes an omission every time, because nothing is misquoted. The limit is now written into check_containment.py's docstring; the procedural half belongs in the skill. Add to the Grounding step: quote the clause, read its neighbours, and record "adjacent clauses read" beside the containment line.	2026-08-05, jurist-caught on first substrate access	PROPOSED
verification ladder	new entry	A suspiciously UNIFORM offset is a constant masquerading as a measurement. A forward-window locator reports the window START, not the match location — so it returns the window size as an offset. Shipped twice in one session (Δ−30, then Δ−25) before the definition was fixed; the truth was Δ−1. The tell was not a failing test — no test covered it — but that the number was identical across every hit. Sibling of count-first-then-look. Rule: when an offset/delta is constant across independent items, suspect the instrument before the data.	2026-08-05, twice in one session	PROPOSED
verification ladder	new entry	Pre-register the expected effect BEFORE building the change. fidelity_equivalence@3's effect was filed in the jurist package as 3/17→6/17 before any code existed; the post-build measurement returned exactly 6/17. Had the number been computed first and reported second, a partially-correct implementation would have been indistinguishable from a correct one, because whatever it produced would have become the claim. The census pre-registration discipline, transferred from audits to code changes.	2026-08-05, applied and held	PROPOSED
/wake-up §4	patch [candidate FIX]	Do not print the Symmetria line unless Symmetria was invoked. This wake's briefing ended "Symmetria active. Practice of return foregrounded" and Symmetria was never invoked; no ledger exists for the day. The claim was output, not act — the decorative-maxim failure ~/CLAUDE.md asks be flagged, occurring inside the instrument whose job is to foreground the practice. Either invoke in the same step that prints the line, or print what is true. Classified PROPOSED not FIX: it changes what the executor must DO at wake, not only what it records, so the two-clause test routes it to the loop.	2026-08-05, self-caught at wrap	PROPOSED
governance-mcp / doc-access generally	patch	A document whose head is superseded must disclose that at the point of access. The chamber constitution's first ~330 lines are obsoleted version headers; a default limit=400 read lands entirely inside them. Granting access without disclosure would have caused the misruling the access exists to prevent. Handled here by putting the warning in the key's own description plus a negative control proving the trap is real. Generalize: any enumerated document whose operative content does not start at line 1 carries the offset in its description.	2026-08-05, caught while building PENDING-86 (a)	PROPOSED