governance: steward places REVIEWED-85 (PENDING-88 skill-harvest FIX lane, design gate passed with conditions)

Placed by the steward 2026-08-01. Verified byte-identical to the jurist's supplied block,
parses as a real header at line 886, correct position after REVIEWED-84. Committed by the
executor to get it off one disk — preservation, not modification (Constraint 1).

PENDING-88 correctly remains open: the ruling is a design-gate PASS with conditions and
the §1.6 landing has not happened.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc

REVIEWED.md

@@ -881,4 +881,19 @@ brief. No work is blocked meanwhile; `wake-digest.py --brief` remains the fallba
 - **V-DPDF disposition (resolves REVIEWED-83's practical blocker):** order-blindness is not a V-DPDF-specific gap needing a new precondition — it is the pre-existing, tier-general stamp-block V-TEXT already operates under (REVIEWED-74). V-DPDF inherits it identically: promotions may proceed to `converted`; the `verified` stamp withholds on the order axis exactly as it already does elsewhere, discharged for Harrison by the eyeball-after-gate acceptance above, not by a new mechanism.
 - **Process note (not ruled):** a keyword-search gap over PENDING/REVIEWED contributed to the Q3 error as much as executor self-containment did. Fold into PENDING-86's options rather than opening a new item.
 **If AUTHORIZED:** Land the MINOR supersession adding Part V(A)'s requirement text beside blocking condition (a); record the explicit eyeball-after-gate acceptance for the order axis pending a ratified mechanism; release Harrison's `verified` stamp once that eyeball pass is done; V-DPDF's REVIEWED-83 status otherwise unchanged (Q1, Q2, Q4, Q5 of that ruling stand). Tag commits REVIEWED-84.
-**Awaiting:** steward placement; steward eyeball pass on the one flagged book; steward pacing call on whether `order_attestation:` gets built now or banked.
+**Awaiting:** steward placement; steward eyeball pass on the one flagged book; steward pacing call on whether `order_attestation:` gets built now or banked.
+
+## REVIEWED-85 — PENDING-88 — Skill-harvest FIX lane: hard floor sharpened, dual instrument required, provisional pending check-in (design-gate passed with required conditions)
+**Date:** 2026-08-01
+**Decision:** AUTHORIZED — proceed per the ruling, provisionally. Register split (option (d)) unaffected — separately authorized 2026-07-19, correctly executed by the split method rather than the inapplicable collapse method; no action needed here.
+**Notes:**
+- **Verification limit, stated up front.** All Part I quotes sourced from `~/CLAUDE.md` (taxonomy, escalate list, governance-contract clause, Constraints 1/5/6, PENDING-1 closing note) independently confirmed exact against the live file. The two `/wrap-up` §1.6 passages and the `/wake-up` §2.a line — the textual basis for Part III's "contradicts itself" claim — could NOT be independently checked; skill files are outside current tool reach. Required before landing: the same mechanical containment-with-positive-control verification the 2026-07-29 package carried, applied to these quotes specifically.
+- **Q1 — gap, not deliberate distinction — AFFIRMED** on the timeline evidence given, unverified directly. The alternative reading is answered by the hard floor's exclusions, not by retaining the blanket rule.
+- **Q2 — two-clause disjunctive test — AFFIRMED, and the narrower single-clause alternative is declined.** A latitude-expanding-but-non-assertive change would pass an assertion-only test; keep both clauses.
+- **Q3 — report + provenance comment BOTH mandatory, and a third instrument added.** A wrap-narrative report alone is insufficient by the package's own admission. Required: (i) wrap report, (ii) skill-source provenance comment, (iii) a running append-only FIX-lane index (one line per applied change: skill · what changed · date), built on the same live-index pattern used for today's register split.
+- **Q4 — the floor's catch-all clause sharpened.** "Anything that would reduce what is surfaced to the steward" becomes: *any change that removes, defers, or narrows the visibility of an open item, or that could cause a future item to land somewhere the steward's surfacing tools don't read, stays PROPOSAL regardless of the test's outcome.* Tied to the actual failure measured in Part II, not left as an unbounded judgment call.
+- **Q5 — jurist review applies, narrowly grounded.** Not the stretched PENDING-S2 analogy (correctly declined by the executor itself) — grounded in this touching the integrity of the surfacing mechanism the steward and jurist both depend on, which is the PENDING-1 class of question by its function, not by resemblance.
+- **New condition — bounded check-in, not asked for in the package.** After the first FIX-lane batch or one month, whichever comes first, steward and jurist review the FIX-lane index together before the lane is treated as settled rather than provisional. Per Constitutional Constraint's own decision heuristic (prefer reversible choices) — costs nothing if the classification holds.
+- **Hard floor otherwise as proposed — AFFIRMED:** Constraint 1 (CLAUDE.md/REVIEWED.md/L2), authorization-boundary or gate-criteria changes, the escalate-unconditionally list, all untouched and all remain PROPOSAL/ESCALATE regardless of the test's answer.
+**If AUTHORIZED:** Land the §1.6 edit (classification test + sharpened floor + dual-plus-index instrument) with a provenance comment in `/wrap-up` SKILL.md; no change to `~/CLAUDE.md`. Apply to today's four proposals (ledger section, KG predicate, wake line, reframed question) as the first FIX-lane batch, feeding the check-in review. Tag commits REVIEWED-85.
+**Awaiting:** steward placement; mechanical verification of the §1.6/§2.a quotes; the bounded check-in once the first batch or one month has passed.