STARTING A RUN

CHAPTER SUMMARY A run is one complete attempt at one task, and it is the basic unit of tracking and accounting. Task intake receives, validates, and structures the request into a goal object, and asks for clarification when ambiguity would be risky. Instruction assembly combines system rules, project conventions, the structured request, and environment facts, with a clear priority order for conflicts. Before the first model call, the harness must initialize logging, permissions, budgets, and state, in an order that ensures every guardrail exists before any action is possible. KEY TERMS REVIEW Run: one complete attempt by an agent to accomplish one task. Task intake: receiving, validating, and structuring the user's request. Goal object: a structured description of the goal, constraints, inputs, and expected output. Run identifier: a unique label attached to every record of a run. Least privilege: granting only the permissions actually needed. Auditing: reviewing records after the fact to confirm proper conduct.