01Build for people who must make and defend real security decisions
Begin here when you need to find genuine open roles and working principles. Stay with the domain, relationship or service state named on the page; the task does not widen silently into a different security or product claim.
02Prefer evidence provenance over dramatic but unsupported language
Use the visible product state and named recovery action. A missing result does not mean that an assessment, payment or account change succeeded; wait for an explicit outcome or contact support with the correlation reference.
03Keep customer exposure separate from provider and shared-platform context
Complete the step shown on the page, then check the resulting state before moving on. Unknown, unavailable and not-applicable outcomes remain distinct, so absence is never presented as a successful or reassuring result.
04Use product feedback to improve comprehension without weakening safeguards
Use product feedback to improve comprehension without weakening safeguards. Record the resulting owner, evidence or recovery state where the product provides it, so another person can verify what happened without repeating the task.