RETIREMENT / FICTIONAL ESTATE
Runtime change for a customer portal
Catalogue candidate; actual application scope still needs confirmation.
Next step: Review the vendor source and confirm the affected feature.
Needs reviewFICTIONAL EXAMPLE / NO ACCOUNT NEEDED
Four signals.
A working plan.
These examples show the review process, not findings from a live customer. Open a free workspace to explore the complete fictional scenarios.
CONFIGURATION / FICTIONAL ESTATE
Storage setting outside an approved baseline
Fictional setting observation; no public-object access has been proven.
Next step: Assign an owner and agree the change and validation plan.
PlannedVERSION / FICTIONAL ESTATE
Declared API version needs follow-up
A team-supplied declaration compared with a reviewed rule, not traffic discovery.
Next step: Check the callers, record a target version and retain test evidence.
Needs reviewACCOUNT NOTICE / FICTIONAL ESTATE
AWS Health scheduled change
Fictional resource-ARN match; no real AWS account was queried.
Next step: Review the private notice and agree the resource-specific follow-up.
OpenTest the workflow, including the awkward cases.
In a workspace, fictional scenarios include deviations, compliant settings and denied permissions. Unknown evidence stays unknown, a pass does not close the task automatically, and history remains attached to the review.
START WITH ONE USEFUL REVIEW
Give the next step an owner.
Try a fictional estate, review its evidence and prepare a report. No card or cloud connection needed.