diff --git a/PENDING.md b/PENDING.md index 248a981..3c820fe 100644 --- a/PENDING.md +++ b/PENDING.md @@ -6525,8 +6525,20 @@ Two things follow, and they point opposite ways. **The check fired correctly** since: 2026-08-02 trigger: date 2026-08-02 owner: steward + resolved: 2026-09-01 — check-in held, steward + jurist; outcome EXTENDED PROVISIONAL, recorded at claude/memory/skill-harvest-fix-lane-index.md §FIX-LANE CHECK-IN --> + + +⚠ **The re-based trigger is only HALF machine-checkable, and the unchecked half is the one the re-basing was for.** The 2026-09-01 check-in re-based the trigger from time to **use** — *next check-in at 5 executor classifications, backstop 2026-12-01, whichever first* — because the date trigger fired twice with nothing recorded and a use-count cannot be missed by being busy. **The schema's trigger vocabulary is `glob | path-exists | date | manual`; a use count is not expressible in it.** The block above therefore carries the **backstop only**, and the use-count half is recorded in `discriminator:` where a reader will find it. + +**No proxy was invented, deliberately.** The schema's own comment says `manual` exists so a deferral whose condition cannot be mechanised is *listed rather than checked*, "instead of inventing a proxy — proxies are what failed here." A `glob` over the index's table rows would have fired on any row, including the ruled and steward-instructed ones, and would have looked machine-checked while counting the wrong thing. **⇒ Until the schema can express a count, this deferral's primary condition is honoured by a human reading the index.** That is the state, stated, rather than the appearance of coverage. + The block is filed with a trigger date **already in the past**, deliberately, so the drift-check reports it **DUE on the next run** rather than quietly waiting. Agenda is already written and needs nothing from the executor: `skill-harvest-fix-lane-index.md` §*Check-in agenda* carries both items, the second folded in by REVIEWED-86 Q4 (*the record is not just written, it is read*). **Consequence adopted for this session, before the finding was convenient.** Today's one harvest candidate — the `daybook-ensure.py` SKELETON missing the `## ` heading `/wrap-up` §7.5 specifies — is filed as a **[PROPOSAL] in the skill-harvest register, not applied through the lane**, on the lane's own suspension rule. It would otherwise have been a clean FIX with an exact 2026-08-24 precedent. diff --git a/claude/memory/skill-harvest-fix-lane-index.md b/claude/memory/skill-harvest-fix-lane-index.md index d529a8e..0859c38 100644 --- a/claude/memory/skill-harvest-fix-lane-index.md +++ b/claude/memory/skill-harvest-fix-lane-index.md @@ -43,3 +43,17 @@ cannot authorize its own construction. - 2026-08-02 · ARC `CLAUDE.md` · removed `js/ # JavaScript (theme toggle)` from the asset-structure tree — directory absent, toggle retired Stage M 2026-06-01; replaced with a retirement note. Mechanical freshness; no latitude or assertion change. - `/wrap-up` §8 — added standing **Instruments** field (N run · M with a control written before first execution · K duplicating something already banked). Converts the 2026-08-07 one-off literal question into a series, and turns the steward's "do we need so many single-use items?" into a measured K column rather than a standing worry. — 2026-08-08 - 2026-08-24 · `/wrap-up` §7.5 + `daybook-ensure.py` SKELETON · added a standing `## Corrections` section to the daily-note format, with the rule that an empty Corrections on a working day is itself a claim · **applied on direct steward instruction, reasoning from the jurist (REVIEWED-126)** — recorded here rather than in the lane proper, since it was authorized rather than executor-classified. Changes what the note *records*, not what any party may do. + +## FIX-LANE CHECK-IN — REVIEWED-85 provisional review, 30 days overdue +**Date:** 2026-09-01 · **Parties:** steward + jurist · **Discharges:** REVIEWED-85's provisional condition; the `DEFERRED-DECISION: fix-lane-provisional-checkin` block filed at PENDING-168 ADDENDUM 1. + +**Item 1 — the lane.** EXTENDED PROVISIONAL, not settled and not withdrawn. The lane has been exercised by the executor exactly once in thirty days (the 2026-08-08 `Instruments` field); batch 1 was ruled by REVIEWED-85, the Corrections entry was steward-instructed, the ARC entry is mechanical freshness. **n=1 is not evidence either way.** +- The 2026-08-08 entry is **RATIFIED on the merits as class (i)**, and its procedure is recorded as **defective**: it was executor-classified under a lapsed authorization, against the lane's own instruction to treat borderline calls as PROPOSAL until review. **Not precedent.** +- **The trigger is re-based from time to use:** next check-in at **5 executor classifications**, backstop **2026-12-01**, whichever first. The original date trigger fired twice with nothing recorded; a use-count trigger cannot be missed by being busy. Filed as a `DEFERRED-DECISION` block in the same act. ⚠ **The use-count half is not expressible in the current schema and carries no machine check** — see the note beside the block in `PENDING.md`. No proxy was invented. +- **Boundary flagged, not reopened:** batch-1 #4 changed the standing wrap question, which is what the executor must **inquire into**, not what a skill **records**. It was ruled class (i) by REVIEWED-85 and stands. It marks where class (i) ends, and the next hard classification should be measured against it rather than against #1–#3. + +**Item 2 — the retrieval obligation (REVIEWED-86 Q4).** **NOT DISCHARGED.** Answered with two fresh instances rather than a confirmation: REVIEWED-67's Q4 census and its unconditioned per-conversion typography gate did not reach the PDF lane in 42 days, and PENDING-177 AMENDMENT 1 records it as the identical PENDING-56 failure in a second format class. The cost is measured — `verify_conversion` returning **5/5 PASS on word-damaged output**. +- **The machinery is not missing; the question is.** Batch-1 #2 and #3 built `prevention` and put it in the wake for this purpose. What has no surface is the **class-level question at the point of adoption**: *what standing rule already governs the class I am about to route?* +- Directed to the wrap/wake surface, deliberately **not** as a new instrument and **not** as a new item. It is one question in an existing skill. ⚠ **Placement is unresolved and is flagged rather than guessed** — see the executor note below. + +**⚠ EXECUTOR NOTE — item 2's natural home is frozen.** "What standing rule already governs this class?" is a verification-ladder entry by shape, and the ladder is under a **general freeze** (REVIEWED-123, 2026-08-17: no additions, rewordings, removals or reorderings from any source until the trial is graded). Placing it in `/wrap-up` or `/wake-up` instead is available but fires at the wrong moment — the failure it addresses happens **at adoption**, not at wake or wrap. **Not placed. Awaiting direction on where it goes.** Recording the mismatch rather than putting it somewhere it will be decorative.