mirror of
https://github.com/ThearchyHelios/AgentLab.git
synced 2026-11-21 17:12:05 +00:00
口径台账:固定执行、验证审阅发布与增量重导入
- QueryCore 固定执行(K09):按已发布的不可变口径跑一次,交回类型化标量、发布/manifest 引用与逐查询证据 - 依赖闭包(K08):按选中的指标算出要拷的取数节点、要的入口字段,接进 derive / compose / metrics - SQL 模板参数完整性(K01):试跑、组合问数、派生图、运行时取数共用一套语义,缺参数在渲染前就拒 - 受限字段变更服务(K03)与口径领域边界(K01):改动打在整图深拷贝上,身份与证据归属不可改 - 版本化受控模板绑定(K04):业务口径按显式绑定落到 SQL,对不上就报 unsupported / needs_update - 验证记录(K05)与最小审阅:样例匹配不等于正式批准,审批人只从服务端身份取 - 发布依据清单(K07):发布时按不可变图物化内容寻址清单,正式用途按它判 - 增量重导入(K11)与 B/L/R 三方合并、受限自然语言修改提案(K12):只产候选,落图仍走既有写路径 - 接口与前端:口径草稿页接上字段变更、绑定状态、验证与重导入,新增 caliber-drafts / studio 检查脚本 验证:前端 tsc -b 通过。
This commit is contained in:
@@ -12,9 +12,10 @@
|
||||
* 请求函数从 ./http 导入,不从 ./client 导入(client.ts 要导入这个文件,反过来就成了循环)。
|
||||
*/
|
||||
import type {
|
||||
CaliberDescriptor, CaliberDraft, CaliberDraftAttachOut, CaliberDraftSummary, CaliberTrialOut, CertifyQueue, DraftMetric,
|
||||
DraftTrialOut, FreezeOut, LedgerFeedbackOut, LedgerFeedbackVerdict, LedgerIssueOut, LedgerReconcileIn, LedgerReconcileOut,
|
||||
RunLedger,
|
||||
CaliberDescriptor, CaliberDraft, CaliberDraftAttachOut, CaliberDraftSummary, CaliberTrialOut, CertifyQueue, DraftExpectIn,
|
||||
DraftImportAcceptOut, DraftImportRun, DraftMetric, DraftOperation, DraftTrialOut, DraftValidationsOut, FreezeOut,
|
||||
LedgerFeedbackOut, LedgerFeedbackVerdict, LedgerIssueOut, LedgerReconcileIn, LedgerReconcileOut, NlChangeOut,
|
||||
NlChangePreviewOut, RunLedger, DraftValidationRecord,
|
||||
} from '../typesLedger'
|
||||
import { get, patch, post, type RequestOptions } from './http'
|
||||
|
||||
@@ -62,10 +63,25 @@ export const caliberLedger = {
|
||||
draftTrial: (draftId: string, opts?: RequestOptions) => get<DraftTrialOut>(`${draftAt(draftId)}/trial`, opts),
|
||||
/**
|
||||
* 按填好的入口字段再试运行一次(POST 同一个路径):参数按入口字段校验,缺必填回 422;
|
||||
* 返回 {run_id, status, metrics, error},status 是 running / succeeded / failed / needs_input
|
||||
* 返回 {run_id, status, metrics, error},status 是 running / succeeded / failed / needs_input。
|
||||
*
|
||||
* 带 expect(K05 的固定期望)时,期望里的指标必须是这张卡上的、要**逐条给全**(不合规回 422,不发起运行);
|
||||
* 跑完把结果追加成一条验证记录。不带 expect 也能跑,但那样只记 observed——没有独立期望就不能算验证通过。
|
||||
*/
|
||||
runDraftTrial: (draftId: string, inputs: Record<string, unknown>) =>
|
||||
post<DraftTrialOut>(`${draftAt(draftId)}/trial`, { inputs }),
|
||||
runDraftTrial: (draftId: string, inputs: Record<string, unknown>, expect?: DraftExpectIn) =>
|
||||
post<DraftTrialOut>(`${draftAt(draftId)}/trial`, expect ? { inputs, expect } : { inputs }),
|
||||
/** 这份草稿的验证记录(新的在前)+ 总情况 + 字段基线状态:K06 读的那份契约 */
|
||||
draftValidations: (draftId: string, opts?: RequestOptions) =>
|
||||
get<DraftValidationsOut>(`${draftAt(draftId)}/validations`, opts),
|
||||
/**
|
||||
* 对一条验证记录做一次审阅(builder 及以上):confirmed / rejected,只追加。请求体里**没有 actor**,
|
||||
* 审批人取服务端身份(关登录时是自报署名);没有能记下来的主体时回 409 review_actor_required。
|
||||
* 返回里的 record 带这次决定和 covers_current(所审记录还算不算覆盖当前定义/绑定)
|
||||
*/
|
||||
reviewValidation: (draftId: string, recordId: string, body: { decision: 'confirmed' | 'rejected'; note?: string;
|
||||
metrics?: string[] }) =>
|
||||
post<{ ok: boolean; draft_id: string; record: DraftValidationRecord }>(
|
||||
`${draftAt(draftId)}/validations/${encodeURIComponent(recordId)}/review`, body),
|
||||
/** 选文档发起起草:documents 是要用的知识库文档 id,guidance 是给模型看的附加要求,
|
||||
* fixed_filters 是每次跑都不变的条件(工厂、产线、属性组),服务端要求写死在 SQL 里、不做成入口字段 */
|
||||
extractDraft: (body: { documents: string[]; collection?: string; datasource_id?: string; guidance?: string;
|
||||
@@ -73,13 +89,85 @@ export const caliberLedger = {
|
||||
post<{ draft_id: string; status: string }>('/ledger/drafts/extract', body),
|
||||
/**
|
||||
* 改标题、整体换掉指标、或把答清的问题消掉(resolved 是问题原文)。服务端据此重算状态:还有问题 → questions_open,
|
||||
* 否则 ready;已经接上或驳回的不改状态
|
||||
* 否则 ready;已经接上或驳回的不改状态。
|
||||
*
|
||||
* 已接管的草稿(有取数图)是 K02 的并发保护对象:expected_revision 是读草稿时给的 revision(必带,缺了 409
|
||||
* revision_required),target.card_id 在多张可写的卡时必须给(否则 409 card_required),request_id 是幂等键——
|
||||
* 同一个键带着同样的内容重发不会多存一版。基准版本过期回 409 stale_revision(另带 current_version),
|
||||
* 这时保留页面上的编辑、刷新详情后再改。
|
||||
*
|
||||
* 走 operations 时回执里另带 change 一段(变更分类、影响指标、定义指纹前后值、失效说明、绑定状态);同键同内容的
|
||||
* 重放交回的是当前视图(带 replayed),不再重算一份回执
|
||||
*/
|
||||
patchDraft: (draftId: string, body: { title?: string; metrics?: DraftMetric[]; resolved?: string[] }) =>
|
||||
patch<CaliberDraft>(draftAt(draftId), body),
|
||||
patchDraft: (draftId: string, body: {
|
||||
title?: string; metrics?: DraftMetric[]; resolved?: string[]
|
||||
/** K03 的字段操作:按稳定 metric_id + 字段路径改一处;和 metrics / resolved 互斥(422 change_conflict) */
|
||||
operations?: DraftOperation[]
|
||||
expected_revision?: number; request_id?: string
|
||||
target?: { workflow_id?: string; card_id?: string }
|
||||
}) => patch<CaliberDraft>(draftAt(draftId), body),
|
||||
/** 接上一次真实运行补取数路径(app/ledger/docattach.py):由它建工作流和版本,定义来自草稿 */
|
||||
attachDraft: (draftId: string, runId: string) => post<CaliberDraftAttachOut>(`${draftAt(draftId)}/attach`, { run_id: runId }),
|
||||
/** 「不是口径」:置 rejected,写一条审计,以后不再出现在列表的待办里 */
|
||||
dismissDraft: (draftId: string, note?: string) =>
|
||||
post<{ ok: boolean; draft_id: string; status: string }>(`${draftAt(draftId)}/dismiss`, { note: note ?? null }),
|
||||
|
||||
// ---- K11 增量重导入(app/ledger/reimport.py、api/caliber_import.py;搭建者)----
|
||||
/** 这份草稿的导入记录(新的在前),每条都带工作项和逐字段三方 */
|
||||
imports: (draftId: string, opts?: RequestOptions) =>
|
||||
get<{ runs: DraftImportRun[] }>(`${draftAt(draftId)}/imports`, opts),
|
||||
/**
|
||||
* 按这份草稿的来源文档重新抽一次候选 R(后台跑)。**不改 L、不改 B**:真正落到图上的只有 accept。
|
||||
* 带 request_id 的:同一份草稿 + 同一个键已经建过就交回那一次,不重复抽、不重复建工作项
|
||||
*/
|
||||
createImport: (draftId: string, requestId?: string) =>
|
||||
post<DraftImportRun>(`${draftAt(draftId)}/imports`, requestId ? { request_id: requestId } : {}),
|
||||
/** 一次导入的现状:工作项、逐字段三方、冲突;queued / running 时轮询它 */
|
||||
importRun: (runId: string, opts?: RequestOptions) =>
|
||||
get<DraftImportRun>(`/ledger/imports/${encodeURIComponent(runId)}`, opts),
|
||||
/**
|
||||
* 按**现在的** L / B 重算这次导入还没决定的三方,并刷新每项的比较锚点(人处置过的决定不动)。
|
||||
* 这是 409 import_stale_l 之后的恢复动作:候选算出来之后 L 被人改过,不能只把 expected_revision 更新到最新一版
|
||||
* 就覆盖上去,要按现在的口径重新算、人重新看过再接受
|
||||
*/
|
||||
refreshImport: (runId: string) =>
|
||||
post<DraftImportRun>(`/ledger/imports/${encodeURIComponent(runId)}/refresh`, {}),
|
||||
/** 人工把一条工作项对到图上某条指标(空串 = 取消对齐):baseline_unknown 和同名不同范围都走这里 */
|
||||
alignImportItem: (runId: string, itemId: string, metricId: string) =>
|
||||
post<DraftImportRun>(`/ledger/imports/${encodeURIComponent(runId)}/items/${encodeURIComponent(itemId)}/align`,
|
||||
{ metric_id: metricId }),
|
||||
/**
|
||||
* 接受选定字段:**一次性**落到 L(新增一版图)并按被接受的那几格推进 B。要带读到的基准版本
|
||||
* (expected_revision,缺了 409 revision_required、对不上 409 stale_revision)和幂等键。
|
||||
* items 一律按**工作项身份**(item_id)指认:同一条指标上可能有多条工作项(重复的候选、同一位被两项候选各带一份
|
||||
* 说法),按 metric_id 指会指错(服务端只在旧调用只给 metric_id 时才要求它在这条导入里唯一对得上一条);
|
||||
* fields 要**明确列出来**(页面列了几格就只接受几格,不靠 auto 猜)。服务端发现要接受的格子「当前内容和算候选时的
|
||||
* 那一版不一样」时回 409 import_stale_l(另带 fields 指出是哪几格),这时不能只更新 expected_revision 覆盖上去,
|
||||
* 要先 refreshImport 按现在的口径重算三方再让人确认
|
||||
*/
|
||||
acceptImport: (runId: string, body: {
|
||||
items: { item_id: string; metric_id?: string; fields: string[] }[]
|
||||
expected_revision?: number; request_id?: string
|
||||
}) => post<DraftImportAcceptOut>(`/ledger/imports/${encodeURIComponent(runId)}/accept`, body),
|
||||
/** 拒绝选定字段:保持 L 不动,也不推进 B。同样按工作项身份(item_id)指认;老调用可以用 seq */
|
||||
rejectImport: (runId: string, body: {
|
||||
items: { item_id: string; metric_id?: string; seq?: number; fields: string[] }[]; note?: string
|
||||
}) => post<DraftImportRun>(`/ledger/imports/${encodeURIComponent(runId)}/reject`, body),
|
||||
/** 显式恢复:把这次导入重新排进后台,续做还没完成的工作项(已接受 / 拒绝的不动,不重复建版) */
|
||||
resumeImport: (runId: string) =>
|
||||
post<DraftImportRun>(`/ledger/imports/${encodeURIComponent(runId)}/resume`, {}),
|
||||
|
||||
// ---- K12 受限的自然语言修改(app/ledger/nlchange.py;搭建者)----
|
||||
/** 一句话 → 受限修改提案:**只读**,不落库、不新增版本;说不清就只回澄清项 */
|
||||
changeProposal: (draftId: string, body: { instruction: string; metrics?: string[]
|
||||
target?: { workflow_id?: string; card_id?: string } }) =>
|
||||
post<NlChangePreviewOut>(`${draftAt(draftId)}/change-proposal`, body),
|
||||
/**
|
||||
* 一句话改口径:默认只预览(confirm=false);**confirm=true 才按同一批操作落一版**(内部翻成一次
|
||||
* DraftPatchIn 交给现有变更服务:expected_revision / request_id / CAS / 绑定同步一条不少)。
|
||||
* 说不清时回 409 并带澄清项,一条操作都不落
|
||||
*/
|
||||
nlChange: (draftId: string, body: { instruction: string; confirm: boolean; expected_revision?: number
|
||||
request_id?: string; metrics?: string[]; target?: { workflow_id?: string; card_id?: string } }) =>
|
||||
post<NlChangeOut>(`${draftAt(draftId)}/nl-change`, body),
|
||||
}
|
||||
|
||||
@@ -257,7 +257,10 @@ export const api = {
|
||||
name: string; description?: string; graph?: GraphSpec; tags?: string[]
|
||||
origin?: { run_id: string; conversation_id?: string; turn_id?: string }
|
||||
}) => post<Workflow>('/workflows', body),
|
||||
update: (id: string, body: Partial<Workflow> & { note?: string }) =>
|
||||
/** 改工作流:带 graph 就是保存一版。expected_revision 是读到的 Workflow.version(K02 的乐观锁):对不上回
|
||||
* 409 stale_revision(另带 current_version),这时页面保留自己的编辑、也不自动重放,人确认后再按最新一版
|
||||
* 显式重试(或载入最新版本) */
|
||||
update: (id: string, body: Partial<Workflow> & { note?: string; expected_revision?: number }) =>
|
||||
patch<Workflow>(`/workflows/${id}`, body),
|
||||
remove: (id: string) => del(`/workflows/${id}`),
|
||||
duplicate: (id: string) => post<Workflow>(`/workflows/${id}/duplicate`),
|
||||
|
||||
Reference in New Issue
Block a user