Capture a clean problem report
Name what you expected, what happened, when it happened, the exact page, the device, and whether the problem repeats. Remove passwords and private identifiers before attaching evidence.
Room 06 · Controlled guidance
The answer should
outlive the question.
Search clear public guidance. Every article declares its scope, keeps private data out, and remains eligible for correction or retirement when the product changes.
What our priority levels mean
P0 threatens safety, security, or total service. P1 blocks a critical journey. P2 materially degrades a journey with a workaround. P3 covers bounded defects, questions, and improvements.
Share evidence without sharing your life
Crop the view, remove unrelated names, hide account numbers, never include passwords, and tell us if the file contains information requiring restricted handling.
Read the case timeline
Every event should reveal what changed, who owns the next move, what is still unknown, and when the next update is due—even when no fix exists yet.
What counts as resolved
The original journey works, adjacent risk has been checked, the customer can verify the result, and the team records the cause or admits what remains uncertain.
Take your care history with you
A portable brief should include the problem, relevant versions, decisions, evidence references, work performed, outcome, and remaining obligations—without exposing internal secrets.
No guidance matches that search. Try the problem, product, or task instead of an internal code.