AI Playbook
Post-change validation
Compare observed post-change state with the approved change plan and expected outcomes.
Copy this prompt
Replace the bracketed values, then paste it into an AI client connected to Stackyapper.
Run the "Post-change validation" playbook using Stackyapper.
Inputs
- change request: [Approved change ticket identifier]
- validation window: [Optional bounded post-change observation window] (optional)
Objective
Compare observed post-change state with the approved change plan and expected outcomes.
Required evidence
- Service tickets
Use when available
- Ticket history
- Managed devices
- Device alerts
- Device activity
- Identity configuration
- Identity security
Procedure
1. Load the approved scope, expected result, validation steps, and rollback threshold.
2. Collect post-change ticket, device, alert, activity, configuration, and security evidence.
3. Compare expected and observed state and recommend accept, monitor, remediate, or roll back.
Return
- Expected state
- Observed state
- Validation result
- Regressions or residual risk
- Recommended disposition
Use only evidence available through the Stackyapper Apps and permissions connected to this AI client. If required evidence is unavailable, say what is missing before continuing. Do not guess or make changes in connected systems.Before you paste
Replace every bracketed value in the prompt. Delete an optional input line if it does not apply.
change request: Approved change ticket identifier. (required)validation window: Optional bounded post-change observation window. (optional)
What Stackyapper will use
The exact tools depend on the Apps connected to your workspace and the current user's permissions.
- Service tickets (required)
- Ticket history (used when available)
- Managed devices (used when available)
- Device alerts (used when available)
- Device activity (used when available)
- Identity configuration (used when available)
- Identity security (used when available)
What you'll get
- Expected state
- Observed state
- Validation result
- Regressions or residual risk
- Recommended disposition
How it works
- Load the approved scope, expected result, validation steps, and rollback threshold.
- Collect post-change ticket, device, alert, activity, configuration, and security evidence.
- Compare expected and observed state and recommend accept, monitor, remediate, or roll back.