A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
majordomus devcontext explain
Why one canonical identifier is or is not in the context a request compiles to
What it is
read onlyWhy one canonical identifier is or is not in the context a request compiles to
- Identity
executable.devcontext.explain- Program
- executable
- Runs
- non interactive
- Requires
- repositorylayer
Where it appears
- Command line
majordomus devcontext explain- Workflow
just devcontext-explain- MCP tool
majordomus_devcontext_explain- HTTP
/api/v1/devcontext/explain- Declared in
apps/majordomus-cli/src/cli.rs- Capability
- devcontext.explain
Arguments
| argument | values from | required | help |
|---|---|---|---|
<URI> | yes | The canonical identifier, `majordomus://<kind>/<identity>` | |
--issue | — | An issue id (`I0301`) or its canonical identifier | |
--milestone | — | A milestone id or slug, or its canonical identifier | |
--intent | — | What the session is trying to do, in words; the only input the compiler infers from | |
--path | — | A repository-relative path the work touches; repeat for each | |
--uri | — | A canonical identifier to seed with directly; repeat for each | |
--budget-tokens | — | The ceiling in estimated tokens | |
--max-depth | — | How far from a seed the walk goes | |
--floor | — | Relevance below which an entry is reported rather than given, between 0 and 1 | |
--all-blocking-rules | — | Every blocking rule of the layer, not only the ones the work reaches | |
--repo | — | Start the search for the repository root here (default: the current directory) | |
--discovery | — | How declarative files are enumerated | |
--strict | — | Refuse to proceed when any file of the layer carries an error diagnostic | |
--share | — | The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable | |
--format | — | Output shape |