Skip to content

[finding] Clause-②: yes on a non-spec, non-skills lane — the protocol says the contract-review-tier review is the spec seat's, but spells no handoff (who is asked, by which artefact), so a lane seat reaches for an in-seat PASS the harness classifier then refuses as self-approval #18349

Description

@os-zhuang

Filed by the domain:skills execution PM seat, session session_01HZfg2AwVX191qCizp88gQr, at 2026-09-16T01:59Z, from the objectui PM seat's report to the maintainer on objectui PR #9578 (a Clause-②: yes card, CI green, needs:contract-review on both carriers): that seat wrote a same-shape ## Contract review … VERDICT: PASS at the default tier and the harness auto-mode classifier refused the write as [Self-Approval] (control: a card create and an ACCEPT on the same channel succeeded seconds later). The seat did not route around it and holds the PR in the safe state.

What the protocol already says (读数,origin/main 500c1b56)

The gap

Nothing in SKILL.md, contract-review.md or lanes/spec.md spells HOW a lane seat hands a Clause-②: yes PR to the spec seat for its review: which seat post is addressed (the board's own spec seat — objectui has one — or objectstack#6017), by which artefact (a comment on the PR? a card on the spec lane's queue? the needs:contract-review label alone?), what the spec seat writes back (a same-shape record on the PR with Reviewed-by: = the spec seat's session), and who then clears the two carriers and enqueues (the dispatching seat, per :38–:39). A seat that cannot find the handoff reaches for the in-seat PASS, and the classifier's [Self-Approval] reading lands on exactly that act. The classifier reading itself belongs on platform-readings.md as a harness fact (comment writes are refused by CONTENT — a PASS verdict on a PR the same session dispatched — not by endpoint).

What is asked (⛔ not asserted — the seat grades)

(1) One or two lines in SKILL.md / contract-review.md naming the handoff for Clause-②: yes outside spec / skills: the artefact, the addressee (the same board's spec seat when it exists, else objectstack#6017), the record shape the spec seat posts, and that the dispatching seat keeps landing duty; (2) one platform-readings.md row for the classifier reading, with the objectui measurement (refused PASS, accepted ACCEPT + card create); (3) ⛔ no change to the SELF-REVIEW machine reading — a subagent dev's Implemented-by: stays the branch. Rules layer (four-piece + an authorized APPROVED) for (1); references tier for (2). Budget: SKILL.md 812 / 812 — an in-place re-key of :513 or :523 may carry (1) without a new line.

Grading (lane finding self-triage; class (b)-shaped — a declared rule with no executable handoff): p3 · Task · pm:queue · domain:skills — not p2: the safe state holds (draft, both carriers, no enqueue), and the maintainer is choosing A / B / C on the live case.

查重词

Clause-② yes spec seat handoff · contract review self-approval classifier · needs:contract-review non-spec lane · spec seat review request artefact · in-seat PASS refused


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions