Foundation stage · Module 1 of 15
Outcome for this lesson
Choose one small course project and use the describe, build, inspect, test, and refine loop responsibly.
Bring forward: No prerequisite. Bring a small problem you understand well.
Produce: A one-sentence project outcome, intended user, important constraint, and failure case.
0 of 15 core modules complete
Progress is saved on this browser. Create a free membership to sync across devices.
Foundation stage
Build the next result
This module gives you a safe starting point and one small project to carry through the entire course. Do not begin with a platform, a high-risk workflow, or a promise of income. Begin with a problem you understand and a result you can observe.
Your result for this module
A one-sentence project outcome, intended user, important constraint, and failure case.
Continuous case study
Course case study: Freelancer Follow-Up Tracker
Throughout the course, the worked example is a small tracker for a freelancer who wants to record a new inquiry and see the next follow-up date. It is narrow enough to test and useful enough to reveal requirements, privacy, accessibility, cost, and business decisions.
Do the work
Choose one user and moment
Name one person or role and the moment the tool should help. Example: a freelancer immediately after receiving a new inquiry.
State one observable result
Describe what the user can do or see. Avoid technology and revenue language. Example: record an inquiry and see the next follow-up date.
Set a responsible boundary
Exclude sensitive or high-risk work from the first project. Decide what data the project will not collect.
Name one failure case
Choose a failure that would make the result unreliable, such as saved information disappearing after refresh.
Copy-and-complete template
Create your module artifact
User: Moment of need: Observable result: Important constraint: Data I will not collect: One failure case:
Keep sensitive information, passwords, API keys, payment data, and private customer details out of course notes and AI prompts.
Quality gate
Check the result before the quiz
- The project serves one primary user.
- The result can be demonstrated.
- The first version avoids high-risk decisions.
- A failure case is written before building.
How this moves the project forward
Module 2 uses this project card to decide exactly where human review is required.
Evidence checkpoint and lesson summary
Confirm the artifact, then answer the key questions
The questions cover a core idea, a realistic decision, and evidence from the lesson. Incorrect answers identify concepts to review; they are not a complete measure of your experience or ability.
Confirm the artifact and answer all three questions correctly to unlock the recommended next step.
Continue to Module 2: Vibe Coding Is Not Magic: Set the Human Review Boundary