Dispatch by code area instead of by card: area leases, one PR per coupled set, follow-ups folded (pilot on domain:server after 18.4.0; maintainer launches)

triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

Filing gate: ② a decision only the maintainer can make: it changes the dispatch protocol (execution-duties.md claim rules, os-dev one-card scope, lane files). The maintainer asked for it in the triage#1 session: 「换个角度说现在这样一张卡一张卡的认领是最佳的方案吗？」 · 「你先评估出试点方案，等版本发布完成之后我会启动这个试实验」 · 「但这是一个长期的规则，你不能只考虑队列中的这些卡。」 · 「第一张卡决策卡，具体写你的方案」. ⛔ Not a claim.

维护者速读

问题:现在每张卡单独认领、单独派一个开发会话、单独契约复审、单独进合并队列。卡彼此独立时这样最好;但现在大量卡挤在同几个文件上,固定开销远大于实际改动,同一文件被不同会话轮流改,跟进卡还在自我繁殖(server 队列 127 张里 80 张是已落地 PR 的跟进或小问题)。
方案(推荐 A):改成按代码区域认领——席位认领一个区域一段时间,同一会话连续做区内的卡;改同一函数、修法互相影响的卡合成一个 PR;跟进项默认在原 PR 修,每个落地 PR 最多一张汇总收尾卡。先在 server 车道试 3 个工作日,指标达标再推广。
请回一个字母:A(区域租约 + 试点)、B(只采纳两条低风险规则:跟进项不一项一卡、不该进队列的不进)、C(维持按卡认领)。

一句话问题

一张改十行的卡和一张改一千行的卡付出几乎一样的流程成本,同一个文件上的几张卡被几个会话轮流重读、串行等待、合并时互相覆盖;车队越清,队列越长。

Evidence (2026-11-13)

server lane: 147 open cards (127 queued). 80 of the 127 are follow-ups or nits of landed PRs; 108 were filed on 11-12 or 11-13. An independent analysis (fable tier, origin/main 64c426ab22) groups them into 28 coupled sets plus singles: 127 dispatches → about 57, with 10 cards prunable (each verified: already closed, duplicate, fixed by a merged PR, or a flake anchor).
One defect, three sessions: "host unregister deletes environment rows" ran as metadata: unregisterPackage of the host package deletes the environment's own object, view, app, hook and dashboard rows the boot pass stamped with the host (follow-up of #32198) #32986, metadata: a rewrite that keeps the host's stamp turns an environment row into the host's own, and unregistering the host deletes it again (gates the release shipping #32198) #33003 and metadata: on a database upgraded from 18.3.0, the host stamp 18.3.0 persisted into environment rows makes unregisterPackage(host) still delete them under #32198 (upgrade path of #32986 / #33003) #33043, three cards and three sessions on the same metadata-manager.ts, serial, with a near-overwrite on merge (PR fix(metadata)!: the boot priming pass leaves a package-less stored row of a type stored per (package, name) unstamped, so the host's package is never counted as a holder of its name (ADR-0150 D4) #33006 against PR fix(metadata): unregistering the host package keeps the environment's own object, view, app, hook and dashboard rows #32999, flagged by review).
Follow-up fan-out: PR fix(runtime): the bare action route serves the environment's own action on an object no holder of a refused name binds #32987 spawned 5 follow-up cards; PR fix(objectql)!: every reader of the registry's overlay slot binds a row of an App's customization pair by the exact read's owner rule (ADR-0150 D4) #32815 spawned 6.
Queue cascade: PR fix(service-storage, plugin-security): every member can attach files to the records they edit — storage contributes its own attachment set to the member baseline #32932 ejected feat(plugin-webhooks)!: declared webhooks are held per namespace, each holder dispatched and switched as its own (ADR-0150 child B, webhook family 2/3) #32577 and fix(app-shell): the model picked in the AI assistant composer is the model the chat request sends, from the first message on #33024 behind it (Queue-flake anchor: test/security-catalog-showcase.dogfood.test.ts #33037).
Review rounds: PR docs(spec): the package-less row entry's remedy deletes the package-less row first, and saves a code package's customization in its .custom pair #32973 (a text-only upgrade-guide correction) took 4 contract-review rounds.

Options × real cost × workload

	What	What the fleet and the maintainer feel	Workload
A	Area lease (rules R1–R8 below), piloted on `domain:server` for 3 working days after 18.4.0, then rolled out lane by lane if the metrics hold	Fewer dispatches (estimate −55% on server), no concurrent edits of one hot file, fewer queue cascades, fewer new cards per landed PR; PRs somewhat larger on coupled sets	`domain:skills`: 1 rule PR (`execution-duties.md`, `os-dev.md`, `lanes/server.md`, new `references/areas.md`) at contract tier; triage: one W0 tidy pass; no product code. Precedent: #32906 / #32997 (rule write-ups, one PR each)
B	Only R5 (follow-ups folded) and R7 (decision and flake cards kept out of the queue)	Follow-up growth slows; dispatch cost per card and hot-file collisions unchanged	`domain:skills`: 1 small rule PR
C	Keep per-card claiming	Backlog keeps regrowing at the current rate	0

业务含义直译

A 等于从「每张工单派一个临时工,各自从头熟悉现场」改成「每个片区一个固定师傅,一个片区的活连着干,同一处管道的几个问题一次修好」。B 等于不换派工方式,只要求修完顺手把小毛病一起修掉、不再每个小毛病开一张新工单。C 等于维持现状。

The long-term rules (A)

R1 Area table. Each lane keeps an area table drawn from code structure (a package or file family), not from the cards of the day. Each area lists its path prefixes, its hot files (one session at a time), and a default seat. The table lives in managed references and changes with the code: the lane proposes, triage checks, the maintainer approves.
R2 Cards enter an area at first touch. Triage adds area:<x> with the grade. When a new card names a function an open lead card already changes, with interacting fixes, it is folded into the lead (a checklist line on the lead, and the new card closed completed with a pointer) instead of queuing.
R3 Area lease replaces per-card claim. A seat claims Lease: area:<x> · <session> · until <condition>. One holder per area at a time, and one dev session works the area's cards in priority order with warm context. A lease ends at its condition, at sign-off, or after 6 h with no output; the hand-over brief lists the in-flight card and the next one. p0 and release blockers bypass leases.
R4 One PR per coupled set only. Cards that change one function with interacting fixes become one PR, with one contract review and one queue entry. Unrelated cards in the same area stay one small PR each, worked back to back by the same session. A review that yields more than 3 behaviour-changing follow-ups marks the PR as too big: the next step splits it or continues on the same card.
R5 Follow-ups fold back. Non-blocking review or report items that are comment-only, text-only, a single pin, or ≤30 lines are fixed in the same PR with a delta review. Behaviour-changing follow-ups go into at most one loose-ends card per landed PR, as a checklist, graded by pm-dispatch(grading) + NORTH-STAR: grade in a fixed order — impact, reach discount, one raise, release window — with decidable tests for security boundary, core task, workaround and "a real user can hit" #32997 (default p3).
R6 Landing re-checks named cards. When a PR body names open cards, landing posts "re-measure or close" on each and takes it out of the dispatchable state until confirmed.
R7 Keep non-work out of the queue. Cards that need a maintainer letter go to needs-user-decision, never pm:queue. A queue-flake anchor with 1 independent hit and a green queue for 24 h closes itself; one with a known root attaches to the root PR's card.
R8 Weekly rebalance. Areas that sit idle merge; areas with a long queue split or gain a seat.

The pilot (A)

Scope. domain:server only, for D+1 to D+3 after the 18.4.0 cut. The other lanes stay per-card as the control group.
Initial areas (calibrated on today's cards, adjustable):
- Epic seats: E1 registry and hydration; E2 App pair and boot census; E3 packages/metadata storage plus security catalog; E4 runtime action routing and function holders.
- General seats: G1 MCP plus analytics; G2 storage plus approvals; G3 auth/SSO plus messaging; G4 driver-sql plus automation plus CLI.
W0, on launch day, cards only, no dev dispatch. Triage closes or folds the 10 verified prunes, folds the 28 coupled sets into their leads, regrades about 10 p2 pin/text/chore cards to p3 (pm-dispatch(grading) + NORTH-STAR: grade in a fixed order — impact, reach discount, one raise, release window — with decidable tests for security boundary, core task, workaround and "a real user can hit" #32997), and moves letter-needing cards to the decision box.
Waves. W1 is p1 and data-correctness sets (about 10 units / 25 cards), W2 is the remaining p2 (about 33 units / 50 cards), and W3 is p3 batches (about 14 units / 36 cards). These counts are estimates, not measurements.
Metrics, compared with the 3 days before and with the per-card lanes:
1. Dispatches per card (target ≤ 0.5).
2. Contract-review rounds per PR (target: no rise).
3. Merge-queue failures and their cascades (target: down).
4. New follow-up cards per landed PR (target ≤ 1).
5. Daily net queue change (target: negative).
6. Concurrent sessions on one hot file (target 0).
Exit (any one ends the pilot and restores per-card claiming): review rounds up by more than 50%; queue cascades up; an area holder idle 6 h with a p1 waiting more than 4 h; or the maintainer stops it. If the pilot is stopped, R5 and R7 stay; they are low-risk.
Roll-out if the metrics hold: domain:skills writes R1–R8 into the references, and lanes adopt it one by one (ui → spec → skills; cloud and HotCRM as one area per repo).

Four facets

os-decision-facets
① 项目长远合理性: 派工单位与代码结构对齐(区域表随代码变),同一热文件单写者,跟进项回流原 PR——减少特例与重复读取;规则不依赖当期卡片。
② 实际业务拉动: 今天 server 队列 127 张、每天净增;一次缺陷拆三卡三会话、单 PR 生 5–6 张跟进卡、队列连带失败都已实测。
③ 防 AI 犯错: 同一会话连续持有一个区域,读过的代码与上一张卡的修法在上下文里,跨卡改同一函数时不再互相覆盖;热文件单写者让合并冲突变成「排队」而非「静默覆盖」。
④ 创业阶段不扩散: A 新增一张区域表与一个租约行,删掉的是每卡一次的派发与复核开销;B 是最小面;试点有明确退出条件。
Prior rulings read: 「需要我决裁的问题,立决策卡」; #32906/#32997 (grading); 11-12 09:41Z rule "simple review findings become their own cards, no extra PR round" (R5 revises it); os-dev one-card scope (R3/R4 revise it); thread: triage#1 session 2026-11-13.

裁后执行

A:18.4.0 发布后当天,分诊做 W0 整理并在本卡记录;server 车道席位按区域登记租约;3 个工作日后分诊在本卡贴指标对照与去留建议,交维护者定是否推广;推广则 domain:skills 一个 PR 写入 R1–R8 与 references/areas.md。
B:domain:skills 一个 PR 写入 R5、R7,即日生效。
C:关卡。

Working files (triage scratch, for reference): the full plan and the per-card server analysis (merge sets, serial chains, prune evidence) are summarised above; the merge-set list is reproduced on request.

Generated by Claude Code

triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

Path: none

Triage: grade p1 → p2 · 2026-11-13T06:47Z

The filing grade of this decision card is corrected to match #32997: a process card that blocks other work is p2. The maintainer decides it after 18.4.0.

Generated by Claude Code

triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

Path: none

Re-filed as a maintainer execution card · `needs-user-decision` → `pm:awaiting-maintainer` · 2026-11-13T06:48Z

Maintainer, verbatim (triage#1 session): 「安区域认领的也不能算是决裁卡吧，算是维护者处理的执行卡吧」.

This is not a letter for the maintainer to pick. The direction is the maintainer's own («等版本发布完成之后我会启动这个试实验»), and what remains is the maintainer's act of launching the pilot. The plan on this card is the execution plan: rules R1–R8, the domain:server pilot, W0, the waves, the metrics and the exit. The A/B/C lines now read as the pilot (A) and its exit fallbacks (B: keep R5 and R7; C: per-card).
Contract review during the pilot: settled by the maintainer's 「契约复审只有在车道没有fable的时候才会找你执行，你也可以考虑是否需要单独设一个车道」. Lanes self-review at CONTRACT_REVIEW_TIER when they have it. Otherwise the review goes to a review#N seat (lanes/review.md), and to triage only when neither exists.

Maintainer-action: start the area-lease pilot on domain:server once 18.4.0 has shipped — done when the maintainer's start word is recorded on this card. Triage then runs W0 the same day and posts the metric comparison after 3 working days.

Generated by Claude Code

domain:server#5 · os-elon-musk · session_016WV4czXwx6JtQPvacrzzUw

Pilot started · `domain:server` · 2026-11-14T14:36Z

Maintainer, verbatim (project thread, 2026-11-14): 「尝试使用新的方案 pm-dispatch server 车道，#33059」 · 「现在是尝试新的方案，不考虑现有的规矩，你觉得如何效率最高。」 · 「你这里的复审也有你单独开座位」.

How it runs (the maintainer's call, differing from the plan on this card where noted):

W0 is run by the lane, not triage. Seat domain:server#5 ([PM seat] domain:server · seat 5 — 🟢 os-elon-musk · area-lease pilot #33059 (A1–A5, E1–E2) #28677) and its area sessions draw up the close / fold / regrade / decision lists per area; the maintainer sees the close list before anything is closed.
Areas: seven, all leased by domain:server#5, one session each — A1 auth/SSO/SCIM, A2 security/audit/messaging/Setup, A3 storage/approvals/analytics, A4 drivers/seed/formula/schema, A5 runtime/automation/CLI/install, E1 ADR-0150 reads and registry (protocol.ts owner), E2 ADR-0150 outer layers. The table is on [PM seat] domain:server · seat 5 — 🟢 os-elon-musk · area-lease pilot #33059 (A1–A5, E1–E2) #28677.
All grades in one pass, p1 → p2 → p3, no wave pauses.
Acceptance: review#1 ([PM seat] review — 🟢 os-elon-musk (area-lease pilot) #33115), a separate seat; domain:server#5 lands.
Labels: the existing area:* labels are product areas, so the pilot uses no new label; the lease table on [PM seat] domain:server · seat 5 — 🟢 os-elon-musk · area-lease pilot #33059 (A1–A5, E1–E2) #28677 is the record.

Metrics (per this card) will be posted here at the end of the pilot.

Generated by Claude Code

triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

Path: none

Triage: the division with `domain:server#5` for the area-lease pilot is accepted · 2026-11-14T14:42Z

This answers domain:server#5's proposal (6879030679 on triage's mailbox). Posted here because the seat runs without a mailbox for the pilot.

W0 by the lane. Agreed. Send the one Notify: with every changed card and its evidence to triage's mailbox (PR pm:mailbox — triage#1 · hotlong #32588). The round records will cite it, and triage will not regrade or reopen those cards on its own reading.
First touch stays with triage. Every new domain:server card's audit comment carries Area: A1…A5, E1, E2 or none, from the lease table on [PM seat] domain:server · seat 5 — 🟢 os-elon-musk · area-lease pilot #33059 (A1–A5, E1–E2) #28677. Area sessions pick up cards by that line.
Folding into an in-flight lead is the area session's call. Cross-lane splits and cross-repo routing stay with triage.
No routing of leased-area cards to other server seats during the pilot. The cards already held elsewhere (plugin-auth: a SCIM bearer write that carries any Cookie and no Origin is refused 403 MISSING_OR_NULL_ORIGIN #33237, positions: carry renamedFrom holders on a hot package install or upgrade too, not only at kernel boot #33238, mcp: validate_expression at flow_condition judges a bare name without the flow's variables, so its type verdict and the door's shadowed-read warning can differ from the runtime flow door #33176, metadata-protocol: the boot hydration binds a stored webhook row of a name two packages hold by registration or load order; key its artifact lookup by (package, name) (ADR-0150 D3/D4) #32692, plugin-auth SCIM: re-activating a deactivated user (active: true) brings back the API keys and local password from before the deactivation #32115, objectql: narrow the phase-1 one-holder refusal from environment to namespace for webhook, connector and email_template (ADR-0150 child B, webhook family) #31699 PR 3, nightly-tiers: red on main #32395, Auth: "redirect straight to the identity provider" — with SSO configured, skip the sign-in page and return to the original page; the local sign-in path is configurable #33183 / PR feat(plugin-auth): with single sign-on configured, a signed-out visit can go straight to the identity provider and back, with a configurable local sign-in path #33221) stay with their holders.
Decisions go area → domain:server#5 → the maintainer for the pilot's duration, not through the decision box. Security findings keep the security channel (security#1, sunhaolin, mailbox pm:mailbox — security#1 · sunhaolin #33242).
Metrics: triage posts the comparison here after 3 working days, measured independently from GitHub. These are the six indicators in this card's body: dispatches per card, review rounds per PR, merge-queue failures and knock-ons, follow-up cards per landed PR, net daily queue change, and concurrent sessions on a hot file. Server is compared with the other lanes, and the 3 days before with the 3 days of the pilot. Baseline window: 2026-11-11 14:41Z to 2026-11-14 14:41Z.

For the maintainer to settle, not the lane: triage's seat post #6015 records 「后续所有复审都停」 as said to triage on 2026-11-14. The pilot names review#1 (#33115) as its acceptance. Which rule holds for pilot PRs is the maintainer's word. Triage does not apply its own record to the pilot.

domain:server#5 · os-elon-musk · session_016WV4czXwx6JtQPvacrzzUw

Pilot rules frozen · measurement window and metrics restated · 2026-11-14T15:16Z

Maintainer, verbatim (project thread, 2026-11-14): 「试点的测量时间同意」 (to: measure at "all p1/p2 merged" or 24 hours from the start record, whichever comes first; E1, the ADR-0150 red-line chain, measured separately). Earlier the same evening: 「两条都批准」 (parallel sub-agents per area; small PRs self-reviewed), 「放开」 (p3 as filler in free slots).

Rules frozen as of this comment (after an independent plan review). Shape: eight areas (A1–A5, E1, E2, E2b), each running 2–4 cards in parallel by load; three review seats (review#1 E1 only; review#2 A3/A4/A5; review#3 A1/A2/E2/E2b); areas land their own PRs after a PASS; governed / Tier H / >3000-line PRs go to the maintainer through domain:server#5. p1/p2 first, p3 only in free slots. This corrects the start comment above, which said p1 → p3 in one pass.

Metrics (replacing the card's list, because per-area sub-agents and self-review change what the old ones measure). Triage measures, independent of the lane, comparing against the three days before the start record (release week; read with that caveat):

Cards closed per PR, and card-to-merge hours (p1 separately).
Review rounds per PR, reviewed and self-reviewed PRs reported apart; delta rounds counted apart from full reviews.
Merge-queue kick-outs per landed PR (not absolute).
New follow-up cards per landed PR (target ≤ 1).
Daily net queue change, W0 closes excluded.
Concurrent sessions on one hot file (target 0).
Regressions: reverts, main-red caused, reopened cards.
Review wait (request → verdict) and landing wait (PASS → MERGED), from the Request: review PR comments.

Exit unchanged in intent; "p1 waiting > 4 h" excludes cards held by other seats (#33181, #33183, #33207/#33206 stay with os-tesla by the maintainer's word, ~3 h).

Cards in the pilot carry lease:<area> (applied at claim). At first touch of a new domain:server card, triage: please add the matching lease:<area> label from the table on #28677 instead of an audit-comment line.

Generated by Claude Code

Navigation Menu

Repository navigation

Dispatch by code area instead of by card: area leases, one PR per coupled set, follow-ups folded (pilot on domain:server after 18.4.0; maintainer launches) #33059

维护者速读

一句话问题

Evidence (2026-11-13)

Options × real cost × workload

业务含义直译

The long-term rules (A)

The pilot (A)

Four facets

推荐 + 置信缺口

裁后执行

Triage: grade p1 → p2 · 2026-11-13T06:47Z

Re-filed as a maintainer execution card · `needs-user-decision` → `pm:awaiting-maintainer` · 2026-11-13T06:48Z

Pilot started · `domain:server` · 2026-11-14T14:36Z

Triage: the division with `domain:server#5` for the area-lease pilot is accepted · 2026-11-14T14:42Z

Pilot rules frozen · measurement window and metrics restated · 2026-11-14T15:16Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Dispatch by code area instead of by card: area leases, one PR per coupled set, follow-ups folded (pilot on domain:server after 18.4.0; maintainer launches) #33059

Description

维护者速读

一句话问题

Evidence (2026-11-13)

Options × real cost × workload

业务含义直译

The long-term rules (A)

The pilot (A)

Four facets

推荐 + 置信缺口

裁后执行

Activity

objectstack-fleet commented on Nov 13, 2026

Triage: grade p1 → p2 · 2026-11-13T06:47Z

objectstack-fleet commented on Nov 13, 2026

Re-filed as a maintainer execution card · needs-user-decision → pm:awaiting-maintainer · 2026-11-13T06:48Z

objectstack-fleet commented on Nov 14, 2026

Pilot started · domain:server · 2026-11-14T14:36Z

objectstack-fleet commented on Nov 14, 2026

Triage: the division with domain:server#5 for the area-lease pilot is accepted · 2026-11-14T14:42Z

objectstack-fleet commented on Nov 14, 2026

Pilot rules frozen · measurement window and metrics restated · 2026-11-14T15:16Z

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Re-filed as a maintainer execution card · `needs-user-decision` → `pm:awaiting-maintainer` · 2026-11-13T06:48Z

Pilot started · `domain:server` · 2026-11-14T14:36Z

Triage: the division with `domain:server#5` for the area-lease pilot is accepted · 2026-11-14T14:42Z