Workspace Intelligence command
workspai workspace why
Explain why a relationship, verdict, or workspace fact exists.
- Category
- Workspace Intelligence
- Workspace Intelligence
- Yes
- Produced artifacts
- 1
- Related contracts
- 3
- Registration
- contract-declared
- Registered options
- 0
Operational role
This purpose is versioned in the CLI runtime command surface. It is not inferred from page copy or a generic command template.
Canonical invocation
This invocation is derived from the runtime command surface. Commands with a registered intelligence execution include their canonical evidence-producing flags.
npx workspai workspace whyRuntime signature
Arguments, aliases, and options come from the versioned snapshot of the live Commander tree emitted by the CLI. Contract-declared delegated commands intentionally expose only their canonical invocation.
This command is declared by the cross-runtime capability contract and delegated outside the npm Commander tree. Its invocation remains canonical, but runtime-specific flags are documented by the selected project adapter.
Contract relationships
Capability contracts govern whether the command exists; artifact contracts govern the structured output it produces.
Produced artifacts
Artifacts are durable machine-readable outputs. Their schema, path, and producer relationship must remain stable across CLI, CI, IDE, MCP, and agent consumers.
| Artifact | Schema version | Contract |
|---|---|---|
| .workspai/reports/workspace-why-last-run.json | workspace-explain.v1 | contracts/workspace-intelligence/workspace-explain.v1.json |