Repository navigation
pm-dispatch SKILL: require a four-lens analysis block on every needs-user-decision card #7498
Description
Maintainer accepted 2026-08-11: decision cards reach the maintainer pre-analyzed on four fixed lenses, so rulings do not depend on a seat back-filling the analysis later.
The change (SKILL edit, by PR, mind the line ratchet): the step-0 / step-8 guidance for needs-user-decision gains a required short block — one line per lens:
- Platform long-term coherence — does each option shrink or grow special cases / contract accretion?
- Measured business pull — who hits this today; zero-pull options default to defer/remove.
- AI-agent error-resistance — which option is hardest for an AI author/consumer to misuse (closed enums over structured reads, loud refusal over silent tolerance, no fabricated success)?
- Startup scope discipline — prefer remove over declare-and-maintain; every declared key is a permanent obligation.
Evidence this pays for itself: the 2026-08-11 four-lens re-review of the standing decision ledger reversed 4 of ~30 recommendations that a urgency-times-leverage framing had gotten wrong (recorded on #7485, #7243, objectui#4165, objectui#3804).
Filed by the triage seat Routine (#5474 pilot) recording a maintainer ruling of 2026-08-11. Unassigned — recording, not claiming.
Generated by Claude Code
Activity
claude commentedon Aug 11, 2026
Maintainer ruling — 2026-08-11 (second ruling, scope extension). The maintainer asked whether depended-upon cards should carry a high-priority label; the accepted answer is no blanket label — encode the ordering at the read side instead, and fold the mechanism into THIS card's SKILL amendment:
pm:queuecandidates, a card named by any open card'sBlocked-by:line sorts ahead in batch selection. Computed at selection time from the greppableBlocked-by:lines — the same mechanism the unlock sweep already runs on every close; derived-at-read, so it cannot go stale. ⛔ No stored label.priority:*/pm:unblockslabel on depended-upon cards — rejected because "depended-upon" is a derived, decaying property (the exact gradient-rot shape thetarget:v17ruling refused), a label nothing reads is banned by the state model, and the release-critical chains are already covered by the existingtarget:v17contract-first propagation rule. Revisit thepm:unblocksvariant only if the depended-upon population grows well past today's ~6 cards.Recorded by the triage seat Routine (#5474 pilot) on the maintainer's direct instruction — ruling record, not a claim.
Generated by Claude Code
huangyiirene commentedon Aug 11, 2026
Claim: PM loop round 1 (devx seat, 2026-08-11 term)
Session:
session_01GZKbx4xyF7U5WXj6ch49BMBranch:
claude/issue-7498-decision-four-lensWorktree: cloud session, own clone (worktree rule satisfied by construction)
Domain:
domain:devxFile surface:
.claude/skills/pm-dispatch/SKILL.md+.claude/skills/pm-dispatch/references/**(stop on breach; explain in the report)Container & model: M,
mode:cloud,model: claude-fable-5— mandatory tier for any card editing.claude/skills/pm-dispatch/**; no Size/model suggestion line on the triage comments, tier is this seat's read.Serial constraints cleared: SKILL.md has no in-flight claim (predecessor's #5925/#6644/#7341 chains all MERGED, cards closed; #7492/#7493 sit in
needs-user-decision, not in flight). This wave's #7488+#7440 dispatch is scope-barred from.claude/skills/**(direction 1, scripts-only) precisely to keep this batch file-disjoint.Scope note: this card now carries TWO maintainer rulings — the four-lens block (body, 2026-08-11) and the scope extension (comment, 2026-08-11 03:11Z: step-3 Blocked-by ordering rule, round-brief decision-box flag, declined-option record). Both land in one PR. Line-ratchet headroom measured at claim time: 3027 lines vs ceiling 3050.
Generated by Claude Code
huangyiirene commentedon Aug 11, 2026
{ "issue": 7498, "status": "done", "branch": "claude/issue-7498-decision-four-lens", "pr": "https://github.com/objectstack-ai/objectstack/pull/7552", "premise_still_valid": true, "summary": "Both 2026-08-11 rulings land in one PR within the card's file surface (SKILL.md + references/** only). Ruling 1: step 8 gains the required four-lens block (one line per lens, required at step-0 filing and step-8 escalation; step 0's Maintainer-confirm classification and the step-5 dispatch clause template updated to match). The merge keeps ONE frame: the four lenses are defined as the card-face serialization of the existing three-axis frame (lens2↔axis1, lens1↔axis2, lens3↔axis3, lens4 promotes axis1's embedded startup-focus principle to its own required line), because renumbering the frame itself 3→4 is a four-copy edit gated by check:skill-frame-sync whose other three copies (os-dev.md, the published skills/ mirror twice) plus AXIS_MAP in scripts/ all sit outside this card's file surface — see open_questions. Ruling 2: step-3 selection now sorts pm:queue candidates named by any open card's Blocked-by: line ahead of plain queue items (computed at selection time from the greppable lines, no stored label); step-9's decision-inbox metric requires the triage brief to flag decision cards with open downstream dependents (first instance #7496 ← objectui#4190); the declined blanket priority:*/pm:unblocks option is recorded in the step-3 no-new-labels paragraph with its revisit condition. Line ratchet paid by extracting four step-8 narratives verbatim to references/incidents.md (append-only): 3027 → 3043 lines, ceiling 3050. All dispatch-prompt premises verified against origin/main before editing (frame at line 2834 ✓, 3027 lines ✓, 解锁扇出优先 section exists ✓). Diff verified orthogonal to open decision cards #7492 (Operational note 1) and #7493 (发版板 section) — neither section touched. skip-changeset applied to PR #7552; label list at write time was empty (PR seconds old), union written; PM should see [skip-changeset] plus whatever the bots add.", "tests": "pnpm check:pm-skill-ratchet → '✓ SKILL.md is 3043 lines (ceiling 3050; headroom 7)', self-test 5 cases pass. pnpm check:skill-frame-sync → '✓ 4 copies of the decision frame are structurally isomorphic across 3 files; 3 axes: business-need → long-term-soundness → ai-authoring-safety; binding sentence present in all 4; 4 count mention(s) agree', self-test 12 cases pass. pnpm check:doc-authoring → '✓ 375 files clean'. pnpm --filter @objectstack/lint run check:doc-formula-expressions → '✓ 22 record-scoped formula example(s) across 390 files / 1406 TS blocks judged clean' (green after building the dependency closure per fresh-worktree rule). pnpm check:nul-bytes → 'OK (scanned 7000 text file(s))'. No package code touched (markdown-only in .claude/), so no package test suites apply. CI status at report time: in_progress (report delivered at draft-PR time per #6644 L2).", "open_questions": [ { "question": "Should the escalation frame itself be renumbered from three axes to four across all four gate-synced copies (internal SKILL.md, os-dev.md, the published skills/objectstack-pm-dispatch/SKILL.md twice) plus AXIS_MAP in scripts/check-skill-frame-sync.mjs — or does the four-lens card-face block over the unchanged three-axis frame (this PR's shape) suffice?", "options": ["A. Keep this PR's shape: one frame, three gate-anchored axes, four-lens block as its card-face serialization — no cross-file churn, published mirror untouched", "B. File a follow-up card with a wider surface (os-dev.md + skills/** + scripts/**) to renumber the frame to four axes everywhere, splitting startup-focus out of the business-need axis in all four copies"], "recommendation": "A now, B only if the maintainer wants third-party consumers of the published skill to inherit the fourth lens as a structural axis — B is a mechanical follow-up and this PR loses nothing by landing first; doing B inside this card would have breached the file surface, which the dispatch marks stop-on-breach." }, { "question": "Tier placement of the new Blocked-by-named rule in the step-3 selection priority: the ruling says named cards 'sort ahead in batch selection' without fixing their rank against the existing 扇出 ≥ 2 and target: board tiers.", "options": ["A. p0 > 扇出≥2 > target: > named(扇出≥1) > plain queue (implemented — preserves both standing ruling-backed tiers, named beats plain)", "B. p0 > named(any 扇出≥1) > target: > plain queue (collapses the ≥2 tier into the new rule)"], "recommendation": "A, because the 扇出 ≥ 2 tier and the target:-board tier each carry their own maintainer ruling and the 03:11Z text only mandates ordering against ordinary candidates; collapsing tiers would silently re-rank target: board items below single-dependent cards without a ruling saying so." } ], "out_of_scope_findings": [] }Generated by Claude Code
Generated by Claude Code
huangyiirene commentedon Aug 11, 2026
ACCEPT — PR #7552 (all gate jobs green: ESLint, TypeScript Type Check,
check:pm-skill-ratchet3043/3050,check:skill-frame-sync4 copies isomorphic). Terminal state: awaiting a human merge — per the maintainer's 2026-08-11 ruling (「所有 skills 的更新和 adr 类似,需要人工审核」, recorded on #6023 and #7548), this seat flips the PR ready but does ⛔ not queue it and does ⛔ not arm auto-merge.Review record: changed files are exactly the claimed surface (SKILL.md +50/−34, references/incidents.md +43). Both rulings land as specified: the four-lens block is merged INTO the existing three-axis frame as its card-face serialization (one frame — the diff's own wording rules out a second parallel frame), required at step-0 filing and step-8 escalation; the step-3 Blocked-by-named tier, the step-9 brief flag, and the declined-option record are all present with the ruling dates and #7498 cited. The ratchet was paid by verbatim extraction of four narratives to references/incidents.md — checked: the moved text is verbatim, each extraction point leaves a pointer, and the diff stays orthogonal to the pending #7492/#7493 decision sections (neither touched).
Answering the report's two open questions (PM-level, recorded here so the merge isn't blocked on them):
target:→ named ≥1 → plain). Correct reasoning: the ≥2 andtarget:tiers each carry their own maintainer ruling; the 03:11Z text only mandates sorting ahead of ordinary candidates.@maintainer: this PR is ready for your review and manual merge.
Generated by Claude Code
huangyiirene commentedon Aug 11, 2026
Label transferred to the skills seat (#7623):
domain:devx→domain:skills, on the maintainer's direct chat instruction to the devx seat, 2026-08-11, verbatim: 「所有现有 skills 相关卡片转到 新的项目经理」. 改标不改辖 (label follows classification, custody stays — the #6367 migration precedent): this card is in flight, its PR #7552 is ACCEPTed and awaiting the maintainer's manual merge, and closure/verification remain with the devx seat's session (session_01GZKbx4xyF7U5WXj6ch49BM).Generated by Claude Code
os-help commentedon Aug 11, 2026
Folded into the consolidated skills batch #7631 on the maintainer's direct instruction (专题讨论, skills seat session
session_01ATJiqhFNL82YwV8udPkoqX, 2026-08-11; verbatim: 「关闭 #7552,内容并入批次」+「包括 7498」).claude/issue-7498-decision-four-lens(head24934cf8b) is the reference implementation the batch dev reuses.pm:dispatched→pm:queue, assignee cleared — this card is now a member of batch [batch] pm-dispatch SKILL consolidated amendments + compression — eight ruled cards, two serialized PRs (skills seat, round 1) #7631 (member candidacy suspended per sweep rule; closes via the batch PR'sFixes #7498).session_01GZKbx4xyF7U5WXj6ch49BM, via PR pm-dispatch SKILL: require a four-lens block on every needs-user-decision card, Blocked-by-aware batch selection, round-brief decision flags #7552) ends with its PR; thanks on the record — the work is carried forward, not discarded.Generated by Claude Code
pm-dispatch SKILL batch: eight ruled amendments — four-lens block, AD…