Agent contract
Job, allowed inputs, tools, actions, exclusions, and escalation.
Production AI agents · Europe
I build focused agents for research, knowledge retrieval, support, reporting, and operational follow-up. The system is designed around approved context, bounded actions, evaluation, logs, and a person who remains accountable.
Direct answer
A production AI agent has a defined job, controlled access to data and tools, representative evaluations, observable actions, explicit approval points, and a recovery path. The model is one component. Reliability comes from the surrounding software: retrieval, permissions, state, deterministic checks, logging, and an interface that shows uncertainty instead of concealing it.
When this helps
What the work covers
The build covers the complete path from source to action and from failure back to a responsible person.
Job, allowed inputs, tools, actions, exclusions, and escalation.
Retrieval, APIs, credentials, permissions, and state.
Representative cases, quality criteria, red-team cases, and regression tests.
Logs, traces, cost limits, approval, fallback, and documentation.
Compare the options
| Pattern | Best when | Risk |
|---|---|---|
| Deterministic automation | Rules and inputs are stable. | Poor fit for ambiguous inputs. |
| Single AI step | One classification, extraction, or draft can be reviewed. | Context and quality still need evaluation. |
| Agent workflow | The task requires tools, state, branching, and bounded judgment. | More autonomy increases testing and operating cost. |
| Human service | The decision is consequential, rare, or depends on tacit trust. | May be slower, but accountability remains clear. |
How the work runs
Write the successful outcome, prohibited actions, and escalation rules.
Connect approved sources and tools with least-privilege access.
Run representative and adversarial cases before granting actions.
Observe real use, review failures, and widen the boundary only with evidence.
Relevant work
The system combines reader preferences, LinkedIn enrichment, research, review, and publication. It treats the agent as part of a product and operating workflow rather than a chat window.
FAQ
Model choice follows the task, data, latency, tool use, evaluation results, and operating budget. The system should allow a model to be replaced without rebuilding everything.
Yes, through explicit sources and permissions. Access should be least-privilege, logged, revocable, and separated by user or organisation where required.
No single technique prevents every error. Grounding, citations, structured outputs, deterministic checks, abstention, evaluation, and human review reduce the risk.
Yes, but action permissions should begin narrow. Consequential actions normally require confirmation, limits, and an audit trail.
Cost depends on model calls, context size, retrieval, tool use, volume, retries, and monitoring. I estimate the operating envelope before recommending production use.
A bounded job, not an AI employee
I will help define whether the right answer is an agent, a smaller AI step, deterministic automation, or no build at all.
Discuss the agent