Pi, Hermes, Fiitx, and OpenClaw roles
Understand the job boundary between prompt user, application developer, and Agent engineer.
Pi, Hermes, Fiitx, and OpenClaw roles
"Pi, Hermes, Fiitx, and OpenClaw roles" means turning the capability boundary among Pi Core, Hermes Worker, Fiitx Workbench, OpenClaw intake, and the agent engineer into an executable, observable, recoverable, and acceptable Harness unit. The direct output is not a prompt. It is role matrix, handoff contract, and ownership-conflict tests. The goal is to turn the concept into boundary, architecture map, engineering objects, code comparison, and acceptance evidence.
"Pi, Hermes, Fiitx, and OpenClaw roles" means turning the capability boundary among Pi Core, Hermes Worker, Fiitx Workbench, OpenClaw intake, and the agent engineer into an executable, observable, recoverable, and acceptable Harness unit. The direct output is not a prompt. It is role matrix, handoff contract, and ownership-conflict tests.
It does not make the model "think harder" and it does not hide every behavior inside a chat wrapper. It defines Role ownership so Learning goal to engineering task, Agent Harness control plane, and Role matrix, deliverable list, and acceptance evidence can be traced.
If the implementation causes "Mixing prompts, app UI, and agent runtime into one vague idea", the boundary is not established. Go back to input contract, policy, or runtime and split it again.
Done means delivering role matrix, handoff contract, and ownership-conflict tests, preserving Role matrix, deliverable list, and acceptance evidence, and reviewing it through Can explain who owns context, tools, policy, and delivery.
Mermaid source
flowchart LR
input["Input Contract"] --> boundary["Role ownership"]
boundary --> route["Learning goal to engineering task"]
route --> runtime["Agent Harness control plane"]
runtime --> policy{"Policy"}
policy -->|allow| tool["Model and Tools"]
policy -->|block| blocked["Mixing prompts, app UI, and agent runtime into one vague idea"]
tool --> state["State and Events"]
runtime --> state
state --> evidence["Role matrix, deliverable list, and acceptance evidence"]
evidence --> artifact["role matrix, handoff contract, and ownership-conflict tests"]
artifact --> eval["Acceptance"]
classDef inputNode fill:#eef4ff,stroke:#4664ff,color:#0b1220;
classDef runtimeNode fill:#ecfdf5,stroke:#10b981,color:#0b1220;
classDef gate fill:#fff7ed,stroke:#f59e0b,color:#0b1220;
classDef stop fill:#fee2e2,stroke:#ef4444,color:#0b1220;
class input,boundary,route inputNode;
class runtime,tool,state,evidence,artifact,eval runtimeNode;
class policy gate;
class blocked stop;| Framework | Useful design | How this lesson uses it |
|---|---|---|
| Hermes | Entry points, AIAgent, tool dispatch, Session Storage, Gateway/Cron | Judge whether Learning goal to engineering task has long-running and delivery boundaries |
| Pi Agent Core | AgentSession, event stream, resource loader, compaction, save point | Implement Agent Harness control plane and a recoverable turn lifecycle |
| Fiitx | Workbench, progress stream, approval UI, model routing, history replay | Expose Role matrix, deliverable list, and acceptance evidence as a visible control plane |
| Eval | Done criteria, trace, failure case, regression | Prove role matrix, handoff contract, and ownership-conflict tests meets acceptance criteria |
A plain LLM call returns an answer. A Harness run carries goal, boundary, tools, policy, and acceptance as parameters.
// Plain LLM call: returns text without boundary, state, or acceptance
const answer = await model.generate({
prompt: "Implement: Pi, Hermes, Fiitx, and OpenClaw roles"
});
// Agent Harness 写法:把目标、工具、策略、状态和验收写进运行合同
const result = await harness.runHarnessOrientation3RoleSplit({
lesson: "0.3 Pi, Hermes, Fiitx, and OpenClaw roles",
goal: "Implement: Pi, Hermes, Fiitx, and OpenClaw roles",
boundary: "Role ownership",
runtime: "Agent Harness control plane",
route: "Learning goal to engineering task",
tools: runtime.tools.forBoundary("Role ownership"),
policy: {
watch: "Mixing prompts, app UI, and agent runtime into one vague idea",
requireEvidence: true
},
eval: [
"trace_complete",
"artifact_exists",
"policy_checked",
"harness_orientation_3_Role_split_accepted"
]
});
assert(result.artifact === "role matrix, handoff contract, and ownership-conflict tests");
assert(result.evidence.includes("Role matrix, deliverable list, and acceptance evidence"));Key points
- 1
Definition: "Pi, Hermes, Fiitx, and OpenClaw roles" means turning the capability boundary among Pi Core, Hermes Worker, Fiitx Workbench, OpenClaw intake, and the agent engineer into an executable, observable, recoverable, and acceptable Harness unit. The direct output is not a prompt. It is role matrix, handoff contract, and ownership-conflict tests.
- 2
Boundary: It does not make the model "think harder" and it does not hide every behavior inside a chat wrapper. It defines Role ownership so Learning goal to engineering task, Agent Harness control plane, and Role matrix, deliverable list, and acceptance evidence can be traced.
- 3
Code: a plain call gets answer; a Harness call must return artifact, evidence, and trace.
- 4
Acceptance: deliver role matrix, handoff contract, and ownership-conflict tests, preserve Role matrix, deliverable list, and acceptance evidence, and guard against "Mixing prompts, app UI, and agent runtime into one vague idea".