map-deployment

Repository context

The current repository is both the CONSUMER, whose convention home declares where artifacts land, and the DEFAULT SUBJECT, whose tracked IaC declares the topology.

Collect with an individual Bash call, one command per call: the project root, git rev-parse --show-toplevel. Treat a failure (not a repository, git unavailable) as an unknown value and carry on; ${CLAUDE_PROJECT_DIR} is the resolver's --root either way.

Purpose

Answer "where does this run, and what is different about that environment" from committed infrastructure as code. Every node traces to a named file. The scripts collect and render. Do not draw a node the script did not emit, and do not describe a live cloud. This is the C4 deployment view; each environment is its own deployment environment in the diagram.

Resolve home and dialect

Read ${CLAUDE_PLUGIN_ROOT}/reference/config.md first. This skill writes into architecture_dir. It does not read landscape_dialect and adds no dialect key: the diagram dialect is diagram_dialect.system from the authoring-formats topic doc. likec4 writes deployment.md with one fenced likec4 block, c4-plantuml with one fenced plantuml block. Mermaid is not offered.

Run bash "${CLAUDE_PLUGIN_ROOT}/lib/resolve-convention-home.sh" --root "${CLAUDE_PROJECT_DIR}" and follow the exit code; never parse the root instruction file yourself. Exit 0: read <home>/architecture/README.md for architecture_dir. Exit 1, 2, or 3: no declared home.

Per key, in order: --out <dir> wins for this run alone, then a declared architecture_dir, then one question. architecture_dir has NO default. An undeclared and unconfirmed home, including every non-interactive run, STOPS and points at /architecture:setup. Do not invent a directory.

Resolve diagram_dialect.system by restating this ladder, then running the resolver rather than parsing the topic doc yourself. The ladder is a resolution order, not a task list:

1. Anchor at the repository root: `${CLAUDE_PROJECT_DIR}` when set, otherwise
   `git rev-parse --show-toplevel`. Never a CWD-relative read.
2. Resolve the convention home `<home>` with the bundled resolver above. Never hand-parse the root
   file.
3. The printed home is repo-relative: join it to the root, then pass
   `<root>/<home>/authoring-formats/README.md` to the resolver.
4. Layer order is one layer deep: an explicit `--dialect` argument, then the team convention doc,
   then the documented default. There is no personal overlay.
5. `diagram_dialect.system` has NO default. Allowed values are `likec4` and `c4-plantuml`. When it
   is unset, emit no C4 deployment view. The record is still written.
6. Degrade soft, and say so. No pointer, no doc, no key, or an unrecognized value (mermaid
   included) each resolve to emitting nothing. The resolver names the cause on stderr. Do not
   hard-fail and do not ask the operator to create the surface mid-task.
7. Report provenance: the key, the value, and the layer (`argument`,
   `team convention doc <path>`, or `unset (no C4 view emitted)`).