Unverified50% confidenceDecision RuleExact time
DSupport's orchestrator holds no data tools and is only responsible for deciding who handles which part, always delegating to experts; if the orchestrator held tools, DSupportAssembly would fail to assemble directly, enforcing the architectural constraint through code.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedDSupport's architecture divides responsibilities as follows: the model (non-deterministic) handles understanding natural language, deciding which tool to call, drafting replies, and routing between experts; the code (deterministic) handles validating types and rules, hiding sensitive data, blocking operations that must not be allowed through, and running offline tests.75% similarUnverifiedThe tool plugin example imports defineTool from dsh-tools and declares inject: ['tools'], registers tools via ctx.tools.register, and tools must define name, description, parameters, execute, output.schema, and output.render60% similarUnverifiedDSH 的创造模式可在缺少工具时自行封装、创造新插件来完成目标，这种能力被称为工具制造（Tool Making）60% similarUnverifiedA Skill only needs to contain a single SKILL.md file to run, and all other components (scripts, references, resources, etc.) are optional.57% similarUnverifiedCodeSmith's Production-layer ToolSpec (located in crates/agent-runtime/src/tools/spec.rs) adopts a "capability is approval policy" design: tools containing the ExecutesCode capability require approval, tools containing the WritesFiles capability are recommended for approval, and the rest pass automatically, with the approval level derived from the capability set.57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1062643API
curl https://kongchang.com/api/v1/knowledge/claims/1062643MCP
get_claim(id=1062643)