Start with a bounded task, a clear reviewer, and a way to recover from mistakes.
Choose the decision boundary
Write down what the system can read, draft, recommend, and change. A draft reply and a sent reply have different consequences. Define which actions require a person to approve the exact result, and who is responsible for handling exceptions. Begin with one task whose output you can assess.
Define the data boundary
List the information needed for the task and the destination where it would be processed. Check provider settings, retention, contractual requirements, and the permission to use the data before connecting live records. Prefer sanitized examples for early development. Public availability alone does not establish permission for every reuse.
Treat retrieved content as input
Messages, webpages, and uploaded documents can contain instructions that conflict with your workflow. OWASP identifies prompt injection as a risk when model inputs affect behavior unexpectedly. Use narrowly scoped permissions, deliberate approval steps, and controls outside the model; a prompt alone is not an authorization system.
Test ordinary and difficult cases
Create a small representative set of examples with expected outcomes. Include missing information, ambiguous instructions, stale records, and an attempted instruction embedded in source content. Measure review effort and errors as well as speed. Record the model, configuration, and integration behavior so later changes can be checked.
Operate with a fallback
Define when the workflow stops, hands the task to a person, or retries. Make actions reviewable, provide an off switch, and keep an agreed recovery path for failed changes. Recheck permissions and examples when the workflow, data source, or model changes.
Your first worksheet
- Describe one bounded task and an accountable owner.
- Specify approved inputs, destinations, and permissions.
- List actions requiring a person’s approval.
- Test examples and failures before enabling live writes.
Further reading
These links support the referenced technical topics; the worksheet and planning questions are Ciphrus editorial guidance.