Waiting on a decision, not on writing time
What is missing before this page can be written
- Missing
- The named safety owner. Mike resolved the intake route on 2026-08-05, reports enter through general support with safe internal escalation, so only the ownership naming and the confidential-handling confirmation remain.
- Who can answer it
- Ivo, and possibly legal
- Recorded as
- AR-017 decision 1 · AR-006 · manifest v3 gap register
- Planned release
- Wave 1, target 2026-10-31
Nothing on this page is invented. The structure, the customer questions, and the routes are real; the answers stay blank until the owner above supplies the fact.
The questions this page has to answer
Taken from the FAQ export and the gap register. The questions are known; the approved answers are what is waiting.
- How do I report content?
- What happens after I report something?
- Is my report handled confidentially?
The shape it will take
The eleven-part article template from blueprint v3, section 9. Every launch article uses it, so the structure can be reviewed and designed now.
Action-oriented, in the customer's words.
One sentence, outcome first.
Product, account state, device, region, or route this applies to.
The short checklist that prevents a failed attempt.
Numbered steps, one action per step.
What the customer should see when it worked.
The exception paths, in the order customers hit them.
The details to gather first, so the first support reply can resolve it.
Liss, human, processor, shop, or safety, whichever fits the problem.
The parent heading and the neighbouring articles.
Source, owner, last-updated date, review cadence, internal tags.
If you need help with this right now
While this page is being written, the working routes are unchanged. Ask Liss from the Help Hub, or contact VOD support with the account email, what happened, when, and what you already tried.
Never send a password or a full payment-card number.