The Agent Record is the unit of management in this Standard. One record exists per agent in production.
The Record is not a replacement for a vendor agent registry. It is the management layer above it. Identity fields can generally be sourced from a registry. Accountability and governance fields cannot, because no registry currently holds them.
| Block | Fields | Required at |
|---|---|---|
| Identity | 1 to 8 | Level 1 |
| Accountability | 9 to 14 | Level 2 |
| Governance | 15 to 19 | Level 3 |
1. Agent ID. A unique, persistent identifier assigned by the organisation. MUST NOT be a vendor-assigned identifier alone, because agents migrate between platforms and vendor identifiers do not survive migration.
2. Name. Human-readable, unique within the estate.
3. Purpose. One sentence stating what the agent does, written so a person outside the delivery team understands it.
4. Runtime. The platform the agent executes on. Where an agent spans runtimes, all MUST be listed.
5. Date entered production. The date the agent first met the definition in 1.3. Not the build date and not the pilot start date.
6. Status. One of: in production, under review, suspended, retired.
7. Business unit. The unit whose work the agent performs. Where an agent serves several, the accountable unit MUST be identified.
8. Technical owner. Named individual accountable for the agent functioning.
9. Business Owner. Named individual per 1.7. A team, role, committee or distribution list MUST NOT be recorded in this field.
10. Stated outcome. The business result the agent was funded to produce, in the terms its Business Owner would use with their own leadership.
11. Baseline. The pre-agent cost, time, volume or quality of the same outcome. Where no baseline was captured before deployment, this field MUST record "not captured" rather than a retrospective estimate.
12. Cost per successful outcome. Total cost of operation divided by count of successful outcomes over a stated period, with the measurement method recorded alongside. Operating cost includes inference, orchestration, human review, exception handling and monitoring. At Level 2 an estimate is permitted where flagged as such and produced by a consistently applied method. At Level 3 the figure MUST be measured.
13. Autonomy level. One of: assistive (proposes, human acts), supervised (acts, human approves), autonomous (acts, human notified).
14. Escalation point. Named individual or on-call function receiving escalation when the agent fails or behaves outside expectation, reachable within a stated response time.
15. Promotion evidence reference. Pointer to the record demonstrating the agent met the criteria in 5.2.
16. Review triggers. Thresholds against the five control surfaces which, when breached, move the agent to under review without waiting for the scheduled cycle.
17. Last review date and decision. Date, and one of: continue, remediate, demote, retire.
18. Retirement criteria. The conditions under which this agent should be withdrawn. MUST be defined at promotion, not at first review.
19. Next review due. Date, set per the cadence in 5.3.
An organisation MAY record vendor, underlying models, cost centre, dependent agents, regulatory classification, data classification, incident history and version.
None are required. A Record carrying every optional field and lacking field 9 conforms at no level.
Fields 1 to 8 can be substantially populated from an existing agent registry. Appendix D provides field mappings for the major platforms.
Fields 9 to 19 cannot be sourced from any registry currently available, because they record business accountability, economics and governance decisions rather than technical identity.
This division is why this Standard exists. Discovery has been solved. What the discovered list is for has not been defined.
2.7.1 A Record MUST be updated within ten working days of a change to any required field.
2.7.2 A Record MUST NOT be deleted on retirement. Status changes to retired and the Record is retained.
2.7.3 Where a required field cannot be populated, the Record MUST state the reason rather than remain blank. A blank field and a knowingly unavailable field are different conditions and an assessor MUST be able to distinguish them.
