Stop drawing the graph: reactive agents over typed, versioned artifacts
说明与用途
reactifact 运行时允许代理声明它们消耗和产生的类型化工件,自动连接代理,无需手动绘制图形,简化维护并提供可追溯性。
问题
Knowledge‑agent queries often require multiple data sources (Confluence, GitLab, CSVs) and manual orchestration; maintaining a hand‑drawn graph of agent edges becomes brittle as question paths change.
结果
By declaring artifact types and consumption/production contracts, the system automatically composes agents without explicit graph wiring, reducing maintenance overhead and improving provenance tracking.
工作流
- Define typed artifact models (Question, Evidence, Answer).
- Decorate agent functions with @produce to declare produced artifacts.
- Create agents with consumes and produces lists (e.g., search_agent consumes Question, produces Evidence).
- Instantiate Runtime with agents and budget.
- Create initial Question artifact in Context.
- Run the runtime; agents react automatically based on artifact availability.
- Retrieve Answer and related Evidence from Context for provenance.
- Print or use the answer and evidence.
证据
You don't draw a path from A to B. You declare, per agent, what it consumes and what it produces — typed artifacts, not string blobs in a shared dict.
search_agent and answer_agent both react — nobody wired them together
- 记录日期: 2026-09-16T04:30:29.198Z