用户定的逻辑:「调用活动,输入数据可以不定或者为空;进入活动后受理归一,
信息不全派补全单。」把收敛点从门口挪进活动 —— 三道门口闸全撤:
· 触发装配:缺必填**不再入死信**(AssemblyResult 的 missing 改 partial,带上已装配的);
装到多少带多少照样起单。死信只留给真错误(勾了确认没指定人这类配置错误)。
· process.start:撤掉调用接口缺项闸 —— 从前缺一个字段整条流都起不来,
现实是客户来信本来就常缺客户码,拦在门外等于要求外界替系统把信息备齐。
· task.start(替代旧 AM 12.1「缺项不得启动」):缺必填的任务落成「等人」,
缺的字段做成**补全卡**(elicitation,标签取 schema 的 title)发到负责人的
任务对话流,并武装 human 监听(IntakeDesk 端口;不占活动的人卡预算)。
答复只收契约声明过的键,合并进 data;齐了或答「没法填」才转 running 开跑;
答一半就就缺的部分再派一张卡。等人期间谱一步不走、不扣步数。
· 测试台预检改成**信息**不是闸:灯灭不拦起单,文案直说
「抽不出的键由受理补全单找人收齐」。
5 条受理归一单测 + 全链实测:投一封只写「想问下工控板价格」的信(零键)→
流照起 → A1 落负责人工位、等人、补全卡在对话流 → 答卡(customerCode/rfqRef)→
任务醒、合并、谱跑 3 步到验收。修一处接线错误:监听 deadline 要 ISO-8601
时长(P2D)不是时刻,传错整个补全监听静默没装上。
trigger/task/process 三份 CONTRACT.md 与产品设计.md 同步(宽进纪律成文)。
五闸绿;契约快照随本提交入库。
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KeDBx2PHLavbURXB8LJJ7m
139 lines
5.3 KiB
TypeScript
139 lines
5.3 KiB
TypeScript
/**
|
|
* module: task —— 本模块要外界提供的能力(编码规范 §10.1 / §5.3)。
|
|
*/
|
|
import type { BudgetCaps, Paradigm, StaffId, TaskId, TerminalState } from '@contracts';
|
|
import type { Consumption } from './internal/domain/harness.ts';
|
|
import type { LandedFacts, Task } from './contract.ts';
|
|
export type Clock = {
|
|
now(): Date;
|
|
};
|
|
export type IdGenerator = {
|
|
next(): string;
|
|
};
|
|
export type TaskStore = {
|
|
insert(task: Task): Promise<void>;
|
|
get(taskId: TaskId): Promise<Task | undefined>;
|
|
listByOwner(ownerId: StaffId, openOnly: boolean): Promise<Task[]>;
|
|
update(taskId: TaskId, patch: Partial<Task>): Promise<Task>;
|
|
addConsumption(taskId: TaskId, delta: Partial<Consumption>): Promise<Consumption>;
|
|
lastProgressAt(taskId: TaskId): Promise<Date | undefined>;
|
|
markProgress(taskId: TaskId, at: Date): Promise<void>;
|
|
};
|
|
/** 活动装载 —— app 注入 `activity-registry`(L4) */
|
|
export type ActivityLoader = {
|
|
load(activityId: string): Promise<{
|
|
paradigm: Paradigm;
|
|
caps: BudgetCaps;
|
|
envelope: Record<string, unknown>;
|
|
/** 输入 data 的 JSON Schema —— 缺项不得启动 */
|
|
inputSchema: Record<string, unknown>;
|
|
businessModel: unknown;
|
|
stallAfter: string;
|
|
}>;
|
|
};
|
|
export type SchemaValidator = {
|
|
validate(schema: Record<string, unknown>, value: unknown): {
|
|
ok: boolean;
|
|
errors: string[];
|
|
};
|
|
};
|
|
/** 范式引擎 —— loop / flow 在此汇流;对上层不可区分(§9 双层边界) */
|
|
export type ParadigmEngine = {
|
|
load(taskId: TaskId, model: unknown): Promise<void>;
|
|
advance(taskId: TaskId): Promise<EngineOutcome>;
|
|
onEvent(taskId: TaskId, event: {
|
|
kind: 'data' | 'time' | 'human' | 'control';
|
|
ref: string;
|
|
payload: Record<string, unknown>;
|
|
}): Promise<EngineOutcome>;
|
|
};
|
|
export type EngineOutcome = {
|
|
readonly status: 'running' | 'awaiting' | 'submitted' | 'finished' | 'blocked';
|
|
readonly reason?: string;
|
|
/** 谱走完时:放行是否通过 —— **完成只出自放行通过**,引擎不自行宣布完成 */
|
|
readonly released?: boolean;
|
|
/** 选择组的出口选择:恰发一口,随放行一并确认 */
|
|
readonly selectedPorts?: Record<string, string>;
|
|
};
|
|
/**
|
|
* 落地收敛 —— app 注入 `release`(L4)。
|
|
* 放行通过的那一刻才落地:草稿合并入正式版、动作意向执行、收敛后才发射输出口。
|
|
*/
|
|
export type LandingGateway = {
|
|
land(input: {
|
|
taskId: TaskId;
|
|
ownerId: StaffId;
|
|
humanCallCap: number;
|
|
/** 选择组的出口选择 —— 恰发一口,由放行时的确认给定 */
|
|
selectedPorts: Readonly<Record<string, string>>;
|
|
}): Promise<{
|
|
converged: boolean;
|
|
emittedPorts: readonly string[];
|
|
ledgerRowsMerged: number;
|
|
/** 已落地的事实 —— 输出口载荷,随终态报给流程层 */
|
|
facts: LandedFacts;
|
|
}>;
|
|
};
|
|
export type MemoryRecorder = {
|
|
append(input: {
|
|
taskId: TaskId;
|
|
/** control = 治理干预(叫停 / 恢复 / 改派):人对过程的裁断,归人裁决侧 */
|
|
kind: 'engine-transition' | 'terminal' | 'observation' | 'control';
|
|
title: string;
|
|
detail?: Record<string, unknown>;
|
|
}): Promise<void>;
|
|
seal(taskId: TaskId): Promise<void>;
|
|
/** 终态封卷触发蒸馏钩子 —— 产出活动记忆候选条目 */
|
|
distill(input: {
|
|
taskId: TaskId;
|
|
activityId: string;
|
|
trigger: 'terminal';
|
|
prompt: string;
|
|
}): Promise<unknown>;
|
|
hasHistory(taskId: TaskId): Promise<boolean>;
|
|
};
|
|
/** 监听在等?—— app 注入 `event`(L1):监听中是健康态,与停滞分别对待 */
|
|
export type ListenerProbe = {
|
|
hasArmedListener(taskId: TaskId): Promise<boolean>;
|
|
};
|
|
/** 草稿层与运行时状态是否在 —— 断点续跑的三份持久状态 */
|
|
export type PersistenceProbe = {
|
|
hasDrafts(taskId: TaskId): Promise<boolean>;
|
|
hasRuntimeState(taskId: TaskId): Promise<boolean>;
|
|
};
|
|
/** 控制事件与终态事件 —— app 注入 `event`(L1) */
|
|
export type TaskEventPublisher = {
|
|
publishControl(taskId: TaskId, semantic: string, by: StaffId, reason?: string): Promise<void>;
|
|
/** `facts` = 落地收敛的事实,作为输出口载荷随终态报给流程层;非放行终态为空 */
|
|
publishTerminal(taskId: TaskId, terminal: TerminalState, reason: string, facts: LandedFacts): Promise<void>;
|
|
};
|
|
/** 改派通知 —— app 注入 `message`(L2):改派留痕并**通知双方** */
|
|
export type ReassignNotifier = {
|
|
notify(input: {
|
|
from: StaffId;
|
|
to: StaffId;
|
|
taskId: TaskId;
|
|
title: string;
|
|
by: StaffId;
|
|
}): Promise<void>;
|
|
};
|
|
/** 交互态 —— app 注入 `interaction`(L3):控制权按态转交 */
|
|
/**
|
|
* 受理补全台(2026-07-30 宽进):把缺的必填字段做成补全卡发到负责人的任务对话流,
|
|
* 并武装 human 监听等答复 —— app 注入 human-tool + event。
|
|
*/
|
|
export type IntakeDesk = {
|
|
askCompletion(input: {
|
|
taskId: string;
|
|
ownerId: string;
|
|
title: string;
|
|
fields: ReadonlyArray<{
|
|
key: string;
|
|
label: string;
|
|
}>;
|
|
}): Promise<void>;
|
|
};
|
|
export type InteractionPhaseSetter = {
|
|
setPhase(taskId: TaskId, phase: 'activating' | 'active' | 'awaiting-human' | 'awaiting-event' | 'transitioning' | 'terminal'): Promise<void>;
|
|
};
|