create-yss-spec 2.2.3 → 2.2.4

package/template/.hermes/skills/yss-tactical-design/tests/fixtures/invalid-stale-upstream-ref.yaml

@@ -0,0 +1,21 @@
+schema_version: 1
+tactical_design_id: tactical-design.invalid-stale
+tactical_version: v1
+status: ready-for-human
+context_ref: context.example
+aggregate_catalog: [{aggregate_id: aggregate.example, name: Example, context_ref: context.example, root_entity: entity.example-root, invariant_refs: [invariant.example], behavior_refs: [behavior.example], consistency_boundary: single, api_exposure: internal-only}]
+entity_catalog: [{entity_id: entity.example-root, name: Root, aggregate_id: aggregate.example, identity: id, lifecycle: active}]
+value_object_catalog: []
+behavior_catalog: [{behavior_id: behavior.example, name: Do, aggregate_id: aggregate.example, command: do, preconditions: [ready], invariant_refs: [invariant.example], postconditions: [done], event_refs: []}]
+invariant_catalog: [{invariant_id: invariant.example, aggregate_id: aggregate.example, statement: required}]
+state_transition_catalog: [{transition_id: transition.example, aggregate_id: aggregate.example, from: draft, to: done, behavior_id: behavior.example}]
+consistency_policy: {transaction_boundary: single, concurrency: optimistic, idempotency: guarded, cross_aggregate_strategy: none}
+domain_event_catalog: []
+gateway_catalog: [{gateway_id: gateway.example, name: Gateway, context_ref: context.example, layer: Domain, capabilities: [load]}]
+persistence_mapping: [{aggregate_id: aggregate.example, storage_model: example, notes: mapping}]
+test_seams: [{seam_id: test-seam.example, kind: domain, subject_ref: invariant.example, assertion: behavior}]
+adr_candidates: []
+upstream_impact: {spec_ref: spec@v1, strategic_ref: strategy@v1, api_ref: api@draft, data_ref: data@v1, upstream_current: false}
+version: v1
+digest: sha256:0000000000000000000000000000000000000000000000000000000000000000
+evidence_refs: []

package/template/.hermes/skills/yss-tactical-design/tests/fixtures/invalid-strategic-as-tactical.yaml

@@ -0,0 +1,21 @@
+schema_version: 1
+tactical_design_id: tactical-design.invalid-strategic
+tactical_version: v1
+status: ready-for-human
+context_ref: context.example
+aggregate_catalog: [{aggregate_id: aggregate.example, name: Example, context_ref: context.example, root_entity: entity.example-root, model_origin: strategic-concept, invariant_refs: [invariant.example], behavior_refs: [behavior.example], consistency_boundary: single, api_exposure: internal-only}]
+entity_catalog: [{entity_id: entity.example-root, name: Root, aggregate_id: aggregate.example, identity: id, lifecycle: active}]
+value_object_catalog: []
+behavior_catalog: [{behavior_id: behavior.example, name: Do, aggregate_id: aggregate.example, command: do, preconditions: [ready], invariant_refs: [invariant.example], postconditions: [done], event_refs: []}]
+invariant_catalog: [{invariant_id: invariant.example, aggregate_id: aggregate.example, statement: required}]
+state_transition_catalog: [{transition_id: transition.example, aggregate_id: aggregate.example, from: draft, to: done, behavior_id: behavior.example}]
+consistency_policy: {transaction_boundary: single, concurrency: optimistic, idempotency: guarded, cross_aggregate_strategy: none}
+domain_event_catalog: []
+gateway_catalog: [{gateway_id: gateway.example, name: Gateway, context_ref: context.example, layer: Domain, capabilities: [load]}]
+persistence_mapping: [{aggregate_id: aggregate.example, storage_model: example, notes: mapping}]
+test_seams: [{seam_id: test-seam.example, kind: domain, subject_ref: invariant.example, assertion: behavior}]
+adr_candidates: []
+upstream_impact: {spec_ref: spec@v1, strategic_ref: strategy@v1, api_ref: api@draft, data_ref: data@v1, upstream_current: true}
+version: v1
+digest: sha256:0000000000000000000000000000000000000000000000000000000000000000
+evidence_refs: []

package/template/.hermes/skills/yss-tactical-design/tests/fixtures/valid-tactical-design.yaml

@@ -0,0 +1,80 @@
+schema_version: 1
+tactical_design_id: tactical-design.example-feature
+tactical_version: v1
+status: ready-for-human
+context_ref: context.example
+aggregate_catalog:
+  - aggregate_id: aggregate.example
+    name: ExampleAggregate
+    context_ref: context.example
+    root_entity: entity.example-root
+    invariant_refs: [invariant.example-required]
+    behavior_refs: [behavior.example-publish]
+    consistency_boundary: single-aggregate-transaction
+    api_exposure: internal-only
+entity_catalog:
+  - entity_id: entity.example-root
+    name: ExampleRoot
+    aggregate_id: aggregate.example
+    identity: stable-id
+    lifecycle: draft-published
+value_object_catalog:
+  - value_object_id: value-object.example-code
+    name: ExampleCode
+    aggregate_id: aggregate.example
+    immutable: true
+behavior_catalog:
+  - behavior_id: behavior.example-publish
+    name: Publish
+    aggregate_id: aggregate.example
+    command: publish
+    preconditions: ["状态为 draft"]
+    invariant_refs: [invariant.example-required]
+    postconditions: ["状态变为 published"]
+    event_refs: [domain-event.example-published]
+invariant_catalog:
+  - invariant_id: invariant.example-required
+    aggregate_id: aggregate.example
+    statement: "发布前必须满足业务前置条件"
+state_transition_catalog:
+  - transition_id: transition.example-publish
+    aggregate_id: aggregate.example
+    from: draft
+    to: published
+    behavior_id: behavior.example-publish
+consistency_policy:
+  transaction_boundary: single aggregate
+  concurrency: optimistic version check
+  idempotency: repeated publish is rejected by state guard
+  cross_aggregate_strategy: domain event with retry
+domain_event_catalog:
+  - event_id: domain-event.example-published
+    name: ExamplePublished
+    aggregate_id: aggregate.example
+    consumers: [downstream-context]
+    delivery: outbox-at-least-once
+gateway_catalog:
+  - gateway_id: gateway.example
+    name: ExampleGateway
+    context_ref: context.example
+    layer: Domain
+    capabilities: [save aggregate, load aggregate]
+persistence_mapping:
+  - aggregate_id: aggregate.example
+    storage_model: example_aggregate_snapshot
+    notes: "持久化结构不泄漏到领域模型"
+test_seams:
+  - seam_id: test-seam.example-invariant
+    kind: domain-behavior
+    subject_ref: invariant.example-required
+    assertion: "不满足前置条件时 publish 失败"
+adr_candidates: []
+upstream_impact:
+  spec_ref: docs/.scratch/example/spec.yaml@v1
+  strategic_ref: docs/.scratch/example/domain-strategy.yaml@v1
+  api_ref: docs/.scratch/example/openapi.yaml@draft
+  data_ref: docs/.scratch/example/data-architecture.md@v1
+  upstream_current: true
+version: v1
+digest: sha256:0000000000000000000000000000000000000000000000000000000000000000
+evidence_refs: [docs/.scratch/example/tactical-review.yaml]

package/template/.hermes/skills/yss-tactical-design/tests/run-scenarios.mjs

@@ -0,0 +1,47 @@
+#!/usr/bin/env node
+import { mkdtemp, readFile, rm, writeFile } from "node:fs/promises";
+import { dirname, join } from "node:path";
+import { fileURLToPath } from "node:url";
+import { spawnSync } from "node:child_process";
+import { tmpdir } from "node:os";
+
+const root = dirname(fileURLToPath(import.meta.url));
+const validator = join(root, "..", "scripts", "validate-tactical-design.mjs");
+const fixture = (name) => join(root, "fixtures", name);
+const run = (file) => spawnSync(process.execPath, [validator, file], { encoding: "utf8" });
+const pass = run(fixture("valid-tactical-design.yaml"));
+if (pass.status !== 0) throw new Error(`valid tactical design should pass: ${pass.stderr}`);
+
+const blockedCases = [
+  ["invalid-missing-invariant.yaml", "invariant_refs 必须是至少 1 项的数组"],
+  ["invalid-api-leaks-aggregate.yaml", "api_exposure 必须为 internal-only"],
+  ["invalid-stale-upstream-ref.yaml", "status 必须为 stale"],
+  ["invalid-strategic-as-tactical.yaml", "不得直接把战略概念当作 Aggregate"],
+  ["invalid-missing-consistency-policy.yaml", "consistency_policy.transaction_boundary 缺失"]
+];
+for (const [name, message] of blockedCases) {
+  const result = run(fixture(name));
+  if (result.status === 0 || !result.stderr.includes(message)) throw new Error(`${name} should be blocked: ${result.stderr}`);
+}
+
+const temporaryRoot = await mkdtemp(join(tmpdir(), "yss-tactical-design-pressure-"));
+try {
+  const source = await readFile(fixture("valid-tactical-design.yaml"), "utf8");
+  const escalated = join(temporaryRoot, "missing-standalone-ref.yaml");
+  await writeFile(escalated, `${source}\ncomplexity:\n  escalate_to_standalone: true\n`);
+  const result = run(escalated);
+  if (result.status === 0 || !result.stderr.includes("standalone_ref")) throw new Error("complexity escalation without standalone_ref should be blocked");
+
+  const wrongGateway = join(temporaryRoot, "wrong-gateway-layer.yaml");
+  await writeFile(wrongGateway, source.replace("layer: Domain", "layer: Infrastructure"));
+  const gatewayResult = run(wrongGateway);
+  if (gatewayResult.status === 0 || !gatewayResult.stderr.includes("layer 必须为 Domain")) throw new Error("Infrastructure gateway should be blocked");
+
+  const crossAggregateRoot = join(temporaryRoot, "cross-aggregate-root.yaml");
+  await writeFile(crossAggregateRoot, source.replace("aggregate_id: aggregate.example\n    identity", "aggregate_id: aggregate.other\n    identity"));
+  const crossAggregateResult = run(crossAggregateRoot);
+  if (crossAggregateResult.status === 0 || !crossAggregateResult.stderr.includes("root_entity 的 aggregate_id 必须与当前 Aggregate 一致")) throw new Error("cross-aggregate root should be blocked");
+} finally {
+  await rm(temporaryRoot, { recursive: true, force: true });
+}
+process.stdout.write("DDD tactical design scenarios passed\n");

package/template/.pi/skills/yss-domain/SKILL.md

@@ -5,7 +5,7 @@ description: 用于构建或重构 YSS 领域层代码。当用户要求设计
 
 # yss-domain
 
-这是一个建模型 skill。核心目标是先把领域语义和边界建立清楚，再落代码。
+这是一个领域实现 skill。核心目标是消费已批准的战术模型，将领域行为落实为代码；战术模型的设计与批准由 `yss-tactical-design` 和 `yss-product-lifecycle` 负责。
 
 默认输出是新 DDD target profile；现有 YSS 组件仓库常见 `core/client/repository`、贫血对象和 VO 型 Gateway 只是 legacy profile，不得静默复制成新模块架构。
 
@@ -23,10 +23,10 @@ description: 用于构建或重构 YSS 领域层代码。当用户要求设计
 
 ## 工作方式
 
-1. 先抽业务术语、聚合边界和状态变化。
+1. 先读取批准且版本当前的 tactical-design contract 和 Slice Implementation Contract。
 2. 数据库字段只做补充，不直接决定领域对象结构。
-3. 先定义领域行为，再决定 Gateway 边界。
-4. 规则不清晰时，保留显式假设，不要静默猜测。
+3. 按合同实现领域行为、状态机、不变量和 Gateway 边界。
+4. 规则不清晰或模型需要扩展时，返回 `new_impacts` / `drift` 并停止，不要静默猜测。
 
 ## 产物范围
 
@@ -63,6 +63,7 @@ description: 用于构建或重构 YSS 领域层代码。当用户要求设计
 ## 阶段 7 合同
 
 - 只消费生命周期已批准的 `Slice Implementation Contract` 和当前 `work_unit`；不得扩大 `allowed_write_paths`。
+- `Slice Implementation Contract` 必须引用批准且版本当前的 `tactical_design_ref`；不得在实现阶段重新批准或替换聚合、不变量和一致性策略。
 - 领域规则、状态机和不变量必须使用 `behavior-tdd`，先形成失败测试，再实现最小行为。
 - 完成后按 `yss-router/references/yss-skill-execution-result.md` 返回统一 `YSS Skill Execution Result`：changed files、领域/测试证据、实际验证结果、偏离和新增影响。
 - 发现新 API、权限、状态机、数据模型或架构影响时填入 `new_impacts` 并暂停，不得静默扩张切片。

package/template/.pi/skills/yss-product-lifecycle/SKILL.md

@@ -27,12 +27,12 @@ Matt 的 `grill-with-docs`、`to-spec`、`to-tickets`、`implement` 等保留为
 | 阶段 | 必需产物/门禁 | 工作单元与技能 | 通过条件 |
 |---|---|---|---|
 | 入口分诊 | 身份、影响面、最近可信阶段 | `yss-product-lifecycle` | `yss-project.yaml` 合法且影响面可解释 |
-| 机会调研/需求分析 | Discovery、用户/MVP/非目标/成功标准、测试 seam | `work-unit.discovery-opportunity` + `work-unit.discovery-requirements`；市场/竞品事实用 `competitive-intelligence`，技术/标准事实用 `research`；`grill-with-docs` 为兼容入口 | 未决事实已 research 或 handoff，用户确认，无 runnable blocker |
+| 机会调研/需求分析 | Discovery、用户/MVP/非目标/成功标准、测试 seam；命中 DDD 影响时补充领域战略设计与阶段决策包 | `work-unit.discovery-opportunity` + `work-unit.discovery-requirements` + `work-unit.domain-strategy-design` + `work-unit.stage-decision`；市场/竞品事实用 `competitive-intelligence`，技术/标准事实用 `research`；领域建模用 `domain-modeling`；`grill-with-docs` 为兼容入口 | 未决事实已 research 或 handoff，领域边界和统一语言可审查，阶段决策包完成必要批准 |
 | Spec/功能架构 | Spec、产品总体设计、功能架构；必要时 Spec Delta | 原生 `work-unit.spec-synthesis`；`to-spec` 为兼容入口 | 初稿先为 `ready-for-human`；只有 Spec baseline 会签批准后资产才为 `approved` 并进入下游 |
 | 原型设计 | 交互说明、低保真、状态矩阵、高保真 HTML、评审记录 | `yss-design-system` → `yss-prototype-stage` → `yss-antd-design`（仅原型事实）→ Codex `product-design:index`（非 Codex 交付等价合同）。前端落地改用 `yss-ui` | `gate.prototype-reviewed`、`gate.prototype-verified`、`gate.user-confirmation` 均有证据 |
-| 技术分析 | OpenAPI Draft/Freeze、数据架构、工程基线、架构审查 | `yss-openapi-governance` / `yss-openapi-draft-review`、`codebase-design`、`implementation-repo-onboarding`、`yss-router` | API/架构契约冻结；无 API 影响有明确记录；脚手架策略满足 |
+| 技术分析 | OpenAPI Draft/Freeze、数据架构、工程基线、架构审查；按领域影响执行 Tactical DDD Check | `yss-openapi-governance` / `yss-openapi-draft-review`、`codebase-design`、`implementation-repo-onboarding`、`yss-tactical-design`、`yss-router` | API/架构契约冻结；无 API 影响有明确记录；战术模型无未解释冲突；脚手架策略满足 |
 | Ticket 正式化 | 功能父 Ticket、垂直切片、Slice Implementation Contract | 原生 `work-unit.ticket-decomposition`；`to-tickets` 为兼容入口；生命周期复算 | 依赖、验收、测试 seam 可执行；合同已批准、持久化且为当前版本 |
-| 技术实现 | 前端/后端代码、TDD 证据、YSS Skill Execution Result | 原生 `work-unit.slice-implementation`；`implement` 为兼容入口；前端按 `yss-ui` + `yss-page-module-development`，后端按 `yss-router` 最小闭包，业务行为统一 `tdd` | 只写允许路径；业务行为用 `behavior-tdd`；UI 影响必须有还原计划 |
+| 技术实现 | 前端/后端代码、TDD 证据、YSS Skill Execution Result | 原生 `work-unit.slice-implementation`；`implement` 为兼容入口；前端按 `yss-ui` + `yss-page-module-development`，后端按 `yss-router` 最小闭包，业务行为统一 `tdd` | 仅接收已完成 Ticket 正式化、已绑定垂直切片且 `ready-for-agent` 公式通过的输入；只写允许路径；业务行为用 `behavior-tdd`；UI 影响必须有还原计划 |
 | Review/验证 | 不可变候选快照、review 结论、fresh verification | `code-review`（独立于实现者）；UI 影响追加 `yss-ui` + `yss-design-system` 的 UI fidelity 轴 | findings 已处理；同一候选快照通过全部审查轴与验证 |
 | 发布/复盘 | 发布/回滚证据、复盘记录 | 生命周期自有工作单元 | fresh verification、独立审查和发布裁决齐全；`gate.release-ready` 仍须生物人 |
 
@@ -42,8 +42,8 @@ Matt 的 `grill-with-docs`、`to-spec`、`to-tickets`、`implement` 等保留为
 
 ## 结果与暂停
 
-每个工作单元必须返回 `Workflow Execution Result`（workflow reference、skill、changed files、evidence refs、actual verification、deferred seams、drift/new impacts）。缺少可读证据、`stale`、`violation`、`drift`、`new_impacts` 或阻塞信号时不得标记 completed。实现授权不包含 Git commit/push 授权；“做完提交”等自然语言意向不构成上述结构化 Git 授权。
+凡主控向数字人角色或独立运行时正式派发生命周期工作单元，都必须通过结构化任务包派发，并返回 `Workflow Execution Result`（workflow reference、skill、changed files、evidence refs、actual verification、deferred seams、drift/new impacts）。任务包使用 `docs/process/schemas/digital-human-task-package.schema.json`，由 `scripts/verify-digital-human-task-package` 校验；其中 `role_id`、`runtime_id`、`execution_state`、`contract.kind/id/version`、允许写路径、预期证据和汇合引用必须完整。`slice-implementation` 任务包额外绑定批准且当前版本的 Slice Implementation Contract；Discovery、Spec、原型、技术分析、Ticket、Review、发布和模板维护分别绑定各自的生命周期资产或维护 checkpoint，不得伪造 Slice Contract。缺少可读证据、`stale`、`violation`、`drift`、`new_impacts` 或阻塞信号时不得标记 completed。实现授权不包含 Git commit/push 授权；“做完提交”等自然语言意向不构成上述结构化 Git 授权。
 
-输出固定包含：模式、当前阶段、影响面、资产/门禁状态、证据、阻塞项、本轮动作、下一工作单元、暂停/继续理由、Ticket 同步和 Git checkpoint 判断。暂停会签时必须输出门禁 ID、指定 `role_id`、`runtime_id` 和会签文件路径（`docs/.scratch/<feature>/gates/<gate-id>-approval.yaml`）。恢复前运行 `scripts/verify-approval-record`；错误会签记为 `blocked`，不得把该门禁标为 `approved`。任务包的 `core_skills` / `forbidden_skills` 必须从 `docs/agents/digital-human-roles.yaml` 复制（`taskPackageDefaults`），禁止手写第二套。
+输出固定包含：模式、当前阶段、影响面、资产/门禁状态、证据、Ticket 正式化状态、垂直切片引用、`ready-for-agent` 计算结果、阻塞项、本轮动作、下一工作单元、暂停/继续理由、Ticket 同步和 Git checkpoint 判断。原生路径未出现 `to-tickets` / `implement` 名称本身不构成异常；但没有完成 `work-unit.ticket-decomposition`、垂直切片仍为 `ready-for-human`、引用父 Ticket 或 `next_route` 越过 Ticket 正式化时必须返回 `blocked`。暂停会签时必须输出门禁 ID、指定 `role_id`、`runtime_id` 和会签文件路径（`docs/.scratch/<feature>/gates/<gate-id>-approval.yaml`）。恢复前运行 `scripts/verify-approval-record`；错误会签记为 `blocked`，不得把该门禁标为 `approved`。任务包的 `core_skills` / `forbidden_skills` 必须从 `docs/agents/digital-human-roles.yaml` 复制（`taskPackageDefaults`），禁止手写第二套。
 
 详细执行循环、readiness、脚手架（包括 `controlled-generation`）、审查快照、状态传播和 Matt 边界见 [orchestration.md](references/orchestration.md)、[orchestration-contract.yaml](references/orchestration-contract.yaml)、[artifact-dependencies.md](references/artifact-dependencies.md) 和 [state-model.md](references/state-model.md)。

package/template/.pi/skills/yss-product-lifecycle/references/artifact-dependencies.md

@@ -7,6 +7,8 @@ Discovery → Spec → Product Overview / Functional Architecture
 Spec + Product Overview → Product Design / Requirement Freeze
 Spec + Product Overview → API Impact / OpenAPI Draft
 Spec + Product Overview → System / Data Architecture
+System / Data Architecture + domain impact → Tactical DDD Check / tactical-design contract
+Tactical DDD contract → Architecture Review / Engineering Baseline / Slice Implementation Contract
 API impact = yes: Requirement Freeze + Design Review + Draft Review → OpenAPI Freeze
 API impact = no: API Impact Assessment approved → No-API-Impact record；Draft/Freeze gates = not-applicable
 Frozen Contract → Vertical Slice Tickets
@@ -30,3 +32,5 @@ Implementation → Independent Review → Fresh Verification → Release
 明确写入需求的认证、授权、租户隔离、敏感数据或合规行为变化不使用独立影响类型；按它实际改变的 UI 状态、API schema、状态机、数据模型或服务边界传播。普通 action 注册、SQL / DDL / 迁移和上传 / 下载只使用既有技术影响类型，不增加安全 / 权限传播。
 
 OpenAPI Freeze 后发生上游变化时，不得仅因父 Ticket 仍写阶段 6 就继续实现。先做影响分析，再精准更新相关资产和门禁。
+
+战术设计合同上游引用发生版本变化时，先将 tactical-design 标记为 `stale`，再传播到 Slice Contract；发现新的聚合、状态、不变量、一致性或 Gateway 影响时标记 `drift` / `new_impacts` 并重新路由。

package/template/.pi/skills/yss-product-lifecycle/references/matt-yss-adapter.md

@@ -69,8 +69,8 @@ Router 状态映射为：`draft → completed`、`blocked → blocked`、`ready-
 | Matt flow | 进入条件 | 生命周期结果 |
 |---|---|---|
 | `to-spec`（用户显式） | Discovery work unit 或 `grill-with-docs` 已满足退出条件，且不存在未回流 runnable blocker；用户问题、MVP/非目标、成功标准、测试 seam 和术语审查均有证据 | 生命周期只准备/验收；Spec 初稿为 `ready-for-human`，不等于批准 |
-| `to-tickets`（用户显式） | OpenAPI Freeze 或 `no-api-impact` 记录、必要门禁、垂直切片范围和阻塞边均已明确 | 生命周期只准备/验收；只能生成垂直切片 Ticket，初始统一为 `ready-for-human` |
-| `implement`（用户显式） | `ready-for-agent` 公式、Contract 已批准/持久化/版本一致、Build Architecture Checklist、实现仓库/分支/CI/验证命令/回滚点，以及后端 Contract（适用时）均满足 | 生命周期只准备/验收；单会话实现同样适用，不得绕过门禁 |
+| `to-tickets`（用户显式） | OpenAPI Freeze 或 `no-api-impact` 记录、必要门禁、垂直切片范围和阻塞边均已明确 | 生命周期只准备/验收；只能生成垂直切片 Ticket，初始统一为 `ready-for-human`；必须留下 `ticket_decomposition_result_ref` 和 `vertical_slice_ticket_ref` |
+| `implement`（用户显式） | `ready-for-agent` 公式、Ticket 正式化结果、垂直切片引用/类型/状态、Contract 已批准/持久化/版本一致、Build Architecture Checklist、实现仓库/分支/CI/验证命令/回滚点，以及后端 Contract（适用时）均满足 | 生命周期只准备/验收；单会话实现同样适用，不得绕过门禁；父 Ticket、`ready-for-human` 切片或跳过 Ticket 正式化的 `next_route` 必须 `blocked` |
 
 `grill_exit` 不是“已经聊过”的自然语言声明。它必须同时证明 frontier 为空、事实已解决或分别路由到 `research` / prototype / external input、用户决策已确认、双方共同理解已确认，并且没有未回流的 runnable blocker。
 

package/template/.pi/skills/yss-product-lifecycle/references/orchestration-contract.yaml

@@ -100,6 +100,71 @@ workflow_execution_result:
   workflow_reference:
     required: [source, skill, invocation_mode]
     allowed_sources: [yss-product-lifecycle, mattpocock/skills]
+  next_route:
+    validator: scripts/lib/lifecycle-transition.mjs
+    function: validateNextRoute
+    implementation_predecessor: work-unit.ticket-decomposition
+    null_allowed_when: [blocked, needs-human, failed, terminal_completed]
+  work_unit_requirements:
+    work-unit.ticket-decomposition:
+      completed_requires: [vertical_slice_ticket_ref, ticket_decomposition_result_ref]
+    work-unit.slice-implementation:
+      required: [predecessor_work_unit, ticket_decomposition_result_ref, ticket_decomposition_result_status, vertical_slice_ticket_ref, vertical_slice_ticket_role, vertical_slice_ticket_kind, slice_contract_ticket_ref, slice_contract_status]
+      boolean_required: [ready_for_agent, slice_contract_persisted, slice_contract_current_version]
+      validator: scripts/lib/lifecycle-transition.mjs
+      function: validateImplementationEntry
+
+task_package:
+  schema_version: 1
+  applies_to: all-formal-digital-human-dispatches
+  schema_ref: docs/process/schemas/digital-human-task-package.schema.json
+  compatibility_schema_ref: docs/process/schemas/subagent-task-package.schema.json
+  validator: scripts/verify-digital-human-task-package
+  compatibility_validator: scripts/verify-subagent-task-package
+  persistence_layout: docs/.scratch/<feature>/task-packages/<task-id>.yaml
+  required: [schema_version, task_id, work_unit_id, actor_id, role_id, runtime_id, execution_state, workflow_status, skill_source, contract, inputs, objective, allowed_write_paths, forbidden_actions, expected_outputs, expected_evidence_files, verification_commands, verification_results, downstream_consumers, convergence]
+  execution_states: [Explorer, Drafter, Worker, Reviewer, Verifier]
+  workflow_statuses: [not-started, active, paused, resolved, failed]
+  skill_source:
+    registry_ref: docs/agents/digital-human-roles.yaml
+    defaults: taskPackageDefaults(role_id)
+    copy_required: [core_skills, forbidden_skills]
+  contract:
+    kinds: [lifecycle-work-unit, slice-implementation, template-maintenance]
+    required: [kind, contract_id, contract_version, status, contract_ref]
+    status_at_dispatch: issued
+    status_after_change: [stale, blocked]
+    lifecycle-work-unit:
+      required: [lifecycle_ref]
+      forbidden: [slice_contract_ref, maintenance_ref]
+      template_source_work_unit: forbidden
+    slice-implementation:
+      required: [slice_contract_ref]
+      must_match_current_slice_contract: true
+      version_mismatch: blocked
+      stage: stage.vertical-slice-implementation
+      parent_work_unit: work-unit.slice-implementation
+      work_unit_must_be_declared_in_slice_contract: true
+    template-maintenance:
+      required: [maintenance_ref]
+      forbidden: [slice_contract_ref, lifecycle_ref]
+  dispatch:
+    owner: role.lifecycle-orchestrator
+    mode: orchestrator-one-to-one
+    per_feature_instances: forbidden
+  write_isolation:
+    policy: task-package-policy
+    changed_files_must_be_within_allowed_paths: true
+    shared_workspace_is_not_security_boundary: true
+  downstream:
+    formal_channel: [task_package_ref, contract_ref, evidence_refs, workflow_execution_result]
+    direct_chat_is_not_formal_evidence: true
+  stale:
+    owner: yss-product-lifecycle
+    on_contract_change: [mark_downstream_stale, remove_ready-for-agent, reroute]
+  compatibility:
+    legacy_results: read-only-normalize
+    schema_version: 1
 
 # Matt user-invoked skills remain explicit user entry points. Lifecycle work units
 # may prepare, validate and accept their results, but cannot invoke them or create
@@ -146,6 +211,22 @@ work_unit_routes:
     skills: [grilling, domain-modeling]
     applies_when: requirements_or_domain_boundary_unclear
     not_applicable_reason: requirements_already_confirmed
+  work-unit.domain-strategy-design:
+    native: {source: yss-product-lifecycle, skill: yss-stage-decision, invocation_mode: model-invoked}
+    primary_skill: yss-stage-decision
+    supporting_skills: [domain-modeling, research, grilling]
+    skills: [yss-stage-decision, domain-modeling, research, grilling]
+    human_gate: domain-strategy-approved
+    applies_when: domain_boundary_or_language_or_core_rule_impact
+    not_applicable_reason: no_domain_strategy_impact
+  work-unit.stage-decision:
+    native: {source: yss-product-lifecycle, skill: yss-stage-decision, invocation_mode: model-invoked}
+    primary_skill: yss-stage-decision
+    supporting_skills: [domain-modeling]
+    skills: [yss-stage-decision, domain-modeling]
+    human_gate: stage-decision-package-approved
+    applies_when: discovery_to_spec_requires_stable_decision_package
+    not_applicable_reason: existing_approved_stage_decision_current
   work-unit.spec-synthesis:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-product-lifecycle
@@ -166,8 +247,17 @@ work_unit_routes:
   work-unit.technical-analysis:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-router
-    supporting_skills: [yss-openapi-governance, yss-openapi-draft-review, codebase-design, implementation-repo-onboarding]
-    skills: [yss-openapi-governance, yss-openapi-draft-review, codebase-design, implementation-repo-onboarding, yss-router]
+    supporting_skills: [yss-openapi-governance, yss-openapi-draft-review, codebase-design, implementation-repo-onboarding, yss-tactical-design]
+    skills: [yss-openapi-governance, yss-openapi-draft-review, codebase-design, implementation-repo-onboarding, yss-tactical-design, yss-router]
+    tactical_ddd:
+      applies_when: [aggregate-impact, state-machine-impact, invariant-impact, consistency-impact, domain-event-impact, gateway-boundary-impact, persistence-mapping-impact]
+      not_applicable_reason: no_tactical_ddd_impact
+      default_artifact: system-overview-design.tactical-ddd-check
+      standalone_artifact: artifact.tactical-design
+      review_evidence: evidence.tactical-design-review
+      statuses: [draft, ready-for-human, approved, blocked, stale, drift, new_impacts, not-applicable]
+      approved_by: yss-product-lifecycle
+      forbidden: [self-approval, ready-for-agent, production-code-generation]
     human_gate: openapi-freeze_if_api_impact
     applies_when: technical_or_contract_impact
     not_applicable_reason: no_technical_or_contract_impact
@@ -179,6 +269,7 @@ work_unit_routes:
     skills: [yss-router]
     applies_when: frozen_scope_ready_for_slicing
     not_applicable_reason: contract_or_scope_not_frozen
+    must_complete_before: work-unit.slice-implementation
   work-unit.slice-implementation:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-router
@@ -206,6 +297,7 @@ work_unit_routes:
         theme_impact: no_theme_impact
     applies_when: ready_for_agent
     not_applicable_reason: slice_contract_not_approved
+    requires_completed_work_units: [work-unit.ticket-decomposition]
   work-unit.frontend-implementation-verification:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-ui
@@ -239,9 +331,49 @@ compatibility_flow_preconditions:
     output: vertical-slice-tickets
     output_role: ready-for-human
   implement:
-    required: [ready_for_agent, slice_contract_approved, slice_contract_persisted, slice_contract_current_version, build_architecture_checklist, implementation_repo, implementation_branch, ci, verification_commands, rollback_point, backend_slice_contract_if_applicable, backend_scaffold_policy_satisfied, frontend_implementation_plan_if_ui_impact]
+    required: [ready_for_agent, predecessor_work_unit, ticket_decomposition_result_ref, ticket_decomposition_result_status, vertical_slice_ticket_ref, vertical_slice_ticket_role, vertical_slice_ticket_kind, slice_contract_approved, slice_contract_persisted, slice_contract_current_version, build_architecture_checklist, implementation_repo, implementation_branch, ci, verification_commands, rollback_point, backend_slice_contract_if_applicable, backend_scaffold_policy_satisfied, frontend_implementation_plan_if_ui_impact]
     applies_to_single_session: true
 
+ticket_formalization:
+  implementation_predecessor: work-unit.ticket-decomposition
+  result_ref_required: true
+  result_must_be: completed
+  evidence_refs_required: true
+  vertical_slice_ticket:
+    kind: vertical-slice-ticket
+    role_before_promotion: ready-for-human
+    role_for_implementation: ready-for-agent
+    local_ref_pattern: '^docs/\\.scratch/[^/]+/issues/[^/]+\\.md$'
+    parent_ticket_ref_forbidden: true
+  slice_contract_binding:
+    ticket_ref_must_equal: vertical_slice_ticket_ref
+    status: approved
+    persisted: true
+    current_version: true
+  validator:
+    module: scripts/lib/lifecycle-transition.mjs
+    functions: [validateNextRoute, validateTicketFormalization, validateImplementationEntry]
+
+transition_graph:
+  validator: scripts/lib/lifecycle-transition.mjs
+  implementation_requires_predecessor: work-unit.ticket-decomposition
+  routes:
+    work-unit.ssot-update: [work-unit.skill-projection-sync, work-unit.intensity-aware-verification]
+    work-unit.skill-projection-sync: [work-unit.template-snapshot-build, work-unit.intensity-aware-verification]
+    work-unit.template-snapshot-build: [work-unit.attach-sync-integration, work-unit.intensity-aware-verification]
+    work-unit.attach-sync-integration: [work-unit.intensity-aware-verification]
+    work-unit.intensity-aware-verification: [work-unit.intensity-aware-review]
+    work-unit.intensity-aware-review: [work-unit.release-and-rollback]
+    work-unit.release-and-rollback: []
+    work-unit.spec-synthesis: [work-unit.prototype-design, work-unit.technical-analysis, work-unit.ticket-decomposition]
+    work-unit.prototype-design: [work-unit.technical-analysis, work-unit.ticket-decomposition]
+    work-unit.technical-analysis: [work-unit.ticket-decomposition]
+    work-unit.ticket-decomposition: [work-unit.slice-implementation]
+  forbidden_shortcuts:
+    - {from: work-unit.spec-synthesis, to: work-unit.slice-implementation}
+    - {from: work-unit.prototype-design, to: work-unit.slice-implementation}
+    - {from: work-unit.technical-analysis, to: work-unit.slice-implementation}
+
 grill_exit:
   required: [frontier_empty, facts_resolved_or_routed, decisions_confirmed, shared_understanding_confirmed, no_unresolved_runnable_blocker]
   facts_resolved_or_routed:
@@ -467,7 +599,10 @@ wayfinder_completion:
   required: [no_open_children, no_open_blocked_or_claimed_children, no_fog, destination_clear]
 
 ready_for_agent:
-  required: [gates_satisfied, no_stale_artifacts, blockers_closed, implementation_context_ready, implementation_repo, implementation_branch, ci, verification_commands, rollback_point, slice_contract_approved, slice_contract_persisted, slice_contract_current_version, build_architecture_checklist, backend_slice_contract_if_applicable, backend_scaffold_policy_satisfied, frontend_implementation_plan_if_ui_impact]
+  required: [gates_satisfied, no_stale_artifacts, blockers_closed, implementation_context_ready, implementation_repo, implementation_branch, ci, verification_commands, rollback_point, predecessor_work_unit, ticket_decomposition_result_ref, ticket_decomposition_result_status, vertical_slice_ticket_ref, vertical_slice_ticket_role, vertical_slice_ticket_kind, slice_contract_approved, slice_contract_persisted, slice_contract_current_version, build_architecture_checklist, backend_slice_contract_if_applicable, backend_scaffold_policy_satisfied, frontend_implementation_plan_if_ui_impact]
+  ticket_formalization_validator: scripts/lib/lifecycle-transition.mjs
+  requires_vertical_slice_ticket: true
+  parent_ticket_as_implementation_ref: forbidden
 
 frontend_implementation_plan:
   applies_when: [ui_impact]

package/template/.pi/skills/yss-product-lifecycle/references/orchestration.md

@@ -5,8 +5,8 @@
 1. 识别模式、仓库身份、任务规模和影响面。
 2. `setup readiness`：每个任务只执行一次，核对 tracker、五态标签和领域文档布局，并在本轮缓存结果；仅在 tracker、主远端、真实标签或配置变化时重查。
 3. 加载父 Ticket/checkpoint 与真实资产，计算最近可信阶段。
-4. 评估资产、门禁和 `stale`，选择第一个未阻塞工作单元。
-5. 执行最小生命周期工作单元：只实际调用允许的 model-invoked skill；原生工作单元可直接持有正式资产，Matt 兼容 user-invoked skill 仅作为 workflow reference，仍由用户显式启动。将结果归一化为 `Workflow Execution Result`，验收输出并回写状态与证据。
+4. 评估资产、门禁和 `stale`，选择第一个未阻塞工作单元。进入 `work-unit.slice-implementation` 前，必须先通过 `scripts/lib/lifecycle-transition.mjs` 的 Ticket 正式化、垂直切片绑定和合法 `next_route` 校验；父 Ticket、缺少垂直切片或 `ready-for-human` 的切片一律 `blocked`。
+5. 执行最小生命周期工作单元：主控先按 `docs/process/schemas/digital-human-task-package.schema.json` 编译并校验任务包，再只实际调用允许的 model-invoked skill；原生工作单元可直接持有正式资产，Matt 兼容 user-invoked skill 仅作为 workflow reference，仍由用户显式启动。将结果归一化为 `Workflow Execution Result`，验收输出并回写状态与证据。任务包的 `contract.kind` 按工作单元选择；只有实现子任务使用 `slice-implementation` 并消费 Slice Implementation Contract，其他阶段不伪造该合同。
 6. 若仍在授权和自动推进边界内，回到第 3 步；否则暂停。
 
 不要仅输出下一个提示词后结束 `orchestrate`/`resume`。不要因进入业务代码阶段而退出主控；应把实现交给专项 skill，并在返回后继续核验。
@@ -51,9 +51,12 @@ tracker 选择和冲突按 `docs/agents/issue-tracker.md` 裁决：已持久化
 
 ## Matt flow 进入条件
 
+- `work-unit.technical-analysis` 命中聚合、状态机、不变量、一致性、Domain Event、Gateway 或持久化映射影响时，先调度 `yss-tactical-design` 完成 Tactical DDD Check；默认嵌入系统概要设计 / 数据架构，复杂场景才生成 `artifact.tactical-design`。无领域影响记录 `not-applicable`。该 skill 只返回设计合同和验证结果，批准仍由生命周期编排器维护，发现 `stale`、`drift` 或 `new_impacts` 时不得继续 Ticket 正式化。
+
 - `work-unit.discovery-requirements` 实际调用 `grilling` 和 `domain-modeling`；`work-unit.discovery-opportunity` 按事实类型路由 `competitive-intelligence` 或 `research`。生命周期原生工作单元默认负责 Spec、Ticket 和实现资产；`to-spec`、`to-tickets`、`implement` 仅保留为显式兼容入口，结果必须回交生命周期验收。
-- 原生 `work-unit.ticket-decomposition` 只能在 OpenAPI Freeze 或无 API 影响记录后创建垂直切片，初始 Ticket 状态统一为 `ready-for-human`；生命周期复算完整公式后才能提升 `ready-for-agent`。
+- 原生 `work-unit.ticket-decomposition` 只能在 OpenAPI Freeze 或无 API 影响记录后创建垂直切片，初始 Ticket 状态统一为 `ready-for-human`；生命周期复算完整公式后才能提升 `ready-for-agent`。该工作单元必须返回 `ticket_decomposition_result_ref` 和垂直切片引用，并作为实现的必经前置证据。
 - 原生 `work-unit.slice-implementation` 必须在生命周期批准并持久化 Slice Implementation Contract 和 Build Architecture Checklist 后执行；用户显式 `implement` 仍走兼容入口，不得绕过生命周期。
+- `Workflow Execution Result.next_route` 必须通过生命周期转换校验；Spec、原型和技术分析不得直接跳转到 `work-unit.slice-implementation`，只能先进入 `work-unit.ticket-decomposition`。
 - `implement` 遇到 backend `scaffold_status=required` 时，还必须满足原型确认后的脚手架策略：脚手架 Execution Result、`yss-backend-scaffold-parent` 基线、Wrapper 验证和 Router 合同重编译均已回写；否则停在工程基线，不得写业务代码。
 - `Workflow Execution Result` 出现 `drift`、`new_impacts`、`stale_candidates`、`violation`、`missing_evidence`、空 `evidence_refs` 或缺少必需字段时暂停当前工作单元；旧结果只能先经只读兼容 adapter 归一化。
 

package/template/.pi/skills/yss-product-lifecycle/references/state-model.md

@@ -38,10 +38,15 @@ phase_boundary:
 
 ```text
 required gates ∈ {approved, not-applicable}
-AND related artifacts 不含 stale
+AND related artifacts 不含 stale（若命中领域影响，`artifact.tactical-design` 或嵌入式 Tactical DDD Check 引用必须为当前版本）
 AND blocking edges 全部关闭
 AND implementation repo/branch/CI/test/rollback 已明确
+AND `work-unit.ticket-decomposition` 已返回 `completed`，且其 `ticket_decomposition_result_ref` 证据可读取
+AND `vertical_slice_ticket_ref` 指向 `docs/.scratch/<feature>/issues/` 下的垂直切片 Ticket
+AND `vertical_slice_ticket_kind=vertical-slice-ticket` 且 `vertical_slice_ticket_role=ready-for-agent`
+AND `vertical_slice_ticket_ref` 不得指向 `parent-ticket.md`
 AND Slice Implementation Contract 已由生命周期编排器批准并持久化
+AND Slice Implementation Contract 的 `ticket_ref` 与 `vertical_slice_ticket_ref` 完全一致
 AND 当前工作单元消费的 contract_id/version 与最新批准版本一致
 AND Backend Slice Implementation Contract（后端适用）和 Build Architecture Checklist 已完成
 AND backend 影响且 scaffold_status=required 时，原型确认后的脚手架策略、`yss-backend-scaffold-parent` 基线、Wrapper 验证和 Router 重编译均已完成
@@ -53,7 +58,7 @@ AND UI 影响切片的前端实现还原计划已通过 schema 校验、`templat
 
 发布前还必须满足所有已触发门禁均为 `approved` 或 `not-applicable`；UI 影响切片必须额外通过 `gate.frontend-implementation-verified`，不能只凭 fresh verification 和回滚点放行。
 
-用户显式运行 `to-tickets` 后，垂直切片初始 Ticket 状态固定为 `ready-for-human`。只有 `yss-product-lifecycle` 复算上述公式全部为真后，才能把它提升为 `ready-for-agent`；生命周期不会自动调用 `to-tickets`，其默认标签也不参与该裁决。
+用户显式运行 `to-tickets` 后，垂直切片初始 Ticket 状态固定为 `ready-for-human`。原生路径执行 `work-unit.ticket-decomposition` 时同样必须产生等价的垂直切片和 `Workflow Execution Result` 证据。只有 `yss-product-lifecycle` 复算上述公式全部为真后，才能把它提升为 `ready-for-agent`；生命周期不会自动调用 `to-tickets`，但不得跳过 Ticket 正式化工作单元。其默认标签也不参与该裁决。
 
 ## Review 与 Git 授权状态
 

package/template/.pi/skills/yss-router/SKILL.md

@@ -13,20 +13,21 @@ description: Use when a YSS vertical slice is entering implementation, spans mul
 
 ## 编译循环
 
-1. 判断 frontend/backend/API/data/cross-repo 影响，并逐项填写 backend `component_impacts`。
+1. 判断 frontend/backend/API/data/domain/cross-repo 影响，并逐项填写 backend `component_impacts`；命中聚合、状态机、不变量、一致性、Domain Event、Gateway 或持久化映射时加入 `yss-tactical-design`。
 2. 检查工程存在性和核心/长尾 skill 可用性。
 3. 选择主 skill，并按 [router-contract.yaml](references/router-contract.yaml) 计算强制依赖闭包。
 4. 为切片生成基线合同；为当前行为生成工作单元增量路由。
 5. 选择 `behavior-tdd` 或 `controlled-generation`。
 6. 输出 `draft`、`blocked` 或 `ready-for-lifecycle-review`，交生命周期编排器核验和持久化。
 
-合同结构见 [slice-implementation-contract.md](references/slice-implementation-contract.md)，专项返回协议见 [yss-skill-execution-result.md](references/yss-skill-execution-result.md)。
+合同结构见 [slice-implementation-contract.md](references/slice-implementation-contract.md)，专项返回协议见 [yss-skill-execution-result.md](references/yss-skill-execution-result.md)。前端、后端和测试子任务必须由生命周期主控从批准的 Slice Contract 编译任务包；任务包 schema 为 `docs/process/schemas/subagent-task-package.schema.json`，技能列表必须来自 `taskPackageDefaults`，不能由 Router 或执行 Agent 另行手写。
 
 ## 硬规则
 
 - Router 不得输出 `approved`、`ready-for-agent` 或 `completed`。
 - UI 影响缺少正式原型确认时，不得路由页面实现。
 - Repository/数据模型影响缺少数据架构时，不得路由持久化实现。
+- 领域影响缺少批准且版本当前的 tactical-design contract 时，不得路由 Domain 实现；无领域影响必须记录 `not-applicable`。
 - API 变化必须回到生命周期 Draft/Review/Freeze；半成品 backend 不得冒充稳定 source of truth。
 - 后端端到端切片必须包含 Application；对象/POJO 影响按契约自动补 `mapstruct`、`lombok`、`alibaba-java-code-style`。
 - Harness 内实现路径必须落在 `apps/backend/<project>/` 或 `apps/frontend/<project>/` 的具体项目目录；`apps/backend/`、`apps/frontend/` 只能作为容器，`app/backend/`、`app/frontend/` 及其子路径一律阻断。外部实现仓库使用其登记的真实项目根路径。`git-submodule` 使用 `implementation_path_policy: git-submodule-harness-apps`，空 gitlink、detached HEAD 或 `--force` 覆盖挂载点不得脚手架；`inspectWorkingTreeScope.writable` 必须为显式布尔值。
@@ -36,6 +37,7 @@ description: Use when a YSS vertical slice is entering implementation, spans mul
 - 脚手架合同在 Router 阶段只能是 `draft` / `ready-for-lifecycle-review` / `blocked`；只有生命周期编排器可以把已持久化脚手架合同标记为 `approved`。脚手架合同只覆盖业务代码前的工程骨架工作单元；生成、基线校验和 Router 重编译完成后，它不能替代脚手架后的 Slice Implementation Contract。
 - 脚手架输出消费批准的脚手架合同；脚手架后的所有生成后端代码都必须绑定当前批准且版本当前的 Slice Implementation Contract、主 YSS skill、依赖闭包、允许写路径、预期证据和 YSS Skill Execution Result。打印命令、`./mvnw validate` 单项通过或脚手架成功不能替代合同批准；生成范围从机械内容变成业务行为时触发完整重路由。
 - 专项结果中的越界路径、缺失证据、`drift`、`violation` 或 `new_impacts` 必须阻断或重路由。
+- 前后端子任务必须使用同一 `contract_id/contract_version`，并在任务包中记录 `role_id`、`runtime_id`、`execution_state`、`allowed_write_paths`、`downstream_consumers` 和 `convergence_ref`；版本不一致或汇合引用缺失时输出 `blocked`。
 - 长尾 skill 不可用时显式 `blocked`，不得用通用知识假装已应用 YSS 规范。
 
 ## 三级路由

package/template/.pi/skills/yss-router/references/router-contract.yaml

@@ -66,11 +66,11 @@ exclusive_flags:
 
 slice_contract_required:
   root: [schema_version, contract_id, contract_version, slice_id, status, lifecycle_refs, readiness, common, frontend, backend, contract, cross_repo, work_units]
-  lifecycle_refs: [spec, ticket, requirement_freeze, low_fidelity_review, prototype_review, high_fidelity_html, prototype_verification, antd_cli_evidence, browser_verification_evidence, prototype_confirmation, openapi_freeze_or_no_impact, architecture_review, data_architecture, engineering_baseline, build_architecture_checklist, implementation_repository, frontend_repository, backend_repository, maven_wrapper]
+  lifecycle_refs: [spec, ticket, requirement_freeze, low_fidelity_review, prototype_review, high_fidelity_html, prototype_verification, antd_cli_evidence, browser_verification_evidence, prototype_confirmation, openapi_freeze_or_no_impact, architecture_review, data_architecture, tactical_design, engineering_baseline, build_architecture_checklist, implementation_repository, frontend_repository, backend_repository, maven_wrapper]
   readiness: [blockers, stale_inputs, not_applicable]
   common: [impacted_areas, implementation_path_policy, project_roots, required_skills, optional_skills, unavailable_skills, allowed_write_paths, forbidden_patterns, expected_evidence_files, verification_commands, human_review_points, full_reroute_triggers]
   frontend: [status, required_skills, approved_prototype_ref, state_matrix_ref, allowed_write_paths, component_test_seams, e2e_paths]
-  backend: [status, affected_layers, component_impacts, required_skills, application_boundary, transaction_boundary, persistence_strategy, allowed_write_paths, forbidden_patterns, expected_evidence_files, seam_deferred, verification_commands]
+  backend: [status, affected_layers, component_impacts, required_skills, application_boundary, transaction_boundary, persistence_strategy, allowed_write_paths, forbidden_patterns, expected_evidence_files, seam_deferred, verification_commands, tactical_ddd]
   contract: [api_impact, freeze_ref, no_api_impact_ref, generated_clients, contract_tests, regeneration_commands]
   cross_repo: [repositories, delivery_order, integration_verification, rollback_order]
 
@@ -91,6 +91,7 @@ lifecycle_ref_by_readiness:
   openapi_freeze: openapi_freeze_or_no_impact
   no_api_impact_record: openapi_freeze_or_no_impact
   data_architecture: data_architecture
+  tactical_design: tactical_design
   engineering_baseline: engineering_baseline
   backend_repository: backend_repository
   maven_wrapper: maven_wrapper
@@ -135,6 +136,10 @@ applicable_subcontract_nonempty:
   backend:
     scalar: [application_boundary, transaction_boundary, persistence_strategy]
     array: [affected_layers, required_skills, allowed_write_paths, forbidden_patterns, expected_evidence_files, verification_commands]
+    conditional_tactical_ddd:
+      when: [aggregate-impact, state-machine-impact, invariant-impact, consistency-impact, domain-event-impact, gateway-boundary-impact, persistence-mapping-impact]
+      scalar: [tactical_design_ref, tactical_design_version, gateway_boundary_ref]
+      array: [aggregate_refs, invariant_refs, state_behavior_refs, domain_test_seams, application_test_seams]
   contract_api:
     scalar: [freeze_ref]
     array: [contract_tests]
@@ -148,8 +153,12 @@ dependency_closure:
     always: [yss-backend-scaffold-parent, alibaba-java-code-style]
   yss-domain:
     always: [alibaba-java-code-style]
-    when_modeling: [domain-modeling]
+    when_modeling: [domain-modeling, yss-tactical-design]
     when_pojo: [lombok]
+  yss-tactical-design:
+    always: [domain-modeling]
+    when_api_impact: [yss-openapi-draft-review]
+    when_data_impact: [yss-repository]
   yss-application:
     always: [alibaba-java-code-style]
     when_conversion: [mapstruct, lombok]
@@ -218,6 +227,12 @@ full_reroute_triggers:
   - data-model-impact
   - new-write-path
   - new-repository
+  - aggregate-impact
+  - invariant-impact
+  - consistency-impact
+  - domain-event-impact
+  - gateway-boundary-impact
+  - persistence-mapping-impact
   - new-required-skill
   - not-applicable-invalidated
   - architecture-drift