Sections
Harness entities
The object map shows what is configured once, what is created for a run, and which records explain a decision.
Configuration
01Definition → Version
Role · Workflow · Policy
Run
02Run → Step → Work item
Agent · Assignment · Event
Decision
03Proposal · Claim · Evidence
Critique · Vote · Decision
Configuration
HarnessDefinition and HarnessVersion
A Definition is a named process template; a Version is an immutable snapshot of its schemas, graph, and policies. Every run always references one specific version.
AgentRole, WorkflowNode, and WorkflowEdge
A role defines an agent’s responsibility and boundaries. Nodes and edges describe task order, parallelism, conditions, review, voting, and human gates.
HarnessPolicy and ContextPolicy
Policies constrain tools, data, budgets, and confirmations. Context policy defines what a role may see and how it is retrieved.
During a run
- HarnessRun — one execution of a version with inputs, Flownix sources, and a budget/policy snapshot.
- AgentInstance and AgentAssignment — a concrete participant and its instruction.
- StepRun and WorkItem — step state and the lease through which an external agent receives, renews, completes, or releases work.
- RunEvent and Artifact — the immutable history and useful outputs of the run.
Deliberation and decision
A Deliberation groups Proposals, Claims, Evidence, Critiques, and DeliberationResponses. Ballot and Vote record a choice; Decision records its rationale and status. ApprovalRequest puts an important action in a person’s queue, while TaskPlanDraft and ProposedNode prepare the result for the Flownix tree.