kai

Advanced Kai / speaking

solo and partner speaking prompts

Short speaking prompts for recording yourself and working with a partner. Each prompt gives a focused task, steps, and self-checks, with companion model responses available after the first attempt.

Advanced Kai role-play cards model responses recording checklist

learner boundary

Common Kai first

Advanced work may compare technical, poetic, symbolic, and sacred choices. Start with exact Common Kai: the claim, condition, cause, request, or definition must be recoverable before register analysis.

  • Write the literal Common Kai sentence first.
  • Label technical, poetic, or sacred pressure separately.
  • Do not make legal, medical, safety, or practical instructions poetic.

routine

how to use prompts

  • Read the prompt once silently and once aloud before starting.
  • Record or perform the first attempt without pausing for correction.
  • Use the self-checks to revise the second attempt.
  • Compare the second attempt with the model response page.

path

prompt list

  1. embedded claim audit solo / complex clauses
  2. translation strategy note solo / translation commentary
  3. technical definition solo / register control
  4. claim and challenge partner / argument
  5. register repair review partner / technical versus poetic
  6. agreement boundary partner / conditional agreement

solo

solo practice prompts

3 prompts

Use these for individual recordings, pronunciation review, and fluency self-checks.

solo 01 / complex clauses

embedded claim audit

Record one embedded claim with va, then explain why its boundary is clear.

steps

  1. State the claim.
  2. Name the embedded clause boundary.
  3. Give one possible ambiguity and repair it.

self-check

  • va does real structural work.
  • The repaired version is clearer.
  • The explanation avoids unnecessary symbolism.
solo 02 / translation commentary

translation strategy note

Choose an English idiom and explain whether you would translate it literally, paraphrase it, or replace it.

steps

  1. Name the idiom.
  2. Give the rejected literal version.
  3. Give the final strategy.

self-check

  • Meaning is prioritized over English wording.
  • The rejected version has a reason.
  • Register is named.
solo 03 / register control

technical definition

Define a technical term in plain Common Kai, then label what makes it technical.

steps

  1. Give a one-sentence definition.
  2. Use rallune or nelo if appropriate.
  3. Add one register note.

self-check

  • The definition is teachable.
  • The register note is specific.
  • Poetic language does not obscure the term.

partner

partner practice prompts

3 prompts

Use these for turn-taking practice, repair routines, and level-specific conversation control.

partner 01 / argument

claim and challenge

One partner makes a claim. The other challenges it politely and asks for evidence.

steps

  1. Use an embedded va clause.
  2. Use Mi el sile ti before disagreement.
  3. Ask for rallune or yelo.

self-check

  • The challenge is precise.
  • Disagreement is not falsehood by default.
  • Evidence or clarification is requested.
partner 02 / technical versus poetic

register repair review

Partner A gives a poetic or unclear line. Partner B repairs it for technical Common Kai.

steps

  1. Label the register issue.
  2. Request clearer wording.
  3. Produce a repaired sentence.

self-check

  • The repair is usable in teaching.
  • The register label is accurate.
  • The repaired sentence preserves meaning.
partner 03 / conditional agreement

agreement boundary

Practice withholding sainel until the explanation becomes clear.

steps

  1. Ask for agreement.
  2. Withhold agreement politely.
  3. State the condition for future agreement.

self-check

  • sainel is not given under confusion.
  • The condition is clear.
  • The conversation remains cooperative.