Test 1 - Mike's Review

25.0Deployment approach: full or incremental, sandbox chain, who deploys to production, change windows, and release freezes.

25.1Build authority: complete the table in Part D so the agent knows what it may do alone, what needs approval, and what it may never do.

25.2Activation policy: Revenue Cloud components have draft, active, and inactive states. May the agent activate pricing procedures, constraint models, approval workflows, and object state definitions in sandboxes? In production?

25.3Test data: which records may the agent create, what naming prefix marks them, and is production data excluded or masked?

25.4Acceptance scenarios: at least five per unlocked module, in the Part D format.

25.5Regression: existing processes and integrations that must keep working.

25.6Rollback: how to revert (deactivate, restore a version, restore data), and what backup must exist before each data load.

25.7Logs the agent must produce: build log, assumptions list, and deviations from this questionnaire. State format and location.

25.8Stop conditions: when must the agent halt and ask (an unsupported feature, a limit exceeded, a contradictory rule, a failed acceptance test)?

25.9Deliverables: design document, data dictionary, admin runbook, and their formats.

25.10After go-live: who owns changes, how long is hypercare, and what is the defect response time?

25.11Salesforce release timing: any freeze around the next release, and will you test in a preview sandbox first?

25.12Who signs off, and on what evidence?