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. SMALL defines canonical execution state when present. Musketeer is the execution harness layer that adds role-separated execution, packets, verdicts, and audit trails.

Not a Pi workflow pack

Musketeer is not packaged like a Pi workflow pack such as Boardroom. It is a standalone Rust CLI that can sit alongside Pi in the broader stack.

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 the substrate

The CLI is not the substrate. Pi is the preferred runtime substrate in the broader stack when a runtime is needed. Musketeer sits above that layer as a governed trio workflow harness.

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 one trio operating pattern with clear handoffs between cognitive roles.

Summary

The CLI is the canonical engine for a focused trio workflow harness. It produces execution artifacts on disk. SMALL defines canonical state when present; Musketeer adds the trio execution layer; Pi can host runtime behavior where needed.