Make authority and remedy explicit
On this page
Make authority and remedy explicit
Governance supports every business workflow. Use this page before delegating a job, including qualifying an enquiry. The recipe explains how to assess it; this check determines which actions are permitted. Neither a recipe nor tool access supplies consent.
Define what your agent may do
Write a short mandate with the human owner before the first test:
- Purpose and input: one named job, the permitted information, and its source.
- Permitted action: what the agent may produce or change, with a time or resource limit.
- Approval boundary: what needs a fresh human decision, including contact or commitments.
- Stop and recovery: who stops the run, what triggers a stop, and how to recover or discard a draft.
- Review: who checks the result, what evidence they need, and when they decide the next step.
For the enquiry practice, permit one draft from synthetic text only. The human sales owner decides qualification; no contact, enrichment, live updates, or promises are included. If any required authority is unresolved, pause and ask the owner rather than expanding access.
Return to the qualification method once its boundaries are clear, or scope an Action test when another recipe is ready. The mandate travels with the method and its output.
Decision: Who may decide, delegate, commit, constrain, stop, and remedy the work? Governance matters because technical capability does not create consent, legitimacy, or accountable judgment.
Smallest useful move: name the human decision owner, permitted action, approval threshold, protected constraint, stop mechanism, and remedy before expanding exposure. Run a bounded move only within that authority and review its consequences with exceptions, harms, escalation, and recovery. This is a family scaffold, not legal or regulatory advice.