Pre-Launch Audit & Bugfixing — AI Platform

Nova — Full Platform QA, UX, Integration & Security Review Deadline: Tuesday afternoon, 1 September 2026 Final changes reviewed and implemented Tuesday evening, so the platform is ready on Wednesday. Objective Nova is a Dutch AI platform that combines multiple AI-powered features and integrations within one environment. The platform has already been built. At this stage, we need a complete end-to-end review of the entire platform before final release. The goal is not to rebuild Nova, but to thoroughly test everything, identify problems and fix them directly, and provide clear feedback on anything that still requires attention. 1. Full Platform Test Please test Nova from the perspective of a real user. Go through the entire platform from start to finish, including: • Account creation / sign-up • Login and logout • Password/account flows • Onboarding • Dashboard • Navigation • User settings • Every AI feature • Every input field • Every button • Every menu • Every page • File uploads/downloads, where applicable • Loading states • Empty states • Error states • Notifications • User history/data, where applicable • Mobile/responsive behaviour • Different realistic user flows Do not only test the "happy path." Try incorrect inputs, unexpected actions, repeated actions and edge cases. The objective is to find anything that could confuse a user, fail technically or make Nova feel unfinished. 2. Test Every AI Feature Every AI function within Nova must be tested individually. For each feature, check: • Does it actually work? • Does it produce the expected output? • Are responses relevant and reliable? • Are prompts/instructions correctly passed to the AI? • Is context maintained correctly where required? • Are conversations or user sessions properly separated? • Are loading times acceptable? Nova — Pre-Release Review Brief · Deadline 1 September 2026 1 • Are errors handled correctly? • What happens if the AI/API is unavailable or times out? • What happens with very short, long or unusual input? • Are usage limits handled correctly? • Are there duplicate requests or unnecessary API calls? • Are there situations where the user receives no response? • Is the output presented correctly in the interface? Please actively try to break each feature rather than simply confirming that the standard use case works. 3. Integrations & API Connections Check all external and internal integrations used by Nova. For every integration, verify: • API connection • Authentication • Missing permissions • API requests/responses • Error handling • Timeouts • Rate limits • Expired credentials/tokens • Failed requests • Retry behaviour • Webhooks, if applicable • Data mapping • Frontend/backend communication Check the browser console, network requests, application logs and backend errors where relevant. We need to know not only whether an integration works normally, but also what happens when it fails. 4. UX / Usability Review Review Nova as if you were using the platform for the first time. Look critically at: • Is it immediately clear what Nova does? • Is navigation intuitive? • Can users understand every AI feature without explanation? • Are buttons and calls-to-action clear? • Are there unnecessary steps? • Are there confusing screens? • Is terminology consistent? • Is important functionality difficult to discover? • Are error messages understandable? • Are success states clear? • Is the interface responsive and consistent? • Does the platform feel fast? • Does anything make the product feel unfinished? Please flag anything that creates friction. If a small UX improvement is obvious, low-risk and does not change the intended product behaviour, you may implement it. For larger UX changes, document the recommendation first. 5. Security & Data Protection — High Priority Preventing data leakage is critical. Please perform a security-focused review of the platform, especially around user data and AI/API integrations. Check for: • Data being exposed between different user accounts Nova — Pre-Release Review Brief · Deadline 1 September 2026 2 • Incorrect authorization/access controls • Users being able to access another user's conversations, files or information • Sensitive information appearing in URLs • Sensitive information exposed in frontend code • API keys or secrets exposed client-side • Secrets accidentally stored in the repository • Incorrect database permissions • Authentication/session weaknesses • Insecure API endpoints • Missing server-side authorization checks • File upload vulnerabilities • Unsafe handling of user-generated input • Injection risks • Cross-site scripting (XSS) • CSRF risks where applicable • Incorrect CORS configuration • Sensitive information being written to logs • Excessive personal data being sent to third-party AI/API providers • Data being retained unnecessarily • Production/debug information being exposed to users • Error messages leaking technical or sensitive information Pay particular attention to tenant/user isolation. A logged-in user must never be able to retrieve another user's private data simply by changing an ID, URL, request parameter or API call. Do not perform destructive testing against production data. If a security test could damage, delete, expose or modify real user data, stop and report it instead. If you discover a serious security vulnerability or possible data leak, report it immediately rather than waiting for the final report. 6. Performance & Reliability Check the general performance of Nova. Look for: • Slow pages • Slow AI responses • Backend errors • Memory/resource issues • Unnecessary API requests • Duplicate requests • Large frontend assets • Failed requests • Console errors • Poor loading behaviour • Features that fail after repeated usage • Race conditions or inconsistent state • Refresh/session issues Where possible, identify the actual cause rather than only reporting that something feels slow. 7. Cross-Device / Browser Testing At minimum, check the platform on desktop, mobile, different screen sizes, Chrome, Safari, and Edge or Firefox. Check responsive layouts carefully. Nothing important should disappear, overlap, become unreadable or become difficult to use. 8. Fix Issues Directly Nova — Pre-Release Review Brief · Deadline 1 September 2026 3 When you find a problem, solve it directly rather than only reporting it. For every issue you fix, note what was wrong and what you changed. For anything involving architecture, authentication, database structure, security, permissions, production infrastructure, major UX changes, or significant changes to AI behaviour: report the issue and proposed solution before making a potentially risky change. Do not introduce major last-minute changes that could destabilise the platform. 9. Regression Testing After making fixes, retest the affected functionality. A fix is not considered complete simply because the original error disappeared. Verify that: 1 The original problem is solved. 2 Related functionality still works. 3 No new frontend/backend errors were introduced. 4 Mobile behaviour still works. 5 Authentication and permissions remain correct where relevant. 10. Required Final Report By Tuesday afternoon, 1 September 2026, please provide a concise but complete report. For every issue found, include: • Issue — What is wrong? • Location — Where does it occur? • Severity — Critical / High / Medium / Low • Category — Security / Bug / Integration / AI / UX / Performance / Other • How to reproduce — Exact steps needed to reproduce the problem. • Expected behaviour — What should happen? • Actual behaviour — What currently happens? • Fix applied — What did you change? • Status — Fixed / Not Fixed / Needs Decision For fixes that you implement, please also mention what was changed. Priority Order Please work in this order: 1 Security / potential data leaks 2 Authentication and user/data isolation 3 Broken core functionality 4 AI features 5 API/integration failures 6 Critical UX problems 7 Performance/reliability 8 Responsive/mobile issues 9 Minor UI/UX improvements A visually imperfect element is less important than a security issue, broken AI feature or failed integration. Definition of Done The review is complete when: • All major user flows have been tested. • Every AI feature has been tested. • All important integrations have been verified. • Authentication and user isolation have been checked. Nova — Pre-Release Review Brief · Deadline 1 September 2026 4 • No known critical data-leak issue remains unresolved. • Critical and high-priority bugs are fixed; anything left unfixed is clearly explained. • Major mobile/desktop flows work correctly. • Fixes have been regression-tested. • A final issue report has been delivered. The main question we need answered at the end is: "Is Nova technically, functionally and from a security/UX perspective ready to be released on Wednesday?" If the answer is no, clearly identify exactly what is blocking the release. Please prioritise stability and security over last-minute cosmetic improvements.