A person stays in control

Quasar's own workflow, which an organization can adopt and adapt, encodes how an agent should work:

• Plan before coding. Before an issue can move to In progress, the agent records a pre-analysis: the plan, and the files it examined with their checksums. If those files change before the work starts, the plan shows as stale.
• Status tells the truth. The issue moves to In progress before the first edit, so whoever supervises sees where the work is.
• Time is measured, then confirmed. The agent opens a work session at the start of each turn and closes it at the end. Quasar's own clock stamps both. A session becomes a work log only when a person confirms it.
• Acceptance is a person's. The agent contract tells an agent to accept a document or a release revision only on a person's explicit word. Every acceptance records whose key made it and whether an agent acted. To keep an agent from accepting at all, give it a key whose owner is not a project lead.
• The code is followed, not trusted. Quasar reads where each issue's code actually is in the repository, from the issue key in commit subjects, instead of taking the agent's word for it.