No real story is published without real consent.
The “Sara” example remains explicitly synthetic. The current public release contains no published real-user story, intentionally, until a pilot can collect auditable publication consent.
Rather than populate this page with fabricated testimonials, it stays empty until a verifiable, consented story exists.
Publication requirements
- Separate explicit consent for story/testimonial use.
- No student ID, transcript content, or unnecessary identifier is published.
- The participant reviews the final wording before publication.
- The story is not converted into a system-wide accuracy or success claim.
- Consent-withdrawal handling is documented in the approved pilot process.
What is technically ready?
The app has a separate Feedback/Testimonial consent flow when pilot analytics are enabled for a defined cohort. Collecting and publishing a real story remains a human/research process, not an automatically generated output.
Development evidence you can inspect
Inspect the source code, mapping rules, consent and withdrawal tests, encryption checks and evaluation plan. These are engineering artifacts, not employment outcomes or proof of recommendation effectiveness.
Project repository · Automated test history
Course-mapping coverage · Release history