Context
Reads submitted contract documents and an approved clause library. It has no authority to send messages externally, approve language, or finalize a record.
CONSTRUCTED EXAMPLE
A generic enterprise legal operations team is preparing an agent that reviews submitted contracts and flags non-standard clauses for human review.
Free to read and cite with attribution to Sougata Roy and sougataroy.com. Do not republish, rebrand, or claim authorship of any framework, term, or model as your own.
Filled authorization record
This scenario is constructed for explanation. It is not a real organization and is not drawn from an engagement.
Context
Reads submitted contract documents and an approved clause library. It has no authority to send messages externally, approve language, or finalize a record.
Intent
Authorized to identify clause variance and route a review note to Legal Operations. Explicitly prohibited from approving, rejecting, editing, or sending a contract.
Governance
Consequence Owner: Head of Legal Operations. Review cadence: quarterly and whenever scope, data, regulation, or ownership changes. Escalation: stop the agent, open an incident, and notify the owner.
Output
Authorization record signed before production deployment.
How to use this page
Compare this completed record with the primary framework, then use the blank template to document a real agent. The example demonstrates the level of specificity expected; it does not replace organization-specific authorization.