Explanation

Use explanation when you need to understand why Drift CLI has a constraint or boundary before making a design or operational decision. These pages describe context, tradeoffs, and consequences rather than procedures.

Client architecture — why parsing, transport, DTOs, workflows, and output remain separate.
Configuration and credentials — why profiles remain non-secret and bearer keys establish tenant context.
Administration security model — how tenant-scoped keys authorize administrative workflows.
Tenant administration trust boundary — why tenant administration is not instance authority.
Command scope — why the CLI exposes a narrow operator surface instead of a generic Drift API shell.