doss/cli
Build and operate DOSS from one command surface.
What it does.
doss/cli exposes the same command registry to people, shell scripts, and agents. Help, JSON output, MCP tools, previews, approvals, and apply behavior come from the command definition rather than separate wrappers.
Humans and agents use the same commands.
doss/cli generates help, completion, JSON output, MCP exposure, and risk behavior from one command registry. The interface changes by transport; command meaning does not.
Schema, examples, risk, output mode, capability requirements, help, completion, and MCP projection are defined once.
Exit codes, structured errors, and smoke results tell a person or agent what to do next.
What it owns
One registry
Generate help, completion, JSON output, and MCP tools from the same command definition.
Stable output
Use JSON, JSONL, pagination, watches, timeouts, and explicit apply flags in automation.
Full release path
Initialize, validate, plan, deploy, inspect logs, smoke test, and roll back.
Call the owner
Route each command to Tapestry, Tesseract, DOSSBOT, CENTARI, or the build system.
What it connects to
doss/cli calls these products and services directly.
