What the CLI Does Not Do

Understanding what the CLI does not do helps set correct expectations.

Not a standalone protocol

Musketeer is not a protocol. It is an execution harness that operates on top of SMALL-governed workspaces. SMALL defines the canonical execution state. Musketeer adds role-separated execution, packets, verdicts, and audit trails.

Not a SaaS platform

The CLI is a local tool. It does not:

Require an account or subscription
Phone home to any service
Store your data in the cloud
Need network connectivity for core operation

You run it locally. Your data stays local.

Not a model runner

The CLI does not run AI models. It does not:

Execute prompts against models
Manage API keys
Handle model responses
Orchestrate model interactions

The CLI prepares handoffs. You (or another tool) execute them with the models of your choice.

Not an automation system

The CLI does not automate anything. It does not:

Loop until a goal is achieved
Make decisions on your behalf
Chain operations automatically
Run unattended

The human initiates every action. The CLI records state.

Not a workflow engine

The CLI is not a general-purpose workflow orchestration tool. It focuses on structuring handoffs between cognitive roles within a SMALL-governed workspace.

Summary

The CLI is a focused execution harness for structuring trio workflows in SMALL-governed workspaces. It produces execution artifacts on disk. Canonical state is defined by SMALL; Musketeer adds the execution layer.