Context, control, and security

A Harness must be useful but bounded: roles see only needed context, risky operations require approval, and budget and audit remain observable.

Context and isolation

A ContextPolicy specifies included sources: run input, Flownix nodes, the previous round, or assigned material only. It also excludes sensitive paths, bounds volume, and can anonymize authors. Do not give agents the entire project by default.

Policies and budgets

Policies

Allow, deny, or require-approval rules apply to tools, data, execution, voting, privacy, and retention.

Budgets

Limits for duration, rounds, model calls, tokens, cost, tools, and parallel agents must stop a run predictably.

Reliability

Optimistic locking, idempotency keys, ordered events, and leases prevent duplicate application and explain what happened after repeated delivery.

Audit and protection

RunEvent creates a timeline, Artifact holds useful output, and capabilities split read, write, start, participate, vote, and approval permissions. Data from code and documents is untrusted and must not be executed as instructions without an explicit policy.