session 2026-07-09 evening: skill-harvest — cross-repo re-anchor ladder entry + CLAUDE.md:67 note + /normalize-epub watch
This commit is contained in:
@@ -387,3 +387,8 @@ The single place proposed skills live so they don't evaporate between sessions.
|
||||
- **PROPOSE — Symmetria §3 flag / feedback: `provenance-is-part-of-the-process, not a loose end`.** I framed source-attestation + archiving as "loose ends / deferrable"; the steward: *"they should never be considered loose ends, they are part of the process."* Executor bias: treat the visible artifact as done, provenance (attestation, archiving, cataloguing) as afterthought. **Text:** *attestation, source-archiving, cataloguing are constitutive steps, not the tail; the feeling that "the artifact is done" hides the provenance the next hand needs.* Kin to `completion-is-a-tripwire`. **PROPOSED.**
|
||||
- **`/graduate-chamber-source` — REINFORCED (the born-digital/EPUB branch, full pipeline incl. archive+attest+catalogue).** The Handke run is the born-digital branch (distinct from Levi-OCR + Olson-V-SCAN): identity-verify → pandoc + structure pass → gates → archive via `archive_sources.py --add` + steward `source_verified` + catalogue. The skill, when built, must carry the branch-selection heuristic AND make archive+attest+catalogue non-skippable (the whole "loose end" failure this session). **PROPOSED (reinforced; build-on-need — another strong nudge it's ripe).**
|
||||
- **PROPOSE — verification-ladder entry: `a red gate deserves the same scrutiny as a green one`.** verify_conversion's `heading_density` FAILED the Handke (a genuinely continuous work). Before trusting OR overriding, I read the gate's own §VII sectionless exception + how the English sibling passes → the honest fix (title-as-`#` heading matching the sibling; NOT invented chapters, NOT a bare `sectionless:true` flag). **Rule:** a gate FAILURE is a candidate, not a verdict — verify true-defect vs heuristic-false-positive (read the gate's own escape conditions + a passing sibling) before either trusting or overriding it. The green-gate-blindness lesson's mirror. Home: `reference-verification-ladder.md`. **PROPOSED.**
|
||||
|
||||
### Harvest 2026-07-09 evening (P1 clean + the cross-repo re-anchor miss + the EPUB-normalizer pivot)
|
||||
- **PROPOSE — verification-ladder entry: `re-anchor spans BOTH repos`.** When a chamber canonical is re-hashed (source-clean OR reconvert), the sha-binding surface is NOT chamber-internal only: studium-engine binds via `corpus/manifest.yaml` sha + `sidecars/*.source_sha256` + `coverage-ledger.json`, enforced by `ingest_gate §1.1`. **Discipline:** grep BOTH `chamber-library` + `studium-engine` for the OLD sha (zero occurrences = completeness gate); regenerate the engine ledger via `ingest_gate` (never hand-edit the derived ledger); the engine gate re-VALIDATING is the proof. Born 2026-07-09 (P1 re-anchored chamber only; engine's 4 bindings missed, caught by luck during P2). **Already landed operationally** in `conversion-runbook.yaml` `reanchor:`; the ladder is the cross-workstream home. Kin to `trust-prior-pass-frame` (cross-repo variant). Home: `reference-verification-ladder.md`. **PROPOSED.**
|
||||
- **PROPOSE (surface, not auto-apply) — chamber `CLAUDE.md:67` discipline note.** The load-bearing line *"Clean at the SOURCE layer … (new hash, re-anchor)"* under-specifies what "re-anchor" covers — the exact under-specification that produced the miss. Add a cross-repo pointer to the runbook `reanchor:` block. This is a **discipline change** → surface for steward review per the CLAUDE.md-freshness rule (not a mechanical fleet/term update). Pairs with PENDING-53 (which completes the *governed graduation-spec* side). **PROPOSED.**
|
||||
- *Watch-list (not yet a skill): `/normalize-epub`* — a structural, verbatim-guarded EPUB normalizer keyed on the bidirectional href↔id mirror predicate (this session's pivot). Premature — the tool doesn't exist yet; the pulling thread is to prototype-then-build it. If it proves out, it earns a skill that carries the detector→converter→verbatim-guard sequence. **NOT YET PROPOSED (build first).**
|
||||
|
||||
Reference in New Issue
Block a user