# Client agent spec template

This is a proposed starting artifact. Replace placeholders and resolve decisions before authorizing a release. Link detailed source inventories, tool contracts, and evaluation cases where needed.

- Agent: [name]
- Spec version: [version]
- Business owner: [person]
- Operator: [person]
- Job: [user and useful observable outcome]
- Non-goals: [work excluded from this release]
- Inputs: [required fields, optional fields, trusted identity]
- Sources: [approved source, policy owner, freshness and conflict rules]
- Outputs: [format, destination, completion evidence]
- Tools: [read, draft and write permissions; resources; preconditions]
- Approval: [who approves what; exact payload; expiry; changed-payload rule]
- Fallbacks: [missing data, conflicts, failures, unknown write outcome]
- Budgets: [time, attempts, spend; where limits are enforced; stop behavior]
- Acceptance: [requirement IDs, starting states, examples, evidence, release blockers]
- Operations: [logs, pause method, recovery and review owner]
- Open questions: [question, owner, blocks release yes/no]
- Sign-off: [approved version, approver, date, boundaries]

## Requirement and example

- Requirement ID: [R1]
- Given: [starting state]
- When: [event]
- Then: [observable result and prohibited effects]
- Implementation control: [configuration or integration that enforces it]
- Evidence: [what the reviewer checks]

## Change record

- Request: [proposed change]
- Affected requirement IDs: [IDs]
- New behavior and risks: [details]
- Updated cases and evidence: [links]
- Approver and release version: [person and version]