skills/rehearse-japanese-speaking/references/interaction-tasks.md

# Interaction tasks

Use these as structured templates, not scripts. A task combines:

**setting + practical objective + relationship + one complication + target capability**

## Runtime principles

- Keep interlocutor turns concise.
- Make the learner produce most of the language.
- Use one internally consistent information gap or complication.
- Do not reveal hidden information prematurely.
- Do not become arbitrarily hostile.
- Do not require obscure procedural knowledge.
- Accept multiple valid outcomes and formulations.
- Task completion and language quality are separate.

## Task schema

```yaml
setting:
learner_role:
interlocutor_role:
relationship:
medium:
mission:
real_details:
simulated_details:
learner_knows:
interlocutor_private_information:
main_complication:
success_conditions:
primary_focus:
secondary_focus:
```

## Scenario templates

### Change an appointment

Mission: identify the existing appointment, request a change, reject an unsuitable alternative, and confirm the final arrangement.

Complications:
- first alternative conflicts with the learner’s schedule;
- receptionist asks for an unexpected identifier;
- requested provider is unavailable;
- compressed date/time confirmation requires clarification.

Success:
- appointment identified;
- change requested;
- unsuitable option handled;
- final date/time and requirements confirmed.

### Missing restaurant reservation

Private information: reservation is under another spelling/name, wrong date, or companion’s name.

Complication: only a later time or different seating remains.

Success:
- identifying information supplied;
- staff asked to check;
- alternative negotiated;
- outcome confirmed.

### Missing delivery

Private information: package is at a similar address, parcel locker, neighbor, or wrong building.

Complication: staff initially offers only “wait another day.”

Success:
- sequence explained;
- address/order confirmed;
- investigation requested;
- concrete next step secured.

### Apartment repair

Problems: air conditioner, leak, mold, hot water, lock, appliance, or noise.

Complication: first visit time is impossible, access is restricted, or urgency is initially minimized.

Target: explain urgency clearly without accusation; negotiate access/timing.

### Food allergy

Complication: staff cannot confirm ingredients or says “probably okay.”

Success:
- allergy and risk stated clearly;
- specific follow-up asked;
- uncertainty not accepted as assurance;
- a safe decision is reached.

Never certify food as medically safe.

### Lost item at a kōban

Complication: more detail is requested than expected: route, time window, appearance, contents, or identifying marks.

Target: chronology, description, uncertainty, and next-step confirmation.

### Administrative procedure

Complication: missing document, wrong counter, or misunderstood step.

Target: clarify requirements, distinguish now/later, and confirm next action.

Do not invent current official rules. Simulate generic language unless verified facts are supplied.

### Train disruption

Complication: obvious route unavailable or first explanation too dense.

Target: request simpler repetition, confirm transfers/platform, summarize back, decide.

### Ask a coworker for help

Complication: coworker is busy or can help only partially.

Target: explain request, acknowledge burden, negotiate timing, confirm ownership.

### Explain a delay or mistake to a manager

Complication: manager challenges the timeline or asks why notice came late.

Target: acknowledge responsibility, give relevant context without over-excusing, propose recovery.

### Correct a misunderstanding

Target:
- identify the incorrect assumption;
- clarify without confrontation;
- confirm shared understanding.

Useful frames:
- `私の説明が分かりにくかったかもしれません。`
- `〜という意味ではなく、…`
- `念のため確認させていただきたいのですが…`

### Decline or disagree

Relationships: friend, coworker, manager, unfamiliar professional.

Complication: interlocutor presses once for a reason or alternative.

Target sequence:
acknowledgment → constraint/concern → alternative or boundary.

## Relationship variation

Practice similar functions across:

- friend;
- familiar peer;
- stranger;
- service professional;
- coworker;
- manager or authority figure.

Do not reduce pragmatic adaptation to “casual versus keigo.” Consider social distance, status, imposition, setting, and communicative purpose.