GUIDED PATH · PHASE 5
Guided Japanese Course
A mastery path for complete beginners and technology professionals.
HOW THIS COURSE WORKS
Follow the path. Advance by mastery.
The primary path tells you what to do next. You can still open any available lesson, but completion is based on checkpoints rather than calendar days.
FULL TARGET CURRICULUM
Tracks 0–10
TRACK 2 · 2-10
Polite Verb Past: ました / ませんでした
Report completed actions and polite negative past actions.
- Polite ます forms.
Stand-ups, incidents, and retrospectives constantly report what happened and what did not happen.
1. Refactor the polite ending
For ます verbs, past affirmative replaces ます with ました; past negative uses ませんでした.
2. Technical status update
Keep vocabulary familiar so attention stays on tense.
Natural: I wrote the code.
Structure: code — object — wrote.
Completed work.
Natural: I ran the test.
Structure: test — object — did.
Completed test.
Natural: I did not check the data.
Structure: data — object — did-not-check.
Negative past.
Natural: I worked yesterday.
Structure: yesterday — worked.
Past reference.
3. Mini stand-up: yesterday
Use separate short statements for now; Track 5 later adds better connectors.
4. Yesterday / did-not-do report
Write eight fictional workday sentences: six completed actions and two not done. Refactor two back to non-past.
INTERACTIVE WORKSHEET
4. Yesterday / did-not-do report
Write 8 past work sentences (6 +, 2 −). Underline only the conjugated ending. Refactor 2 back to non-past.
Tip: on a foldable or tablet, use your pen directly on the page. Your strokes are saved in this browser as you work.
4. Yesterday / did-not-do report
Write 8 past work sentences (6 +, 2 −). Underline only the conjugated ending. Refactor 2 back to non-past.
5. Tense refactor in Language IDE
Keep sentence roles stable while changing tense.
Language IDE
Why here: It makes unchanged sentence structure visible.
How to use it for this lesson: Build データを確認します and refactor ます → ません → ました → ませんでした.
Refactor verb tense →Mastery checkpoint
Answer from memory. Treat every miss as a debugging signal: inspect the explanation, repair the rule, and retry.
