magus-explain
Show one knowledge-graph node's context: data, edges, and reach
Synopsis
magus explain <node-id-or-name> [flags]
Description
explain shows one node's context: its data, its incoming and outgoing edges with provenance, and how many nodes reach it. Where query finds candidates, explain is what you run on the one you picked.
The argument is a node ID (target:pkg/foo:build) or a name that resolves to one (build). Names are convenient and IDs are unambiguous; when a name matches more than one node, resolve it with query first and pass the ID.
Two parts of the output are worth knowing about. Every edge carries its PROVENANCE - what declared it, so a surprising relationship can be traced to the file that created it rather than taken on faith. And the reach count answers the blast-radius question directly: how many nodes can arrive at this one.
The graph is cache-backed under <cache>/knowledge and only shards whose sources changed are rebuilt; --refresh forces a full rebuild.
Options
- --global
- Resolve across the workspaces registered in config (knowledge.workspaces)
- --refresh
- Force a full graph rebuild before explaining
Examples
A target in full
magus explain target:pkg/api:build
Resolve by bare name
magus explain build
A spell's context
magus explain spell:go
As a record
magus explain build -o json
See Also
magus(1), magus-ls(1), magus-describe(1), magus-where(1), magus-run(1), magus-affected(1), magus-x(1), magus-clean(1), magus-shell(1), magus-query(1), magus-refs(1), magus-path(1), magus-graph(1), magus-diff(1), magus-vcs(1), magus-session(1), magus-job(1), magus-notes(1), magus-queue(1), magus-watch(1), magus-events(1), magus-server(1), magus-broker(1), magus-mcp(1), magus-status(1), magus-buzz(1), magus-spell(1), magus-agent(1), magus-init(1), magus-doctor(1), magus-config(1), magus-completion(1), magus-man(1), magus-self(1), magus-version(1)