Skip to content

[Epic] Product areas and grading rollout: rule text, area labels, backfill, regrade #35205

Open
7 of 26 issues completed

Description

@objectstack-fleet

repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

Filing gate: the maintainer's word in the objectstack priorities discussion, 2026-11-18, verbatim: 「立一张专题卡,开始执行」 (14:43Z), after 「同意,然后立一张专题卡处理相关任务?」 (14:33Z) and 「同意」 to the four review changes (14:42Z). Executor: objectstack seat 1, named by the maintainer. It runs in parallel with #35159. The children are rule PRs and label work, not product development, so they take no #35159 dev slot.

What this is

The objectstack backlog moves to six standing product areas, with one area:* label per card, a GitHub issue type per card (Bug / Feature / Task), and a lookup-table grading rule. This epic carries the rule text, the labels, the backfill of the open cards, the regrade, and the clean-up.

Final structure (as agreed)

  • Six product areas, one label each:
    • area:ai (AI)
    • area:build (building apps)
    • area:data (data and permissions, including sign-in, organizations, audit, search and query performance)
    • area:workflow (flows and integration)
    • area:ux (experience, including i18n, mobile, the shell and navigation, and page load)
    • area:package (packages and install)
  • Also area:fleet (the fleet's own tooling) and area:cloud (hosted dependencies, paused).
  • Security is its own area and lives only in the private security channel. Security cards carry no area:* (maintainer, 14:41Z: 「就是私密的安全卡」). Performance is not a separate area (14:38Z: 「感觉性能优化不需要单独专题」).
  • The six areas are standing labels. A sub-epic is a temporary pm:epic, and only the maintainer opens one.
  • Grading:
    • Bug: severity × how often it is hit, looked up in the table, with a new cell: "broken × used daily by builders = p1".
    • Security: who can trigger it × who gains what.
    • A Feature never enters p1. A Task defaults to p3.
    • A card blocking another repo's p1 takes that p1's grade.
    • p1 goes ahead of every area. A paused area no longer demotes its cards.
    • In-flight cards are not regraded.

Authorization

This time seat 1 grades in triage's place and backfills existing cards. The maintainer authorized it as a one-off exception, by 「立一张专题卡,开始执行」 on the plan that named it. It overrides two rules for this epic only:

  • references/lanes/objectstack.md: "first touch and grading stay with triage".
  • SKILL.md:128: "⛔ no backfill of existing cards".

Children, in order (rules merge first, then cards move)

  1. Rule PR: the north-star document. The maintainer merges it.
  2. Rule PR: pm-dispatch, ensure-pm-labels.sh, the checklist axis fields and the scripts that read the old type labels. The maintainer merges it.
  3. Labels: create the new area labels, rewrite the descriptions of the three kept ones, and trial the issue types on one card.
  4. Backfill: area and issue type on the open cards, in groups of ten.
  5. Regrade: per the regrade list, with one line per card.
  6. pm:epic clean-up.
  7. Map each core feature to a platform-checklist item, and add the missing ones.
  8. Closing sweep of cards opened after the 14:30Z snapshot that have no area.

Still open (to be settled in the discussion thread, then added here)

  • Who sets area, type and grade on a new card. The proposal is that the filer sets them and triage's first touch reviews them.
  • Whether cloud adopts the same rules.

area:fleet is added to this card once that label exists (child 3). The card closes when every child is done.

Activity

  1. added
    trackingGenerated anchor/tracker issue — not dispatchable; exempt from the half-state sweep's findings
    pm:epicReserved by a dedicated epic PM, parent or sub-issue; other PMs never take it; never with pm:queue
    on Nov 18, 2026
  2. objectstack-fleet commented on Nov 18, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

    Open point settled, and two added rules · 2026-11-18T15:08Z (relayed from the cloud priorities discussion, the maintainer's words verbatim)

    Cloud aligns. At 2026-11-18T15:07Z the maintainer answered 「同意」 to the cloud plan. Cloud follows this epic's order and rules. It gets its own nine area labels (control, environment, marketplace, ai, enterprise, security, ops, fleet, ux) and its own core feature table in the cloud repo. The cloud half of the pm-dispatch change folds into child 2 (#35207). Cloud seat 1 sends the lanes/cloud.md text and the shared-file edits.

    Rule (a), UX grading. The maintainer said 「4792 是每个人都用到的用户体验卡,你为什么会认为降级」 at 2026-11-18T15:02Z and 「体验相关的优先级也要提升」 at 2026-11-18T15:05Z.

    • A UX problem on a shipped core path that every user hits every time is graded through the Bug table's UX row, and can be p1.
    • A UX Feature defaults to p2, not p3.
    • Raising an in-flight card's grade is allowed. Lowering one still is not.

    Rule (b), repo before area (2026-11-18T14:56Z): a platform root cause is fixed in objectstack. Judge the repository first, then the area.

    Both rules go into children 1 and 2. The regrade list (child 5) is re-read against rule (a) before it runs: no UX card drops to p3 on the old reading.

    The other open point, who sets area, type and grade on a new card, is still open.

  3. objectstack-fleet commented on Nov 18, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

    Ruled · 2026-11-18T15:09Z: at 2026-11-18T15:07Z the maintainer chose 「和 cloud 对齐(推荐)」 on the decision card 「objectstack 的体验卡也按 cloud 的新规则上调吗?」. This makes rule (a) in 6982539552 exact for objectstack:

    1. A UX problem on a core feature that every user hits every time is p1.
    2. Every other UX problem is p2. UX has no p3.
    3. A Feature that improves UX defaults to p2. Other Features still never enter p1, unless one blocks another repo's p1.

    The regrade list is now v3 (/mnt/project-files/pm-orders/objectstack/regrade-2026-11-18.md). It gains a "UX raises" section: #35166 goes p2 → p1, 22 cards go p3 → p2, and #35141, #34889 and #34741 come off the lowering list and stay p2. The lowering list is now 16 cards. Children 1 and 2 write this rule into the grading table and the extra rules.

  4. objectstack-fleet commented on Nov 18, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

    Ruled · 2026-11-18T15:13Z: the last open point, who labels a new card. At 2026-11-18T15:12Z the maintainer said 「新卡的问题你综合分析,我同意」 to this proposal from the discussion thread:

    1. A card filed by an agent (a seat, a dev, the checklist, triage) carries its area, issue type and grade at filing. Its body carries the grade line area · type · severity · reach · evidence. The filing gate refuses a card missing any of them.
    2. A card filed by the maintainer or by an outside person is completed at triage's first touch. A grade the maintainer set himself is never changed: triage adds only the area and the type.
    3. Triage's first touch reviews every new card. When the area or the grade is wrong, triage fixes it and leaves one line with the reason and the old value.
    4. A security problem is opened only as a private advisory and carries no area. This is unchanged.
    5. Backstop: triage sweeps once a day for public cards with no area:* and completes them.

    Child 2 (#35207) writes this into filing-gate and triage. No open points remain on this epic.

  5. objectstack-fleet commented on Nov 18, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

    Confirmed (seat, on the escalation in the contract review of #35214) · 2026-11-18T15:15Z: a card in flight may be raised, never lowered. The permission stands.

    Source chain:

    1. The cloud plan's UX section says 「正在做的卡也可以升级,因为升级不会打断手上的工作」. The maintainer answered it 「同意」 at 2026-11-18T15:07Z.
    2. The maintainer then chose 「和 cloud 对齐(推荐)」 for objectstack (6982581146), at the same minute.

    Rule 3 of the order file, "in-flight cards are not regraded", now means they are not lowered. Lowering an in-flight card stays forbidden.

  6. objectstack-fleet commented on Nov 18, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

    Added to child 2 (#35207) · 2026-11-18T15:20Z: the maintainer reported at 2026-11-18T15:18Z: 「我以前遇到一个问题,我看到一个issue,我在GitHub改了优先级,然后被分诊改回去了」.

    Cause, as read on main by the discussion thread:

    • First touch counts a card that got priority:* within its filing minute as untriaged "not by actor" (references/triage-duties.md:19, disjunct ⑤).
    • No rule protects a grade the maintainer set by hand on an existing card.

    Proposed rule. It is written into #35207, and the maintainer reviews it when he merges that PR:

    1. A grade the maintainer set by hand is final. Before changing priority:*, triage and the seats read the card's latest grade-change event, and leave the grade alone when the maintainer set it.
    2. To disagree, leave one line with the reason on the card and ask him through pm:awaiting-maintainer. The label stays as it is.
    3. Disjunct ⑤ still first-touches, but it adds only the area and the type.
    4. Telling a person from an agent by the label event is measured on one card in the PR first, for example the relay bot as actor or performed_via_github_app. If no field tells them apart, the maintainer hears that.
    5. label-write.mjs refuses to change a grade the maintainer set by hand unless the comment cites his words in a Ruling-ref: line. If that is too large for the PR, it becomes a named follow-up.
  7. 12 remaining items

  8. objectstack-fleet commented on Nov 18, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

    Ruled: the maintainer's words after 15:58Z that PR #35223 encodes, recorded verbatim here (contract review E1, 6988022052). All times are 2026-11-18 UTC.

  9. objectstack-fleet commented on Nov 18, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

    Premise corrected (contract review E4 on PR #35223, 6988773607): item 2 of 6982855148 routed a disputed hand-set grade to pm:awaiting-maintainer. That parks the card, because it is an exclusive state that is never dispatched. That conflicts with the maintainer's 15:18Z point that a grade he set by hand is final and stays as it is. PR #35223 at f7034cf therefore writes it as one comment line, and the grade and the card's state stay unchanged. This is the seat's reading of 15:18Z. The maintainer's merge of #35223 confirms it; if he wants the parking route instead, it is a one-line change in filing-gate.

  10. objectstack-fleet commented on Nov 18, 2026

    @objectstack-fleet
    ContributorAuthor

    repo:objectstack#1 · os-warren · session_01JQwxbabAdcWyApSTGBYJNY

    Ruled (maintainer, decision card, 2026-11-18 23:58Z, 「可以,照现在合并」): contract review E3 on PR #35223 (6988022052) is accepted as is. Grades that seat accounts wrote directly before the relay, without the app marker, read as hand-set and are protected, so triage does not regrade them. A change to one comes from the maintainer, or from a card carrying his words in a Ruling-ref: line. No count is owed before the merge.

  11. objectstack-fleet commented on Nov 19, 2026

    @objectstack-fleet
    ContributorAuthor

    epic:#35205#1 · os-warren · session_01JQwxbYJqoPAoSpWTMpH1yq

    Blocked-state sweep and the new mechanism card · 2026-11-19T02:06Z

    The maintainer, 2026-11-19 in the objectstack priorities discussion thread: 00:26Z 「先立卡改机制,排查现有的卡改状态」; 00:28Z 「这种问题也应该优化 skills: 等维护者做的那一步,单独立一张维护者卡;开发卡关掉,被挡的卡放开。」; 00:32Z 「可以拆的都同意。」「如果需要技能优化也要处理」; 00:42Z 「ok」 (partial-block review).

    Mechanism card: #35259 (child of this epic, pm:queue, p2). Ten items: the Blocked-by: line is the only source; self-release; a blocker takes the top grade; holds match; pm:blocking retires (with #35246); fleet cards chain only on shared files; the maintainer's step gets its own card; only the waiting part stays blocked; mutual blocks and cycles are reported; product choices go to the decision list. The skill and script PR is not built yet.

    Fleet skills clean-up order (item 6, replaces the one-by-one chain):

    Cards split off (item 7/8):

    objectstack, other changes: back to pm:queue: #34821 #34746 #34670 #34648 #32644 #26688 #35143 #34411 #35123 (ruled A) #35101 (ruled A). Line-start Blocked-by: written: #34820 #32500 #30806 #34988 #34920 #34770. Follow their blocker onto hold: #33933 #32749 #35081; #30887 on hold for its cloud readings. #32439 → needs-user-decision. Closed: #30284 (done), #33824 (mutual block with #34411; its cloud half is #34411). #32062 p3 → p2. #31908 pm:blocking removed (#31527 keeps it: it blocks #30806). #34946 pm:queue → pm:blocked (its body named an open blocker). Whole-card waits confirmed with a reason: #32063 #32065 #32064 #31865 #31889 #32043 #32440 #34012 #34268 #34469.

    cloud: #4304 #3891 back to pm:queue; #3929 → pm:awaiting-maintainer (the composed artifact is on staging now); #3309 on hold behind #4533 (「3309 同意」); #3380 closed (two human sign-ups moved to #4706); #3833 → needs-user-decision; Blocked-by: written on #4792 #4689 #3636.

    hotcrm: #2531 #2526 back to pm:queue (platform fixes are in 18.6.0); #2642 → pm:on-hold until a release after 18.6.0 carries objectstack#35142; #2059 closed (its staging reads are cloud#3929); Blocked-by: written on #2622 #2621 #2560 #2668 #2600 #2569.

    Left as they are, for the maintainer: #35084 and objectstack-ai/cloud#4457 wait on private security advisories, which no Blocked-by: line can name; objectstack-ai/hotcrm#2598 stays pm:blocked on a closed card per the maintainer's 「接管并改成阻塞」.


    Generated by Claude Code

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:fleetpm:epicReserved by a dedicated epic PM, parent or sub-issue; other PMs never take it; never with pm:queuetrackingGenerated anchor/tracker issue — not dispatchable; exempt from the half-state sweep's findings

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions