Skip to content

分步录入向导(wizard/steps)要不要成为一等作者面?假教材已删,需求本体待裁 #13342

New issue
New issue
Closed
3 of 3 issues completed
Closed
分步录入向导(wizard/steps)要不要成为一等作者面?假教材已删,需求本体待裁#13342
3 of 3 issues completed
Labels
domain:specDomain lane — seat card indexed by label:pm:seatpm:queueReady for the PM dispatch loop

Description

@claude
claude
bot
opened on Aug 30, 2026

作者想做一个分步的录入向导——第一步填基本信息、第二步填明细、最后确认提交——平台今天没有任何一层能表达它,而文档曾经教的写法全部是平台拒收的假形。

背景

layout-dsl.mdx 曾在两节教 steps: 分步写法(Wizard Template、Multi-Step Wizard)。#13266 实测:steps 在任何一层 schema 都不存在,两节已随 PR #13337 删除/替换,门禁(#13086 的 os:check-yaml)现在钉住该页只教真形。删的是假教材;需求本体(要不要有向导)从未裁过,本卡裁它。

前提(带 re-check 命令)

# steps 不是任何 UI schema 的可作者键(0 命中即前提成立)
git grep -n "steps" packages/spec/src/ui/view.zod.ts packages/spec/src/ui/page.zod.ts

最近的两个已声明形:tabbed form view(能分页,但无进度模型、无「上一步必须过校验才能进下一步」的闸)、flow(自动化流程,不是录入 UI)。

具体问题

分步录入向导要不要成为平台的一等作者面?

选项 × 真实代价

选项 做什么 真实代价(客户可感知)
A — 声明并实现向导表单 新的一等 view 形:步序、进度条、每步校验闸 真实组件工作量;做半截(声明了但渲染骨架)会重演「校验全绿、页面是脚手架」——本板已裁过这是最贵失败形
B — 官方近似 = tabbed form view 不新增声明,文档教「用标签页表达分步」 客户能分页填,但不能强制走完第一步才见第二步;「向导感」(进度、防跳步)缺失
C — defer,记录在案 现状:假教材已删,门禁已闭合,不声明不实现 作者搜不到官方答案;需求若真实存在会以工单形式回来

业务直译:A = 像 Salesforce Screen Flow / Typeform 那样的分步表单;B = 「分页可以,防跳步不行」;C = 「这个面暂时没有,别用没有的词」。

<!-- os-decision-facets -->

轴 读数
① 项目长远合理性 向导若做,应作为 view 的一等形一次做全(进度+步进校验),⛔ 不页面层拼装出第二套半吊子;新 surface 是永久契约义务
② 实际业务拉动 今天没有实测的作者或客户在要它——唯一出处是已删除的假教材;零拉动默认 defer
③ 防 AI 犯错 最贵的失败形(AI 照教材写、校验绿、渲染骨架)已被 #13337+#13086 闭合;A 若声明而缓实现会重开该通道
④ 创业阶段不扩散 C 零成本;B 一页文档;A 真实组件工作量——defer 优于 declare-and-maintain

推荐:C(defer,记录在案;真实客户需求出现时回炉按 A 走契约先行分解);回退:B(一页文档教 tabbed 近似,零声明)。
置信缺口:本分析看不见客户/hotcrm 侧是否已有真实分步录入需求(语料未扫),也看不见 flow 引擎的产品路线图——若 flow 已计划长出录入步,A/B 都该并入它。

裁后执行段(裁后我会怎么执行,你不用管)

相关单与 PR

出处:#13266(escalation ①)、PR #13337(删假教材)、#13086/PR #13267(门禁机制)。

Generated by Claude Code

Activity

  1. claude
    added
    needs-user-decisionBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PR
    domain:specDomain lane — seat card indexed by label:pm:seat
    on Aug 30, 2026

  2. zhuangjianguo commented on Aug 30, 2026

    @zhuangjianguo
    zhuangjianguo
    on Aug 30, 2026 – with Claude
    Collaborator

    ⚖️ RULED — 维护者,2026-08-30,第 5 场总监席决裁批 #6,verbatim「13342 A」

    裁定:采选项 A —— 分步录入向导(wizard)成为平台一等作者面:新的一等 view 形,带步序、进度模型、「上一步过校验才能进下一步」的闸。⛔ 不采 B(tabbed 近似教材)、不采 C(defer)。

    执行形状(照卡面裁后执行段 + #12183 先例,契约先行分解;本卡转为 Feature 父单/协调节点):

    1. spec 形先行(domain:spec 席):设计 wizard view 的一等 schema 形(步序 / 进度 / 每步校验闸的键与语义)。⚠️ 具体契约形状定稿后回决策箱过维护者一次——方向已裁(要做),形状是公开契约新面(条款②预期 yes),⛔ 不由席位定稿即派实现。设计输入:与 tabbed form view 的分界(它能分页、无闸)、ui#6237 已裁的「拆 FormSectionConfig」(WizardForm 侧刻意无谓词槽——wizard 一等形若引入步级显隐,须与该裁决调和而非旁路)。
    2. objectui 渲染子卡随后,带 Blocked-by: 指向 spec 半;⛔ 两半永不同批。
    3. ⛔ 最贵失败形围栏(本板已裁过):声明与实现同波次落地——绝不先声明 schema 后缓实现渲染,那会重开「AI 照教材写、校验全绿、渲染骨架」通道(docs(objectui): layout-dsl teaches only shapes the live schemas accept #13337+[finding] YAML doc fences are validated by nothing — check:skill-examples reads only ts/tsx fences, and only opt-in, so every metadata example in content/docs/** is unverifiable by construction #13086 刚关掉的正是它);文档教材只在两半都落地后回写。
    4. 假教材已删(PR docs(objectui): layout-dsl teaches only shapes the live schemas accept #13337)、门禁已钉([finding] YAML doc fences are validated by nothing — check:skill-examples reads only ts/tsx fences, and only opt-in, so every metadata example in content/docs/** is unverifiable by construction #13086)——现状保持到新形落地,⛔ 不提前写新教材。

    席位边界(裁不派):录裁 + 转 pm:queue(domain:spec,Feature 父单);type 归分诊补(预期 Feature)。同笔摘 needs-user-decision。裁决入本场追认摘要表。

    Generated by Claude Code

  3. zhuangjianguo
    added
    pm:queueReady for the PM dispatch loop
    and removed
    needs-user-decisionBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PR
    on Aug 30, 2026
  4. os-warren
    added a sub-issue on Aug 31, 2026

  5. os-warren commented on Aug 31, 2026

    @os-warren
    os-warren
    on Aug 31, 2026 – with Claude
    Collaborator

    Coordination update (domain:spec seat, session_01PBjwYLS6BciTQW3c9xQiD2): the ruled spec-half design is DELIVERED on sub-card #13622 and staged back to the decision inbox per this card's ruling (「具体契约形状定稿后回决策箱过维护者一次」). One repricing fact for this coordination node: the proposal's re-measurement found the wizard form view already exists end-to-end (spec enum member 'wizard' at view.zod.ts:2906, live WizardForm chain, the gate and progress model implemented, a real showcase author) — the ruling's direction stands, but v1 is a declaration-and-refusal TIGHTENING with zero new keys, and the future Card R (objectui half) shrinks accordingly. Next state transitions happen on #13622 (maintainer pass) → then the implementation cards are filed contract-first as ruled. This parent stays the coordination node; nothing is dispatched from it.

    Generated by Claude Code

  6. os-warren
    added sub-issues on Aug 31, 2026

  7. os-warren commented on Aug 31, 2026

    @os-warren
    os-warren
    on Aug 31, 2026 – with Claude
    Collaborator

    关卡(completed):本协调节点的两半均已落地——

    wizard 需求本体按 #13622 的裁定落定:sections 即 steps、步门为默认语义、allowSkip 为导航自由、进度为派生态、步骤键家族在 wizard 上拒绝、空 wizard 拒绝。#13337/#13086 教材围栏随两半落地解除——教学卡(rich-text/wizard 编写指南类)由后续按需另立,⛔ 不在本节点上挂。假教材已删(本卡开卡时的现场),需求本体已裁并实施。

    Generated by Claude Code

  8. os-warren
    closed this as completedon Aug 31, 2026
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

    domain:specDomain lane — seat card indexed by label:pm:seatpm:queueReady for the PM dispatch loop

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions