Skip to content

pm-dispatch(decision-analysis): the four-axis analysis of a decision card is written or re-read at the ceiling tier (fable) when available before the card is filed; otherwise filed at the seat tier with an Analysis-tier: line #27265

Closed

Description

@objectstack-fleet

Filing gate ③ (maintainer-directed). Filed by domain:skills seat 2 · os-justin · session_01QSeKYmhU5KEj1nukYhp1Tg on the maintainer's word in the seat's session, 2026-10-28 ~13:2xZ. ⛔ Not a claim.

The maintainer's words (verbatim, in order)

  1. 「立决策卡时,如果有fable,是否建议先用 fable 审核之后再立?」
  2. On the seat's recommendation (yes — for the four-axis analysis only, "use when available", not a new gate; one line of guidance; an Analysis-tier: line when the ceiling tier is not available): 「同意」

Why

A decision card is the human floor: the maintainer reads the seat's four-axis analysis and recommendation and rules on it. That text is the highest-judgment artefact the loop produces — a wrong frame either misleads the ruling or comes back for a rewrite. Mechanical cards do not earn the ceiling tier; decision cards do. This is consistent with the standing ruling of 2026-10-28 「同意,维持面强制,不全上 fable」: the file surface sets the MANDATORY tier, a decision card is not a surface, so this is per-card guidance, not a surface mandate.

A mechanical benefit measured this shift: the claim-line checker in scripts/pm/post-stamped.mjs refuses a model: fable value on a surface with no MANDATORY hit unless the line cites a reason: naming a ruling (the seat's claim on #27113 was refused on exactly this, 2026-10-28 12:4xZ). This card, once landed, is the citable standing ruling for the decision-card case.

Wanted

One line of guidance, no gate, no recogniser:

  • 「决策卡的四维分析与推荐,可用则在 ceiling 档(fable)写成或复核一遍再落卡;不可用按席位档落卡,正文加 Analysis-tier: 一行注明。」
  • Home: .claude/skills/pm-dispatch/references/decision-analysis.md 〈落卡分析模板〉 (49 lines on origin/main; the implementer reads its ceiling row in scripts/pm/check-skill-line-ratchet.mjs and edits in place or pays the line). ⛔ Not SKILL.md unless a line there can be paid — SKILL.md is at its ceiling (319) and holds the in-flight pm-dispatch(p0): a lane's p0 card is dispatched at once — no batch, depth-wait or concurrency cap holds it, and lower-priority dev work pauses to make room; main or merge-queue red is graded p0 at first touch #27047 edit; if the implementer judges SKILL.md 〈升级与决策〉 the only honest home, say so in the PR body with the line arithmetic.
  • The Analysis-tier: line is a plain body line a human reads; ⛔ no checker, no half-state row (SKILL.md: a new gate is a no by default; the maintainer named none).
  • Clause-②: no · Metadata-protocol: none. Tier S (.claude/**).

Acceptance

  • A seat filing a decision card reads, in the template it copies from, that the four-axis block is written or re-read at the ceiling tier when available, and what to write when it is not.
  • check:pm-skill-ratchet and check:pm-skill-id-lint green.

Serial

decision-analysis.md is in no open PR and in no in-flight claim's file surface (seat 2's hot-file queue, r72); no ordering owed. If the home becomes SKILL.md, it queues behind #27047.

Dedupe: open and closed domain:skills issues updated since 2026-10-20, read for Analysis-tier, 决策卡+fable, "decision card"+"tier"+"fable": 0 open hits; 4 closed hits all unrelated (#26369 Skills-docs line, #25344 adjudication channels, #25219 coordinator reference, #25216 needs_decision fork). New.


Generated by Claude Code

Activity

  1. added
    toolingFix lands in tooling, not a product package — enters pm:queue only with Unblocks: or a named surface
    pm:queueReady for the PM dispatch loop
    domain:skillsDomain lane — seat card indexed by label:pm:seat
    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterate
    pm:retriageQuestion for triage, answered each fire; coexists with the standing pm:* label; no dispatch
    on Oct 28, 2026
  2. objectstack-fleet commented on Oct 30, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:skills#2 · os-elon-musk · session_016WV4d1QkPVVzNz3FJqb2iS

    ⛔ Not a claim. pm:queue with no triage audit comment, so not a candidate for an execution seat (pm-dispatch execution-duties.md: 无分诊审计评论即非候选). pm:retriage asks the triage seat for the audit (grade, lane, Path:, tier).

  3. objectstack-fleet commented on Oct 30, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

    Path: none

    Triage: p2 · domain:skills · area:devpath · audit (retriage) · 2026-10-30T01:57Z

    ⛔ Not a claim. This audit comment was owed since filing. Triage's sweep skipped the card because it already carried pm:queue, and that is triage's miss.

    • Read fresh. A maintainer-directed one-line guidance (「同意」): use the ceiling tier for the decision-card analysis when it is available, and add an Analysis-tier: line otherwise. No gate and no recogniser.
    • The home is decision-analysis.md, within its line ratchet. Tier H.
    • pm:retriage removed.

    Generated by Claude Code

  4. removed
    pm:retriageQuestion for triage, answered each fire; coexists with the standing pm:* label; no dispatch
    on Oct 30, 2026
  5. objectstack-fleet commented on Oct 30, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:skills#2 · os-elon-musk · session_016WV4d1QkPVVzNz3FJqb2iS

    Claim: PM loop round 1 · 2026-10-30T04:26Z
    Session: session_016WV4cwL4FAJsMLvKcqSyo9 (card thread; seat session_016WV4d1QkPVVzNz3FJqb2iS)
    Account: os-elon-musk
    Branch: claude/project-thread-8p8o5x (the card thread's platform-assigned branch — the recorded platform exception; amended by the seat when the thread reported it)
    Worktree: objectstack-issue-27265
    Domain: domain:skills
    Seat: domain:skills#2 (seat 1 vacant on #7623; p2 rung, oldest first)
    File surface: .claude/skills/pm-dispatch/references/decision-analysis.md (one line of guidance, within its line ratchet, paid in the same file) — stop on breach; explain in the report
    Container & model: S, mode:thread, model: opus — dispatch-gates --tier: no path-derived mandate; effort: medium; governed rules text (.claude/**) owes a CONTRACT_REVIEW_TIER review (fable) before the queue
    Clause-②: no
    Metadata-protocol: none
    Responsibility: the maintainer agreed (「同意」, 2026-10-28) that a decision card's four-axis analysis is written or re-read at the ceiling tier when it is available, with an Analysis-tier: line otherwise; the rule text does not say so, so seats file decision analyses at whatever tier they run and a model: fable claim line on a non-mandated surface has no ruling to cite.
    Thread-read: 6513060884
    Premise: holds (origin/main f8633c7c2: decision-analysis.md is 49 lines and names no analysis tier)
    Serial constraints cleared: no open PR touches decision-analysis.md at claim time. Landing tier is read off the register at PR time (check-governed-merges.mjs --pr N); root .claude/** reads Tier S. ⛔ No gate, no recogniser (card).

  6. added
    pm:dispatchedDispatched to a dev agent by /pm-dispatch
    and removed
    pm:queueReady for the PM dispatch loop
    on Oct 30, 2026
  7. objectstack-fleet commented on Oct 30, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:skills#2 · os-elon-musk · session_016WV4d1QkPVVzNz3FJqb2iS

    ACCEPT → PR #27942 (register Tier S, .claude/**; contract review PASS 6515267777 on head 194b3ea; CI green). The seat flipped it ready and armed auto-merge.

  8. objectstack-fleet commented on Oct 30, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:skills#2 · os-elon-musk · session_016WV4d1QkPVVzNz3FJqb2iS

    Landed: PR #27942 merged (9900366eb, 2026-10-30T05:37Z) as Tier S (the register's claude-tree row) on contract review PASS 6515267777; pm:dispatched stripped with this note. From this commit decision-analysis.md says a decision card's four-axis analysis and recommendation are written or re-read at the ceiling tier when it is available, and otherwise filed at the seat's tier with an Analysis-tier: line. Nothing further owed on this card.

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

Metadata

Metadata

Assignees

Labels

area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratedomain:skillsDomain lane — seat card indexed by label:pm:seatpriority:p2Medium: important, M3toolingFix lands in tooling, not a product package — enters pm:queue only with Unblocks: or a named surface

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions