Enforce least privilege
Start by naming the operational outcome and the people affected. Separate technical preferences from explicit business constraints. Define what a successful change would look like in normal operation and when things go wrong.
Treat retrieved text as untrusted
Use a concrete scenario to test the proposed approach: A document uploaded by a user might contain instructions asking the assistant to ignore access policies. Application authorisation must not be delegated to model judgment.
Minimise sensitive data
Architecture decisions should explain data ownership, security boundaries, error behaviour, ongoing maintenance and the cost of change. Use server-side access checks, separated tool permissions, input and output validation, tenant isolation and carefully scoped logging. Evaluate prompt injection and data leakage scenarios regularly.
Test adversarial inputs
Before rollout, agree on acceptance criteria, monitoring and a method for reviewing the result with real users. Capture known limitations and next steps instead of presenting early assumptions as delivered outcomes.
What to decide next
Build a small decision record: the business problem, options considered, key assumptions, security and integration implications, expected operating costs and success measures. A focused discovery discussion will usually expose the highest risks before significant delivery commitments are made.
Explore UAZO Tech’s related engineering approach, or discuss a project challenge.