0.001% agent operator sheet

The frontier is not one framework. It is control over failure modes.

Use this page when building or studying agents. The strongest pattern is to begin with the low-level failure, then choose the smallest architecture that can control it.

Design laws

PatternWhen it matters
Workflow before agentIf the path is known, use deterministic code plus model calls. Add autonomy only where observations change the route.
Orchestrator-workerUse for breadth-heavy work where subproblems are independent and can return structured artifacts.
Evaluator-optimizerUse when there is a clear rubric, test, verifier, or judge that can drive iteration.
Tool ergonomicsA tool description is an interface contract. Bad schemas create bad reasoning.
Memory hygieneStore facts, plans, and artifacts separately. Treat retrieved memory as untrusted until checked.
End-state evalsJudge whether the environment reached the desired state, not whether the agent followed your expected path.
Security envelopeLeast privilege, approval gates, prompt-injection boundaries, traceability, and rollback.
Cost-aware scalingParallel agents buy performance with tokens. Use them only when the task value justifies it.

Frontier sources to keep current