feat(roundtable): 深链接业务链抽取规范 + 总结报告文件干净/对话强制核对
深链接会商(taskId+goPath,businessCode)下按所选业务链完整层级强制校正 结构化抽取(flow-json) 与 方案总结报告: - 新增 harness 层 extraction_spec(app+harness 共用,单份领域知识两角色用法): build_structure_directive / build_summary_directive 按 businessCode 取 · rwfx(6BF):线性 任务→目的→行为体→预期行为→驱动因素→叙事;预期行为↔驱动因素 1:1、余 1:N · xdfx(7BF):分叉汇聚 DAG,根=行动;行动→受众目标/关键传播节点(1:N)→脆弱点(1:N)→策略(多对一) · 其余业务通用规范(强约束完整性+命名+取数、不套固定模板);business_code 空→零副作用 - 结构化抽取:flow_extract._hierarchy_hint + _validate_messages 用 structure_directive 权威覆盖默认层级(根治"无论什么业务都按目的→行为体抽/停在行为体");前端 streamFlowExtract 传 business_code(源 ingestBusinessCode) - 方案总结报告:前台 multi_agent._special_run(summary) + 后台 build_summary_prompt 注入 business 完整性核对(StartJobRequest/StartParams 透传) - 报告产物策略:.md 报告文件保持完整、干净、无需修改(不写 待补充/不足/⚠️); 「核对说明」(意图对齐+业务链完整性+不足/可补充)改为只在对话回复正文、且每次必出 - 种子 roundtable-structure SOUL 层级顺序改 spec-driven、去 rwfx 写死示例 Tests: test_roundtable_extraction_spec / test_roundtable_summary_prompt Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
3ab674e438
commit
b1b1ff98f5
17 files changed
+378
-25
No files matched your search
@@ -31,6 +31,8 @@ from fastapi.responses import StreamingResponse
|
||||
from langchain_core.messages import HumanMessage, SystemMessage
|
||||
from pydantic import BaseModel, Field
|
||||
|
||||
from deerflow.agents.roundtable_orchestrator.extraction_spec import build_structure_directive
|
||||
|
||||
from app.gateway.routers._roundtable_seed import (
|
||||
STRUCTURE_AGENT_ID,
|
||||
ensure_roundtable_functional_agents,
|
||||
@@ -59,6 +61,9 @@ class FlowExtractRequest(BaseModel):
|
||||
# 层级骨架:优先 coordinator_prompt 里写明的层级,否则用 chain_levels。
|
||||
chain_levels: list[str] = Field(default_factory=list)
|
||||
coordinator_prompt: str | None = Field(default=None)
|
||||
# 深链接业务码(rwfx→6BF 等)。非空 → 按该业务的「业务链抽取规范」**强制**注入完整层级
|
||||
# (覆盖默认/示例层级假设),根治"无论什么业务都按目的→行为体抽"。普通会商为空 → 不注入。
|
||||
business_code: str | None = Field(default=None)
|
||||
model: str | None = Field(default=None)
|
||||
# Phase 2 问答修改:带上当前图 + 用户指令 → 进 edit 模式(按指令改图,其余不变)。
|
||||
current_graph: dict[str, Any] | None = Field(default=None)
|
||||
@@ -438,6 +443,17 @@ def _material(req: FlowExtractRequest) -> str:
|
||||
|
||||
|
||||
def _hierarchy_hint(req: FlowExtractRequest) -> str:
|
||||
# 深链接业务规范**最高优先**:按 business_code 取写实/通用规范,覆盖任何默认层级假设。
|
||||
spec = build_structure_directive(req.business_code)
|
||||
if spec:
|
||||
cp = (req.coordinator_prompt or "").strip()
|
||||
if cp:
|
||||
spec += (
|
||||
"\n(若「业务链总控编排提示」对层级另有更细要求,可在**不违背上述完整层级**的前提下采纳:\n"
|
||||
+ cp
|
||||
+ ")"
|
||||
)
|
||||
return spec
|
||||
if (req.coordinator_prompt or "").strip():
|
||||
return "层级顺序优先采用下面「业务链总控编排提示」里写明的层级链(如它写的 任务→目的→行为体→…):\n" + req.coordinator_prompt.strip()
|
||||
levels = [s.strip() for s in req.chain_levels if s.strip()]
|
||||
@@ -504,8 +520,12 @@ def _edit_messages(req: FlowExtractRequest) -> list[Any]:
|
||||
|
||||
|
||||
def _validate_messages(req: FlowExtractRequest, extracted: str) -> list[Any]:
|
||||
# 深链接业务规范:校验阶段也带上完整层级,确保按规范补齐缺层(不只按抽取里出现的层级)。
|
||||
spec = build_structure_directive(req.business_code)
|
||||
spec_block = (spec + "\n\n") if spec else ""
|
||||
user = (
|
||||
_material(req)
|
||||
spec_block
|
||||
+ _material(req)
|
||||
+ "\n\n===== 已抽取的 flow-json(待校验修复)=====\n"
|
||||
+ extracted
|
||||
+ "\n===== 待校验结束 =====\n\n请对照数据来源,**逐个节点检查上面这份 flow-json 是不是缺字段**、并修复它:"
|
||||
|
||||
Reference in new issue
Block a user