Vibe-Coding Center / Field guide
Gather evidence before sharing
Keep a record of the actual journeys you tried, the results, and the decisions a school or project owner still needs to make. Unknowns stay visible.
Full reference
Launch review
Use this record with the full instruction files. It is not a compliance certificate. Use invented data for testing. Do not put secrets or student records in a public report.
Scope
- Project and source revision:
- Local preview or live deployment examined:
- Actual intended users, task, and age band:
- Reviewer and school decision owner, if needed:
What the application actually does
List inputs, storage, network destinations, sharing, exports, deletion, hosting logs, and third parties. Mark unknowns unverified. Include device storage and URLs even if there is no database.
Checks and evidence
For each row use verified, partially verified, unverified, or not applicable. Explain why. A scanner passing is not proof of full accessibility or security.
| Area | Status | Test and evidence | Remaining action / owner |
|---|---|---|---|
| Main educator/learner journey | Unverified | ||
| Keyboard navigation, focus, and recovery | Unverified | ||
| Phone layout, 200% text size, and 400% reflow | Unverified | ||
| Contrast, labels, headings, and alternative text | Unverified | ||
| Screen reader spot check | Unverified | ||
| Secrets, dependencies, and safe input rendering | Unverified | ||
| Access rules, sharing, and deletion where applicable | Unverified | ||
| Hosting, actual network calls, and vendor behavior | Unverified | ||
| School authorization, legal triggers, contracts | Unverified |
Decision
Choose and explain one:
- Ready for the reviewed scope, with evidence and explicit limits.
- Ready only as a prototype with invented data.
- Blocked for student data until listed controls and approvals are resolved.
Before release
List critical blockers, who can resolve them, and the verification needed. Identify tests not run. Separate engineering results from institutional or legal decisions.
After release
Verify the deployed main journey and downloads. Keep a recovery path and a person responsible for dependency updates, access changes, and future material feature reviews.