中文 | English

Execution Primitives Layer

This layer owns reusable agent, harness, stream, typed-service, and tool execution primitives. It is not the complete Agent Runtime SDK and not the assembled product runtime. Product assembly decides which primitives, tool provider groups, harness providers, adapters, and services are active for a delivery form.

Modules

Crate	Responsibility	Local doc
agent-runtime	Agent registry, scheduler, prompt cache, hooks, goals, prompt facts, port-backed AgentRuntime facade, DeepReview provider-neutral state, DeepResearch citation renumbering, and runtime control contracts	AGENTS.md
agent-stream	Provider-neutral stream DTOs, tool-call accumulation, and replay contracts	AGENTS.md
tool-contracts	Tool contracts, execution gates, input validation, and result presentation contracts. Cargo package remains bitfun-agent-tools.	AGENTS.md
harness	Harness workflow contracts and registry primitives	AGENTS.md
runtime-services	Typed runtime service assembly and service availability facts	AGENTS.md
tool-provider-groups	Tool provider group facts and product-full tool group composition. Cargo package remains bitfun-tool-packs.	AGENTS.md
tool-execution	Low-level file/search/tool IO helpers. Cargo package remains tool-runtime.	AGENTS.md

Placement Rules

• Put portable execution orchestration, agent lifecycle contracts, tool contracts, provider-neutral stream contracts, and execution facts here.
• Keep concrete filesystem, git, terminal, MCP server, remote SSH, and OS behavior in services unless the code is a pure low-level tool primitive.
• Keep protocol projection and external provider request shaping in adapters.
• Keep product feature selection and delivery-profile decisions in assembly, not in execution primitives.
• Tool packs should describe provider groups and required services; concrete service access should flow through ports or typed runtime services.

Dependency Boundaries

• Execution primitive crates may depend on contracts and narrowly scoped provider-neutral DTOs owned by this layer.
• Execution primitive crates must not depend on assembly/core, src/apps, frontend code, Tauri APIs, or product-surface lifecycle.
• Dependencies on adapters are not allowed from this layer. New dependencies on services need an explicit boundary reason in the nearest module doc or PR description.