dx-research

Investigate one topic and record it as a durable, provenance-stamped artifact a later dx-frame/dx-plan can trust without re-deriving. Research is a deliberate act you initiate — one invocation, one topic, one mode. Read foundation/glossary.md for naming (a one-line habit — no section).

Guard. Resolve <container-id> first:

• A change → context/changes/<id>/; an effort → context/efforts/<id>/; the literal foundation → context/foundation/ (durable, reusable investigations — the natural home for external-doc research read by every plan).
• Missing container → tell the user to run /dx-new first, then stop. Under context/archive/ → refuse; an archived container is done.

The file lands at <container>/research/<topic-slug>.md. No index — ls research/ derives the list. If the file already exists this is a refresh: re-run and re-stamp its frontmatter.

1 — Pick the mode from the input

• External when a --url=, --kind=external, or a bare URL is present → §3.
• Codebase otherwise (default) → §2.

If the topic is a refactor investigation (or the container is a type: refactor change/effort), invoke dx-references with module-design and use its vocabulary — deep modules, seams, the deletion test.

2 — Codebase mode