Repository navigation
[PR] decideNudge(): rotate count-triggered T2/T3 distillation nudges with ready T1 on the growth path - #2519
ranxianglei wants to merge 9 commits into
Conversation
…th path (#2513) The growth path of decideNudge() short-circuited on t1Eff >= the T1 mass threshold before ever reaching the tier-2/tier-3 count branches, so an explicitly lowered tiers.tier2Trigger/tier3Trigger was structurally dead in any session whose raw compressible mass stayed above the threshold (billion-context-pi#628: 22 active T1 blocks + t1Eff 100K-400K, zero T2 nudges across the whole session). Fix (issue direction A, ported from acp-kernel#510 fixing acp-kernel#509, migrated here as #2513): count-ready tiers now join a rotation pool with a ready T1 on the growth path. T1 keeps first pick until it has gone (nudge.lastInjectedTier !== 1); then the slot hands to the count-ready tier with the oldest cadence stamp (never-shown = oldest, tie -> lower tier) and back to T1 the next cycle — neither side starves whether the model ignores or complies with one of them. Rotation memory lives in a new OPTIONAL state field nudge.lastInjectedTier, deliberately NOT cleared by the compression-success reset (which still clears lastShownByTier/baselines): using the existing per-tier stamps would let a model that keeps draining raw ranges restart every tie at T1 — the exact production shape of #628. Absent field = null = legacy T1-first, so persisted pre-fix states need no migration. With the default triggers (1000/2000) the candidate pool stays empty and the legacy cascade runs unchanged — default behavior is byte-identical (pinned by a dedicated test). The pressure path, token-mass cascade, first-sight bypass and reason-string formats are untouched.
… -> 1000/2000 since #379) The TierConfig JSDoc still documented "Default 5" / "Default 10" while the actual defaults have been 1000 / 2000 ever since #379 turned the count path off by default. Same mechanism domain as #509 (the count path's semantics), so it rides along as its own labeled commit: fix the drifted values and document the new rotation behavior in the README nudge section.
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.8208-pr.2519.18641e1This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr2519.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 Review complete. Evidence: branch sits on current master 结构化八问
行为变更清单(与 PR 正文披露一致):显式调低 trigger 的会话——旧:T1 在 t1Eff ≥ 阈值期间永远独占 → 新:T1/T2/T3 槽位轮换(T1 首轮优先保留,其后 oldest-stamp count-ready tier)。默认配置会话:无变化(字节级)。 顺手小修(已在 PR 分支补两个独立标注 commit,本地验证:nudge 50/50、kernel 全套 1281/0、typecheck clean):
判定:方向打到根因、回归清点干净、行为变更已按旧值→新值披露、证据链完整(本地红绿双向 + CI)——可合。kernel/ 变更按 Kernel Boundary 属 human-only(不可 auto-merge),请手动合并:#2519 (上述两个 review commit 推送后 CI 会在新 head 上重跑,全绿即可合。) |
# Conflicts: # kernel/package.json # kernel/src/types.ts # package-lock.json
…5698) When a host model only partially complies with T1 compression nudges (folds a few K of the offered mass each time), decideNudge's growth cascade starves T2/T3 distillation forever: the T2 mass leg demands t2Pen > t1Eff behind a T1-first short-circuit, so a persistently high t1Eff makes the distillation slot structurally unreachable even after its own threshold passes — summary blocks accumulate monotonically until the session ceiling (#5671 production incident; #5698 root cause). T1 harvest-stall detection: - A T1 nudge fire records the offered raw mass (breakdown.pendingT1) in state.nudge.lastT1FirePending (consume-once). - On successful applyCompression, realized tokensCompressed is compared against it: a distillation fold (new tier >= 2 block) clears the stall unconditionally; otherwise a T1-shaped fold harvesting less than STALL_HARVEST_RATIO (0.5) of the offered mass latches state.nudge.t1HarvestStall, at/above ratio clears it. No-op calls are not evidence and leave the armed measurement in place. - decideNudge consumes the flag only when tiers.enabled: in the growth band a stalled T1 yields its slot to a cadence-met T2/T3 whose own mass threshold is met (the legacy "> t1Eff" demand drops for this path); in the pressure band the stall removes T1 from candidates when max(t2,t3) clears minPressureBenefit, so arbitration picks the tier that actually delivers. Reasons carry "[T1 harvest stall]". Composes with the #509 count-trigger slot rotation already on this branch: the stall override sits above the count-ready pool, explicit count triggers keep working independently of the flag, and per-tier cadence applies to the redirected slot as usual. Untouched by design: flat 50K growth cadence (KDD #8), the #379 mass-as-demand philosophy (the stall is consulted only once a higher tier's mass leg crossed its own threshold), #194 first-sight re-arm, and the minPressureBenefit gate. Compatibility: both new state fields are optional — pre-fix snapshots lack them, detection stays off, and arbitration is byte-identical (pinned). Eager lanes never latch. Tests: kernel/tests/nudge.test.ts +9 rows (core latch to slot handoff, full-compliance never latches, distillation clears, legacy absent-flag byte-identity, pressure drop/keep, cadence respect, no-op-not-evidence, count-trigger independence). Red-check: 7/9 fail without the fix.
The nudge-slot-rotation change bumped kernel/package.json to 0.0.181 but left kernel/package-lock.json echoing 0.0.180. lock-sync regenerates the kernel lockfile (npm install --package-lock-only) and fails on any drift, so the job went red. Regenerate so the two version fields agree again. Pure lockfile sync — no dependency or semantic change.
(ai: vllm-qwen/qwen3.8-27b) lock-sync 红灯已修复并推回 PR 分支(新 head 是什么问题:这个 PR 把内核版本从 0.0.180 升到 0.0.181( 什么原因导致:升了 影响范围与严重程度:只卡住本 PR 的 CI(lock-sync 红),不影响任何运行行为或最终用户;属于发版流程里的锁文件一致性门禁,不是功能缺陷。 怎么修复的:在 PR 分支上重新生成 是否有回归问题:无。改动只有内核锁文件里两行版本号回显(0.0.180→0.0.181),不碰任何依赖解析或代码路径;本地连跑两次重生成幂等、无残留 diff。 是否破坏缓存:不涉及。纯 manifest 版本字段,与运行时缓存/重试/游标无关。 是否改了设计方向:不涉及。只是补齐一次漏掉的锁文件再生成。 是否引入新配置:不涉及。无新增 env/config/默认值。 验证:新 head 判定:本次红灯(lock-sync)已闭环,PR 无合并冲突,可等全量测试收尾后由人工合并。 |
🔶 需要决策 PR #2519(head 逐条定性(基于 CI 日志失败签名 + PR diff)① storage-render golden ×4(chat/anthropic/responses/google)——本 PR 自身特性导致,属预期副作用 ② #2817 persona cross-wire( ③ #5418 watermark fastpath A/B( 为什么我不直接修
选项
默认(不回复时):按 A —— 等 PR 作者补 golden 重生成 + PR 正文理由 + 本地重跑定性 ②③;在此之前我不再动该 PR 分支。 收工判定本轮:lock-sync 机械修复已完成并转绿( |
…able (#5698) A stored false serializes into every measured session's persisted nudge state and drifts the storage-render goldens for zero information; an initializer in createInitialState did the same for fresh sessions. Absent-only storage: a latch stores true, a clear deletes the key (the createInitialState default is likewise omitted). Consumers already test === true, so behavior is unchanged and feature-inactive snapshots stay byte-identical to pre-feature ones — no golden regeneration needed.
ranxianglei
left a comment
There was a problem hiding this comment.
(ai: vllm-qwen/qwen3.8-27b)
结论:findings-only,不 approve。 本 PR 触碰 kernel/**(compress.ts / state.ts / types.ts)且正文首行带 kernel-change: 声明 —— 按 Kernel Boundary(AGENTS.md「Kernel Boundary」§1「Declare before you touch」+ §3「Human-only review, always」)与本次审核 HARD RULE,kernel 变更一律 human-only、agent 不得 approve。技术面我已独立审完:实现正确、方向成立、测试有牙、无阻塞性缺陷;是否合入需 owner 授权。已在下方补「🔶 需要决策」评论并打 needs-decision 标签。
结构化八问
- 是什么问题:
decideNudge()的 tier 仲裁在两种形状下结构性饿死 T2/T3 蒸馏 —— (A) growth 路径 T1-first 短路,使显式调低的tier2Trigger/tier3Trigger在 raw pending 持续 ≥ T1 阈值的会话里永远够不着(#2513,生产实例 billion-context-pi#628:22 个 T1 块 + t1Eff 100K–400K → 全程零 T2 nudge);(B) T2/T3 mass 腿要求t2Pen > t1Eff,模型部分顺从(每次只折 3–6K)时t1Eff恒 ≥ 50K,mass 腿永不满足、摘要块只增不减直到顶死会话(#5698,#5671 生产事故根因)。 - 什么原因导致的:仲裁把「pending 大」误当「可交付」。T1 的 pending 恰恰在它不可交付时最大 —— T1-first 短路 +
> t1Eff门槛把这个自相矛盾固化了。#5698 实验证明宿主配置改不动(stopgaptierNudgeTokens.t2=30000与 baseline 逐字节相同),只能在 kernel 调度层修。 - 影响范围与严重程度:#5698 为 p1(会话被顶死;生产 floor 17%→42%/12h、229 活跃块、零 T2/T3 触发;手工一次 T2 蒸馏回收 91.6%);#2513 为 p2(显式低触发器形同虚设)。两者都只在「raw pending 长期高 + 模型部分顺从 / 显式低触发器」下触发,默认配置不受影响。
- 怎么修复的:A = growth 路径把 count-ready tier 拉进与 ready T1 的轮转池(T1 先选一次 → 交给最老 cadence stamp 的 count-ready tier,never-shown=最老、tie→低 tier → 再回 T1,严格交替),轮转记忆用新可选字段
lastInjectedTier(刻意不随压缩成功复位,防模型反复抽干 raw range 把每次平局重置回 T1);B = T1 收获停滞检测 —— T1 nudge fire 时记下 offeredpendingT1(consume-once),下次成功折叠按tokensCompressed/offered < 0.5判停滞(蒸馏折叠无条件清除;no-op 不算证据),停滞后 mass 腿过自身阈值即抢 slot(此路径专属地放宽> t1Eff)、pressure 档在剩余 tier 能过minPressureBenefit时把 T1 移出候选(低于 floor 则保持 legacy,避免整条 nudge 被抑制)。 - 是否有回归问题:逐项核过既有行为 —— flat 50K cadence(KDD #8)未动;#379 mass-as-demand 未动(stall 只在 mass 腿已过自身阈值后才被咨询,mass 仍是 need 信号);
minPressureBenefitgate 未动;reason 串仅在新增[T1 harvest stall]标记处追加。默认触发器 (1000/2000) 下轮转池为空 → 逐字节不变(有测试钉);旧持久化快照缺新字段 → 走 legacy 仲裁(有测试钉)。未见无意回归。 - 是否破坏缓存:不涉及。纯仲裁决策改动,不动 wire/golden/前缀渲染;diff 无任何 wire/golden 文件。
- 是否改了设计方向:不改架构,只在既有仲裁阶梯内加两条可达路径 + 三个可选内部状态字段。数据流不变。
- 是否引入新配置:不引入新的用户配置项。复用既有
tiers.tier2Trigger/tier3Trigger+nudge.tierGrowthTokens.{t1,t2,t3}。新增的lastInjectedTier/lastT1FirePending/t1HarvestStall是 kernel 内部状态字段(全部 optional,absent=legacy),非配置面。
独立核验记录(非照抄 issue 结论)
- 控制流端到端追读
kernel/src/compress.ts:2240-2356(growth 阶梯)+:2196-2239(pressure 档 drop-T1)+:875-896(applyCompression 收获停滞测量)+:1518-1526(nudgeNode 武装lastInjectedTier/lastT1FirePending):A/B 两路均正确落地;config.tiers.enabled=false退化为纯 T1(不变);所有新字段读法都是=== true/?? null/?? 0,缺省即 legacy。 - 迁移安全:三新字段全 optional(
types.ts:133-155),createInitialState()显式初始化(state.ts),宿主水合src/state-hydration.ts:31用{ ...fresh.nudge, ...(parsed.nudge ?? {}) }spread —— 旧态载入得安全缺省、新态往返完整;宿主 abort-absorb 路径(src/session.ts:1056-1057)刻意不动这三字段(abort = no-op,与 kernel no-op 语义一致,正确)。 - 测试有牙:
kernel/tests/nudge.test.ts每个 gate 都双向断言(latch / never-latch、drop-T1 / keep-T1-below-floor、cadence respect、no-op-not-evidence、count-independence-from-flag),并对默认配置与 legacy 快照各有一行逐字节钉;red-check 声明 revertcompress/state/types→ 7/9 stall + 5/5 rotation 失败(2 个通过行按设计钉住不变行为)。非恒真断言。 - verif 守卫(KDD #14):
compress.ts在守护清单内(verif/guarded-files.ts:13),但新增构造(for-loop / non-null /.some/.has)在该文件里早已大量存在(pre-PR 已有 32 个for (、3 个 non-null-dot、.some×3、.has×13),不构成子语言越界 → subset-guard 不会因本 PR 新红。(本地未能实跑该守卫:此工作区未装tsx,属环境限制而非代码问题;该守卫随在途 CI test shard 跑。) - 版本纪律:kernel
0.0.180 → 0.0.181,lockfile 同步 —— 末 commitcff2d7928修了一处真实的 lock-sync red(package.json 已 bump 而kernel/package-lock.json仍 echo 0.0.180)。 - 顺手文档修(独立标注 commit
0b71a9578):TierConfigJSDoc “Default 5/10” → “Default 1000/2000 (#379)”,已对kernel/src/config.ts:8核实属实(真实默认即 1000/2000)。
一处设计取舍(非缺陷,已文档化 + 钉测)
stall override 位于 #509 count-ready 池之上 —— 同时存在 latched stall 与 count-ready tier 时,mass-leg stall 路径优先于 count 轮转。正文「How A and B compose」与测试(#5698 × #509)都已说明并钉住,属有意为之,非疏漏。
CI(读镜像缓存,未轮询 gh)
关键门禁已绿:kernel-guard ✅(校验 kernel-change 声明 + 版本纪律)、gate ✅、test-import-graph ✅、mysql-contract ✅;全量 test shard(ubuntu/windows × node22/24,含 verif 守卫)+ static-gates 仍在途(13 pending)。合入判定以在途 head 全绿为准。
阻塞项
仅 kernel-change 授权边界(HARD RULE),非技术缺陷。技术面我认为可合。请见下方「🔶 需要决策」评论走 owner 授权流程。
|
🔶 需要决策 (ai: vllm-qwen/qwen3.8-27b) 请 owner 授权本 kernel 变更合入。本 PR 触碰
选项:
|
🔶 需要决策 CI 状态更正 + 归因边界(接我前两条诊断;head 已推进到作者的 先摆正一处过时信息:授权请求里写「全量 test shard … 在途」。实际 run 41971511702(head_sha 确认 = 红的构成
为何停手:小机械修复边界内没有可落地的修法——golden 重生成是作者对自己特性的取舍;第 2 组归因未定且处置权在作者/owner;ci-fixes 走不通。needs-decision 标签已在位。 选项
默认(不回复时):按 A —— hold 合入;作者处理 golden;第 2 组转 #4599 求 master 基线;期间我不再动该分支。 收工判定:本轮无新增代码改动(作者已自行推 |
…tay stable (#5698) The #509 rotation memory was initialized to null in createInitialState. Newer master hydration fills missing nudge keys from the fresh defaults, so every re-hydrated legacy session picked up nudge.lastInjectedTier=null and all nine storage-corpus digest pins drifted (folded/twinfile/zstd red in CI). The sole reader already normalizes via (lastInjectedTier ?? null), so dropping the initializer is behavior-neutral: absent = never injected = legacy T1-first, and undefined keys drop out of persisted snapshots.
[bot] 🏷 PR review lane complete (ai: vllm-qwen/qwen3.8-27b). 判定:不 approve(HARD RULE — kernel 变更)。 本 PR 触碰 已产出:
方向关:通过。 #2513(p2,count-trigger 饿死→Fix A slot rotation)+ #5698(p1,#5671 生产根因→Fix B harvest-stall);两者均被实验证明宿主配置修不动,正确落在 kernel 仲裁层。 CI: 关键门禁绿(kernel-guard/gate/test-import-graph/mysql-contract),全量 test shard + static-gates 在途。合入以在途 head 全绿为准。 下一步:等 owner 对 kernel-change 拍板。 无小问题需顺手修,未开新 issue。 |
🔶 需要决策 进展(接前两条):作者连续两个 absent-only 修复( 现在只剩 3 条红,且都落在本 PR 窄 kernel diff 没碰的子系统:
这 3 条在分支所有 head( 我的判断:本 PR 自身引入的红(storage-render / storage-corpus golden)已被作者根治;剩下 3 条是 master 侧问题,不该拿它们卡本 PR 的合并。 选项
默认(不回复时):按 A —— 记为继承红、转 #4599、不阻塞本 PR;期间我不再动分支。 收工判定:本轮无代码改动(作者自行推进至 |
🔶 需要决策 重复触发、head 与 run 未变(仍 作者的两个 absent-only 修复已清掉本特性全部持久化面红(两个分片逐一核实):
全矩阵现在只剩同一批继承红(都落在本 PR 窄 kernel diff 没碰的子系统 dsh/persona/watermark):dsh-guard stamping(跨多个分片)、#2817 persona(requests 期望 9 实得 8)、#5418 watermark(B stamp null)。它们在所有分支 head( 决策不变(接上一条 A/B/C,此处压缩复述以便独立阅读):
默认(不回复时)= A。needs-decision 标签已在位。 收工判定:本轮无代码改动(作者自行推进至 |
[ework] auto-fix stalled: test (windows-latest, 22, 4), test (ubuntu-latest, 24, 1), test (ubuntu-latest, 22, 1), test (ubuntu-latest, 22, 2), test (windows-latest, 22, 3), test (windows-latest, 22, 2), test (ubuntu-latest, 24, 3), test (ubuntu-latest, 22, 3), test (ubuntu-latest, 24, 2), test (windows-latest, 22, 1) — stopping for human review |
kernel-change: fix structural starvation of T2/T3 distillation nudges in decideNudge() — two sub-defects of one arbitration mechanism: (A) count-triggered tiers unreachable behind the T1-first short-circuit (#2513, port of acp-kernel#510 fixing acp-kernel#509); (B) mass-leg tiers unreachable under partial T1 compliance because the mass leg demands
t2Pen > t1Eff(#5698, root cause of the #5671 production incident). Host side cannot express either fix through config; owner requested the root fix in the #5671 discussion. In-repo kernel/ per #2092.Closes #2513
Closes #5698
Problem — one mechanism, two starvation shapes
decideNudge()'s growth path short-circuits ont1Eff >= tierThresholds[1]before any higher tier can be reached, and its pressure path picks max-pending among all tiers — which keeps being T1, because T1's pending stays high precisely BECAUSE nothing folds it. Two shapes:A (count-triggered, #2513): an explicitly lowered
tiers.tier2Trigger/tier3Triggerwas structurally dead in any session whose raw compressible mass stayed above the T1 threshold. Production instance (billion-context-pi#628, 256K window): 22 active T1 blocks (~8.8K summary tokens) + t1Eff 100K–400K → zero T2 nudges across the whole session.B (mass-leg under partial compliance, #5698): the T2 mass leg requires
t2Pen >= tierThresholds[2] && t2Pen > t1Eff. When a host model only partially complies with each T1 nudge (production logs: 3–6K folded per offered ~50K),t1Effstays ≥ 50K forever, so even a T2 backlog far past its own threshold (measured: 112K vs 447K) can never win a slot — summary blocks accumulate monotonically until the session ceiling dies (#5671: floor 17%→42% over 12h, 229 active blocks, zero T2/T3 fires; one manual T2 distillation reclaims 91.6%). No config can express "prefer T2 when T1 stops delivering":tierNudgeTokensmoves thresholds, not the else-if structure (verified byte-identical no-op experimentally).Fix A: slot rotation (count-triggered tiers)
Count-ready tiers now join a rotation pool with a ready T1 on the growth path:
nudge.lastInjectedTier !== 1);Rotation memory is a new OPTIONAL state field
nudge.lastInjectedTier, deliberately NOT cleared by the compression-success reset (which still clearslastShownByTier/baselines): reusing the existing per-tier stamps would let a model that keeps draining raw ranges restart every tie at T1 — the exact production shape of #628. Absent field = null = legacy T1-first, so persisted pre-fix states need no migration (adapters unchanged).Fix B: T1 harvest-stall detection (mass-leg tiers)
Make partial compliance MEASURABLE as T1-channel ineffectiveness:
breakdown.pendingT1) instate.nudge.lastT1FirePending(consume-once).applyCompression, realizedtokensCompressedis compared against it: a distillation fold (new block tier ≥ 2) clears the stall unconditionally — progress on the higher tiers by definition; otherwise a T1-shaped fold harvesting less thanSTALL_HARVEST_RATIO(0.5) of the offered mass latchesstate.nudge.t1HarvestStall, at/above ratio clears it. No-op calls are not evidence and leave the armed measurement in place.decideNudgereads the flag only whentiers.enabled:> t1Effdemand drops for this path only — the stall flag IS the evidence the lower channel cannot deliver);max(t2,t3) >= minPressureBenefit→ T1 is removed from candidates so max-pending picks the tier that actually delivers; below the floor the drop would suppress the whole nudge, so legacy behavior wins;[T1 harvest stall]for observability.Untouched by design: flat 50K growth cadence (KDD #8), the #379 mass-as-demand philosophy (the stall is consulted only once a higher tier's mass leg passed its own threshold — mass remains the need signal), #194 first-sight re-arm, the
minPressureBenefitgate, and reason-string formats outside the appended marker. Eager lanes (harvest ≥ 50%) never latch, so their behavior is unchanged.How A and B compose: the stall override sits ABOVE the #509 count-ready pool — explicit count triggers keep working independently of the flag (pinned), and per-tier cadence applies to the redirected slot exactly as before (pinned). Default triggers (1000/2000) leave the pool empty, so on stock config only B can redirect, and only after measured evidence.
Intentional behavior change (old → new)
tier2Trigger/tier3Trigger, met, while t1Eff ≥ T1 thresholdminPressureBenefitWhy: in both shapes the arbitration consumed "big pending" as "deliverable", and T1's pending is structurally big exactly when it is NOT deliverable. A makes the explicit count demand reachable; B makes the implicit mass demand reachable once evidence shows T1 cannot serve it.
Accompanying doc fix (separate labeled commit)
TierConfigJSDoc documented "Default 5" / "Default 10"; actual defaults since #379 are 1000/2000 (kernel/src/config.ts:8). Fixed, plus README nudge section documents the rotation semantics. Same mechanism domain (#379/#509 count-path semantics); fixed in passing per the 小问题直接修 policy.Verification (head 6cbffcd, base current master 0aace2f)
npm --prefix kernel test: 1591 pass / 0 fail, including 9 new harvest-stall rows: core latch→slot handoff, full-compliance never latches, distillation clears (even when the armed measurement was already consumed), legacy absent-flag byte-identity, pressure drop AND keep-T1-below-floor, cadence respect, no-op-not-evidence, count-trigger independence from the flag.kernel/src/{compress,types,state}.tsmakes 7/9 stall tests fail (the 2 passing rows pin unchanged behavior by design). Earlier red-check for A: 5/5 rotation tests fail pre-fix.fcf1e080dstores the harvest-stall flag absent-only (a clear DELETES the key instead of storing false) and6cbffcddedrops the feat: add pi-package keyword so pi.dev gallery indexes billion-context (clean, un-bundled) #509lastInjectedTier: nullinitializer (its sole reader already normalizes via?? null) — otherwise re-hydrated legacy sessions would pick up default-valued nudge keys and drift the storage-render / storage-corpus digest pins. Verified locally: storage-corpus 9/9, kernel suite 1591/1591.npm run typecheckclean +npm run buildgreen on this head; targeted bili suites (kernel-tier-defaults,compress-recovery-ranges,compress-success-tail, storage-corpus golden consumers) green locally. Full bili suite/e2e left to CI (local-testing discipline). No wire/golden changes.Notes
tierThresholds(拆分设置t1 t2 t3 nudge大小 #2376). Upstream release v0.1.82 #510 stays open there; this repo is the home now (acp-kernel 并入billion-context并保持相对独立 #2092).acp-kernel0.0.180 → 0.0.181 (CI-enforced discipline; lockfile synced).kernel/+ nudge arbitration invariants (§7.4 auto-merge forbidden).