plan: open M105 rank authority alignment
This commit is contained in:
@@ -0,0 +1,84 @@
|
||||
# M105 · Rank Authority Alignment
|
||||
|
||||
## Player-visible stopping point
|
||||
|
||||
The formal M80/entry battle simulation receives enemy rank from the gameplay
|
||||
authority in `docs/02_GAMEPLAY_AND_BALANCE.md` §4.1 and §8.1:
|
||||
|
||||
```text
|
||||
offer_level(R) = min(10, 1 + floor((R - 1) / 3))
|
||||
encounter_rank = min(6, offer_level + Q + (boss ? 1 : 0))
|
||||
rank_multiplier = 1 + 0.08 * (encounter_rank - 1)
|
||||
```
|
||||
|
||||
Rank is applied once to the authored enemy base budget. The old ladder-level
|
||||
plus permanent region-step proxy remains available only as historical evidence;
|
||||
it is not a second production authority. The player-visible stopping point is
|
||||
one deterministic focused proof plus first-cycle regression evidence showing
|
||||
that the formal entry route uses the same rank context at every region.
|
||||
|
||||
## Authority decision
|
||||
|
||||
- On 2026-09-20 the Owner replied “好” to the recommended choice A: §8.1
|
||||
`offer_level + risk` is the formal rank authority.
|
||||
- `docs/02_GAMEPLAY_AND_BALANCE.md` has priority over historical M80 proxy
|
||||
calibration notes.
|
||||
- M104 evidence remains historical and is not silently reinterpreted as a
|
||||
production balance decision.
|
||||
|
||||
## Ordered steps
|
||||
|
||||
### P1 · Authoring contract and focused proof — IN_PROGRESS
|
||||
|
||||
- Add one explicit rank-context boundary at enemy authoring.
|
||||
- Remove hidden permanent region-step scaling from the formal path.
|
||||
- Preserve class identity and the existing ordinary/elite/boss base budgets.
|
||||
- Add a focused deterministic marker covering R1/R12, risk 0/2, all classes,
|
||||
and the negative region-only-scaling assertion.
|
||||
|
||||
Acceptance: the focused source-bound attempt passes with one marker, strict
|
||||
diagnostics empty, and exact expected rank/stat values.
|
||||
|
||||
### P2 · Runtime bridge and probe integration — PENDING
|
||||
|
||||
- Pass `market_index` and `risk` from the committed battle snapshot through
|
||||
`battle_service.gd` into `battle_sim_bridge.gd`.
|
||||
- Update M61/M80 probes to use the same context by default; retain any legacy
|
||||
level model only behind an explicit historical switch.
|
||||
- Do not change encounter counts, class schedules, economy, content, or UI.
|
||||
|
||||
### P3 · First-cycle regression and handoff — PENDING
|
||||
|
||||
- Re-run focused bridge/class coverage and the M60 first-cycle route.
|
||||
- Compare committed battle/replay hashes and diagnostics with the pre-M105
|
||||
baseline.
|
||||
- Record the owner gate as still open; this package does not claim MVP ready.
|
||||
|
||||
## Frozen scope
|
||||
|
||||
Enemy counts, elite scheduling, region mechanics, economy, XP, equipment,
|
||||
content catalogs, Save semantics, UI/art/audio, P10.0 wave semantics, and all
|
||||
owner comprehension/listening/feel gates remain frozen. Packaging and release
|
||||
are out of scope.
|
||||
|
||||
## Verification and evidence
|
||||
|
||||
Every formal command runs through `tools/run_test_attempt.py` with an owned
|
||||
source/HOME/cache/TMP/browser root and `--require-marker`. Retain the compact
|
||||
attempt directory and append the marker, source commit, terminal, and strict
|
||||
diagnostics to `docs/EVIDENCE_LEDGER.md` before advancing a step.
|
||||
|
||||
## Issue register
|
||||
|
||||
- M105-I01: M104 found that the old proxy passed ladder level plus region
|
||||
pressure, while §8.1 expects `offer_level + risk`; this is the P1 boundary.
|
||||
- M105-I02: the entry bridge currently has class metadata but not rank context;
|
||||
P2 must carry the committed snapshot fields without changing the snapshot.
|
||||
- M105-I03: owner playtest, listening, comprehension, duplicate portrait, and
|
||||
visual-feel gates remain open after the technical proof.
|
||||
|
||||
## Handoff
|
||||
|
||||
At the stopping point, commit the narrow package, update
|
||||
`CURRENT_CHECKPOINT.md`, `.agent-taskgraph/STATUS.md`, and the evidence ledger,
|
||||
then stop for the next owner/product decision or a new plan.
|
||||
@@ -2,7 +2,11 @@
|
||||
|
||||
日期:2026-09-20
|
||||
决策对象:是否把 M80 代理暴露出的后段墙转成正式战斗难度改动
|
||||
当前结论:**暂不改正式曲线;先解决敌方 rank 公式的权威冲突,再校准队伍形状。**
|
||||
当前结论:**不改正式曲线;Owner 已选择 §8.1 `offer_level + risk` 作为正式 rank 权威,进入 M105 对齐实现。**
|
||||
|
||||
Owner 决策记录(2026-09-20):对推荐选项 A 的“好”按项目上下文解释为
|
||||
采用 `docs/02_GAMEPLAY_AND_BALANCE.md` §4.1/§8.1。M104 的代理结果保留为
|
||||
历史诊断;M105 先修复 authoring/bridge 的权威边界,再决定是否需要经济形状实验。
|
||||
|
||||
## 这份 memo 要做的唯一决策
|
||||
|
||||
@@ -38,7 +42,7 @@
|
||||
| A. 直接降低全局等级/区域倍率 | **拒绝** | 已经出现高区过软、R3 仍为 0 的组合;会破坏区域压力与机制身份。 |
|
||||
| B. 现在就写分段曲线 | **暂缓** | 方向可能正确,但 F3 的代理输入尚未符合经济权威,决策证据不干净。 |
|
||||
| C. 先做经济形状代理,再决定曲线 | **后置** | 可逆、只改探针;但必须先确认敌方公式不是另一套历史模型。 |
|
||||
| D. 先做权威公式对照审计 | **现在执行** | F6 可能是最早失败边界;若不先确认实现应服从哪套公式,经济代理和曲线实验都会在错误的敌方压力上运行。 |
|
||||
| D. 先做权威公式对照审计 | **已完成** | F6 是最早失败边界;审计后 Owner 选择 §8.1,进入 M105 对齐实现。 |
|
||||
|
||||
## 下一次实验契约
|
||||
|
||||
@@ -46,7 +50,9 @@
|
||||
|
||||
实验顺序必须先完成 D,再进行 C。D 已完成:72 个区域×回合×风险格全部出现公式差异,marker 为 `ABG_M104_RANK_AUTHORITY_AUDIT_OK`,且 `production_unchanged=true`。这证明当前 M80 authoring 不是可以继续盲调的产品权威,而是需要单独决策的历史/中间模型;在该决策前不再运行经济形状或分段曲线实验。
|
||||
|
||||
如果 Owner/产品权威确认 §8.1 是正式规则,则必须先开一个新的窄计划,将 `battle_stat_authoring.gd`、正式桥和 M80 探针统一到 `offer_level + risk`,并保留首轮 P10.0 回归。若确认 M80 的区域纵向模型才是正式规则,则必须反向更新 `docs/02` 和相应验收公式,再重新定义 40–70% 目标。当前 M104 不替任何一方做这个决策。
|
||||
Owner 已确认 §8.1;M105 已开为新的窄计划,先将 `battle_stat_authoring.gd`、正式桥和
|
||||
M80 探针统一到 `offer_level + risk`,并保留首轮 P10.0 回归。M80 的区域纵向模型
|
||||
仅作为历史探针证据,不再作为生产权威,也不反向改写 `docs/02`。
|
||||
|
||||
经济形状代理(在 D 通过后)至少要记录并固定:
|
||||
|
||||
@@ -70,4 +76,4 @@
|
||||
|
||||
## 最短下一步
|
||||
|
||||
**由 Owner/产品权威选择 §8.1 还是 M80 区域纵向模型;在选择和新计划建立前,不提交任何正式难度数值。**
|
||||
**完成 M105 的 authoring focused proof,再进入桥接和探针整合;在此之前不提交任何正式难度数值。**
|
||||
|
||||
Reference in New Issue
Block a user