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-14
ある / いる: Existence
Use あります for inanimate existence and います for animate existence.
- Animate/inanimate vocabulary.
Say a server exists, a document is available, a person is present, or a teammate is in a room.
1. Choose the verb by what exists
In polite form, inanimate things take あります; people/animals take います.
2. State existence
Learn the whole pattern N が あります / います.
Natural: There is a server.
Structure: server — existence focus — exists.
Inanimate.
Natural: There is a document / Documents are available.
Structure: document — exists.
Availability.
Natural: Tanaka is here.
Structure: Tanaka — exists.
Animate.
Natural: There is an employee.
Structure: employee — exists.
Animate.
3. Notice が in the existence pattern
This previews が because existence sentences often introduce what exists with が. A fuller は/が treatment comes later.
4. Office existence inventory
Use your office drawing. Write ten existence sentences: at least three います and seven あります. Add two intentional wrong choices and correct them.
INTERACTIVE WORKSHEET
4. Office existence inventory
Write 10 existence statements. Mark ANIMATE/INANIMATE and choose います/あります. Add 2 bug→fix examples.
Tip: on a foldable or tablet, use your pen directly on the page. Your strokes are saved in this browser as you work.
4. Office existence inventory
Write 10 existence statements. Mark ANIMATE/INANIMATE and choose います/あります. Add 2 bug→fix examples.
5. Debug the existence verb
This binary selection rule is perfect for debugging.
Language IDE
Why here: It isolates noun category from verb choice.
How to use it for this lesson: Build 社員がいます and サーバーがあります. Swap nouns and identify when the verb changes.
Debug ある / いる →Mastery checkpoint
Answer from memory. Treat every miss as a debugging signal: inspect the explanation, repair the rule, and retry.
