resume-prompt.md — session entry point

You are starting a session of Project-2, an autonomous research project building a rigorously sourced knowledge base on the "untranslatable words" phenomenon — from popular listicle words (hygge, saudade, and their many companions) to the academic tradition of untranslatables (Cassin's Dictionary of Untranslatables, translation theory) to the linguistics underneath (lexical gaps, linguistic relativity) — and, once the base can support it, original research on whether individual untranslatability claims survive contact with evidence. You have no memory of previous sessions — the repository is the memory. This file stays stable; current state lives in NEXT.md.

0. Ground yourself

• Check the current date.
• Check for stranded work: is there an open pull request against the main branch with this project's project-2: commit prefix? An open one means a predecessor stopped between push and merge — merge it (or resolve why it can't merge) before going on.
• Verify the substrate: fetch the main branch and confirm your working checkout actually contains its latest commit. A stale checkout means redoing already-merged work — check before trusting anything on disk.

1. Read, in this order

1. CLAUDE.md, MISSION.md, and wiki/conventions.md — the rules (short; read every session).
2. NEXT.md — state and queue.
3. wiki/index.md — the catalog.
4. inbox/ — anything there is unprocessed input from the owner and outranks the queue. Process it, then move it to inbox/archive/ and note the processing in wiki/log.md.
5. Only then: the specific wiki/source pages the chosen unit needs. Do not load the whole knowledge base.

2. Work the queue, one unit at a time

Take one coherent, completable unit from NEXT.md's queue, top-down. If the top unit is blocked, write down why and take the next unblocked one. Never end a session having done nothing — if a tool or file this protocol names does not exist yet, building it is the unit.

3. Wrap up — every session, no exceptions

1. Update wiki/index.md and wiki/log.md for anything added or changed.
2. Rewrite NEXT.md from scratch (not appended) — state matching reality, queue re-prioritized, for-owner block current.
3. Write the owner report for this session in journal/YYYY-MM-DD.md.
4. Run the integrity check (python3 tools/check_links.py at minimum); fix anything broken before committing.
5. Commit (subject prefixed project-2:), push, open a pull request, merge it, and confirm the base branch actually advanced. If the merge cannot land, say so at the top of NEXT.md before stopping.