The twelve factors
Define the outcome, execute within authority, check the exact output, then use what you learned to improve the next cycle. Operating principles, not twelve mandatory steps.
Brief the Agent
Intent, sources and a bounded job.
Lay the Rails
Authority, methods and write ownership.
Gate the Work
Checked outputs, preserved behavior and memory.
Govern the Loop
Caller control, stopping boundaries and feedback.
How well research backs each factor.
Each essay cites its sources and says how strong they are. Some rules have been tested directly. Others are practice the research only points toward.
Measured
Studies test the claim behind the rule directly.
Supported
Studies support the reasoning. The claim behind the rule has not been tested head-on.
Practice
Engineering practice. Agent research supports it only indirectly.
Every essay follows the same job.
Draft a monthly operations report from an approved ledger. Reconcile totals, cite claims, exclude personal details and get operator approval before publishing.
The same terms apply when the output is an investigation, a document, an operational action or a code change.
- Intent
- The caller’s accepted outcome, examples, scope and authority.
- Work item
- A bounded assignment with status and dependencies in the existing tracker.
- Output
- The exact candidate result: a report, finding, document, action or code change.
- Checks and judgment
- Checks establish facts; independent judgment evaluates meaning where risk requires it.
- Acceptance and memory
- The caller’s policy decides acceptance; linked records and supported findings inform later work.
See the factors at work.
AgentOps is the reference implementation. Install it and run one read-only Research task in a repository you already work on.