External review pack
EQAI Review
Use this page as the short walkthrough for the current EQAI experience. It lists the review path, verified capabilities, known limitations, and open product questions for reviewers.
Walkthrough path
Home
Confirm the bilingual landing page, core mission, category cards, and embedded assessment guide.
Assessment catalog
Browse six static assessments and filter by Work, Personal, Kid, or Pet.
MWI assessment
Open an assessment detail page and confirm the non-diagnostic boundary.
Contact form
Submit assessment interest, partnership, research, or review feedback into the insert-only intake flow.
Records
Sign in with a reviewer account to inspect private started and completed records.
Verified capabilities
Assessment discovery
Unified directory, category entry points, structured API routes, and dataset fallback are implemented.
Response flow
Signed-in users can start an assessment, answer bounded 1-7 items, save a total score, and review the result.
Contact intake
The contact form saves submissions in the current browser for static hosting review.
Privacy and terms
Privacy Policy and Terms of Service routes exist before the contact form collects submissions.
Known limitations
Formal assessment boundary
The current scales are informational tools for personal reference, not formal psychological instruments.
No admin inbox yet
Contact submissions stay local in the browser for this static version; a staff-facing dashboard is intentionally deferred.
No payment or donation flow
Donate remains deferred until payment, compliance, and public-benefit positioning are confirmed.
Review assets
Screenshots and a short recording should be captured from the verified production-like build before external review.
Open product questions
Formal assessment roadmap
Which assessments should be expanded first, and what validation evidence is required before public claims expand?
Child data posture
What consent, retention, and parent/guardian flows are required before kid-related experiences collect real data?
Reviewer workflow
Should review feedback stay in the contact intake table or move to a dedicated reviewer workflow?