Required review gates
| Area | Current status | Required before launch |
|---|---|---|
| Assessment and claims | Internal development package only | Named qualified construct/content reviewer and approved public claims |
| Privacy and legal | Implementation-aligned drafts | Operator details and named counsel/privacy review receipt |
| Accessibility | Engineering checks in progress | Named manual reviewer and resolved core-flow findings |
| Editorial psychology content | No launch articles published | Truthful authors, appropriate reviewers, citations, and review dates |
Why this is public.
Attractive product language can make a development artifact look more authoritative than it is. Publishing the review boundary keeps credentials, validation, and legal approval from being inferred where they do not exist.