判据 ④⑤ 解锁:G2 并行网关起出 A3 / A2 —— 输出口发射的是落地事实

G2 之后一直不分流,根因三条,逐条修:

① 输出口载荷是空的。`outputPortsOf` 原先从**作用域**里捞字段拼载荷,
   而放行那一刻草稿层已合并并清空,捞到的只剩起单入参 —— 下游节点必然缺字段。
   改为:载荷取自**落地收敛的事实**,由 `releaseWrite` 回报合并了哪些行,
   经 release → task → app 一路带上来。这也正是「落地收敛,输出口才发射」的字面意思:
   发射的就该是已经落地的那些事实。
   `LandedFacts` 给两种读法:铺平(标量取值)与逐行(数组取值),
   输出口声明里 `type: 'array'` 的属性填逐行,标量属性填铺平值(驼峰/下划线两种写法都认)。

② 一条分支起不来,把整条终态上报连坐掀翻 —— 于是**上游任务的终态也报不上去**,
   流停在原地,一行日志都没有。改为:该分支记 `node-start-failed` 事件 + 落一个
   blocked 实例,其余分支照走,在治理台「需处置」里现形。
   (这条是先修的:正因为它,前面两条才一直查不出来。)

③ 边映射引用了不存在的路径:`G2→A3` 的 pn 取 `intake.records`(那是想象中的 LLM 出参形状)、
   `G2J→A4` 的 records 取 `initiation.records`(起单时根本还没有这些行)。
   按输出口的真实声明改正。

结果:A1 released → G2 并行分叉 → **A3 渠道寻源落到林佩萱、A2 替代选型落到王梓名**,
两个 loop 活动同时在跑,岗位解析正确。

gates: tsc / eslint / depcruise(317 模块)/ api-report / 393 测试 全绿

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KeDBx2PHLavbURXB8LJJ7m
This commit is contained in:
2026-07-27 04:52:53 +08:00
co-authored by Claude Opus 5
parent 1721bcf6e3
commit 9de33a5416
22 changed files with 223 additions and 35 deletions
+22
View File
@@ -51,6 +51,17 @@ export type DraftWrite = {
export type ReleaseWriteResult = {
readonly mergedRows: number;
readonly emittedEvents: number;
/**
* 合并进正式版的那些行(键 + 值)。
* 「落地收敛,输出口才发射」——发射的载荷就该是**这些已落地的事实**,
* 而不是从作用域里再猜一遍:放行后草稿层已清空,再猜就什么也猜不到。
*/
readonly merged: ReadonlyArray<{
readonly domain: string;
readonly object: string;
readonly key: Record<string, unknown>;
readonly values: Record<string, unknown>;
}>;
};
/**
* 写三分是**三个不同方法**,不是一个带 flag 的方法 —— 调用方拿不到「绕门」的形态(§7.2)。
@@ -69,6 +80,17 @@ export type LedgerService = {
query(query: LedgerQuery): Promise<LedgerPage>;
/** 任务视图 = 正式版 + 本任务草稿层 */
taskView(taskId: TaskId, query: LedgerQuery): Promise<LedgerPage>;
/**
* **本任务自己写的**草稿条目(读己之写的读面)。
* 与 `taskView` 的区别:那个是「正式版 + 我的草稿」的合并视图,
* 这个只回我写过的那些行 —— 引擎求值要区分「这一单的事实」与「别人放行后的事实」。
*/
taskDrafts(taskId: TaskId): Promise<Array<{
domain: string;
object: string;
key: Record<string, unknown>;
patch: Record<string, unknown>;
}>>;
/** 落地预检第五项:数据冲突检查 */
checkConflicts(taskId: TaskId): Promise<ConflictFinding[]>;
discardDrafts(taskId: TaskId): Promise<void>;
+7
View File
@@ -45,6 +45,13 @@ export type LandOutcome = {
/** 落地收敛后才发射的输出口 */
readonly emittedPorts: readonly string[];
readonly ledgerRowsMerged: number;
/** 已落地的事实 —— 输出口发射的载荷取自这里 */
readonly merged: ReadonlyArray<{
readonly domain: string;
readonly object: string;
readonly key: Record<string, unknown>;
readonly values: Record<string, unknown>;
}>;
/** 落地受阻时发出的落地失败卡 */
readonly failureWorkOrderId?: string;
};
+7
View File
@@ -23,6 +23,13 @@ export type LedgerGateway = {
releaseWrite(taskId: TaskId): Promise<{
mergedRows: number;
emittedEvents: number;
/** 合并进正式版的行 —— 输出口发射的载荷取自这里 */
merged: ReadonlyArray<{
domain: string;
object: string;
key: Record<string, unknown>;
values: Record<string, unknown>;
}>;
}>;
};
/** 工具 —— app 注入 `toolbox`(L2);预检的②③④项与落地执行都经它 */
+10 -1
View File
@@ -18,6 +18,14 @@ export declare class TaskAlreadyTerminalError extends Error {
constructor(taskId: TaskId, terminal: TerminalState);
}
/** 一单任务 —— 活动的运行时实例;**恰有一名负责人** */
/** 落地事实的两种读法:铺平(标量取值)与逐行(数组取值)—— 输出口载荷由此装配 */
export type LandedFacts = {
readonly flat: Record<string, unknown>;
readonly rows: ReadonlyArray<{
key: Record<string, unknown>;
values: Record<string, unknown>;
}>;
};
export type Task = {
readonly id: TaskId;
readonly activityId: string;
@@ -78,7 +86,8 @@ export type TaskService = {
/** 改派:在途任务的负责人变更,**留痕并通知双方** */
reassign(taskId: TaskId, to: StaffId, by: StaffId): Promise<Task>;
/** 终态裁定 —— 完成由框架裁定,终态由系统命名 */
finish(taskId: TaskId, cause: TerminalCause): Promise<Task>;
/** `facts` = 落地收敛的事实(仅放行路径有);作为输出口载荷上报流程层 */
finish(taskId: TaskId, cause: TerminalCause, facts?: LandedFacts): Promise<Task>;
/** 断点续跑的三份持久状态是否齐备 */
resumeReadiness(taskId: TaskId): Promise<ResumeReadiness>;
};
+1 -1
View File
@@ -1,7 +1,7 @@
/**
* module: task —— 唯一出口。只做 re-export,不写逻辑(编码规范 §10.1)。
*/
export type { BudgetBreach, BudgetCaps, Consumption, ControlOutcome, ControlSemantic, HarnessVerdict, Paradigm, ResumeReadiness, StartTaskInput, Task, TaskRuntimeState, TaskService, TaskSnapshot, TerminalCause, TerminalState, TickOutcome, } from './contract.ts';
export type { BudgetBreach, LandedFacts, BudgetCaps, Consumption, ControlOutcome, ControlSemantic, HarnessVerdict, Paradigm, ResumeReadiness, StartTaskInput, Task, TaskRuntimeState, TaskService, TaskSnapshot, TerminalCause, TerminalState, TickOutcome, } from './contract.ts';
export { TaskAlreadyTerminalError, TaskNotFoundError } from './contract.ts';
export type { ActivityLoader, Clock, IdGenerator, InteractionPhaseSetter, ListenerProbe, MemoryRecorder, ParadigmEngine, PersistenceProbe, ReassignNotifier, SchemaValidator, TaskEventPublisher, TaskStore, } from './port.ts';
export type { TaskServiceDeps } from './internal/usecase/task-service.ts';
+5 -2
View File
@@ -3,7 +3,7 @@
*/
import type { BudgetCaps, Paradigm, StaffId, TaskId, TerminalState } from '@contracts';
import type { Consumption } from './internal/domain/harness.ts';
import type { Task } from './contract.ts';
import type { LandedFacts, Task } from './contract.ts';
export type Clock = {
now(): Date;
};
@@ -66,6 +66,8 @@ export type LandingGateway = {
converged: boolean;
emittedPorts: readonly string[];
ledgerRowsMerged: number;
/** 已落地的事实 —— 输出口载荷,随终态报给流程层 */
facts: LandedFacts;
}>;
};
export type MemoryRecorder = {
@@ -98,7 +100,8 @@ export type PersistenceProbe = {
/** 控制事件与终态事件 —— app 注入 `event`(L1) */
export type TaskEventPublisher = {
publishControl(taskId: TaskId, semantic: string, by: StaffId, reason?: string): Promise<void>;
publishTerminal(taskId: TaskId, terminal: TerminalState, reason: string): Promise<void>;
/** `facts` = 落地收敛的事实,作为输出口载荷随终态报给流程层;非放行终态为空 */
publishTerminal(taskId: TaskId, terminal: TerminalState, reason: string, facts: LandedFacts): Promise<void>;
};
/** 改派通知 —— app 注入 `message`(L2):改派留痕并**通知双方** */
export type ReassignNotifier = {