Expand description
The shell tool’s commands as command-graph nodes.
bin/majordomus is a different program with the same name: the task lifecycle, written
in shell. Its command surface already has a canonical owner — share/commands.yaml,
shipped beside the rules, reconciled against the tool’s own dispatch table by the
command_surface_complete doctrine. This reads that owner. It does not parse the help
text, and it does not keep a list of its own: a command added to the registry and the
dispatch table appears here on the next build, and one removed disappears.
§What is translated, and what is read as it stands
Two fields are translated into the graph’s vocabulary, because the graph spans three programs and the registry speaks for one:
registry class | graph effect | why |
|---|---|---|
read-only | read-only | writes nothing |
state-mutating | local mutation | writes under .ai/local/, which no commit carries |
generated-output-mutating | repository mutation | rewrites tracked, generated files |
and interactivity is read from the declared syntax: a command whose synopsis takes a
body on standard input holds a terminal, and no request/response surface may carry it.
Both are derivations from what the registry already states, not new declarations.
Structs§
- Contribution
- What the read produced.
Constants§
- DECLARATION
- The path a projection shows as the declaration.
- DISPATCH
- The dispatch table the registry is reconciled against, named so a diagnostic can point at it.
- REGISTRY
- The shipped registry this reads, relative to the share directory.
Functions§
- contribute
- Read the shell tool’s commands from the shipped registry under
share.