Why this decision matters
Review architecture, interfaces, permissions, logs and rollback paths before adding AI through bounded modules, APIs, plugins or staged changes.
Existing stable systems should not be rebuilt by default. Reuse data, identity and workflows where the interfaces and operational boundaries support safe integration.
Conditions to confirm before development
- Architecture, database, deployment and available interface scope
- Users, roles, departments and data permissions
- Read-only, assistive or automated positions in the workflow
- Logging, monitoring, gradual rollout and rollback requirements
Implementation and delivery approach
Start with low-risk search, Q&A or content processing, then expand only after integration and regression evidence is available.
Retain interface baselines, permission tests, regression results, performance impact and rollback records.
Acceptance boundary
This guidance applies to the agreed data, system and environment. Project-specific scope, dependencies and acceptance conditions must be confirmed separately.