Start with the task
Choose a provider around the work and the information it needs, rather than assuming one model is right for every task. Describe the desired result, the evidence available and the review boundary. A model’s output should remain a draft when the result has not been checked.
Review the data boundary
Decide what may leave the workspace and under which provider terms. Credentials must stay out of prompts, public forms and source code. A task should receive only the context it may use; permission to connect an account is not authority to expose every record in it.
Agree usage before execution
Keep provider charges separate from a workspace offer or an implementation quote. The responsible person should understand what is authorised and what happens when the agreed boundary is reached. Unknown cost is still unknown; it should not be presented as an accepted spend or an invoice.
Verify the real path
A protocol test with synthetic responses is useful engineering evidence, but it does not prove a live provider connection. Review a real permitted result, errors and revocation before describing the workflow as operational. No provider is activated by reading this guide.