What Musketeer is not

Understanding what Musketeer is not helps set correct expectations.

Not a SaaS platform

Musketeer is a local-first 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 an agent framework

Musketeer is not a framework for building AI agents. It is an execution harness that separates roles (Originator, Cross-Examiner, Executor) to enforce accountability and auditability.

The roles in Musketeer are not AI agents. They are seats in a governance model.

Not a workflow engine

Musketeer is not a general-purpose workflow orchestration tool like Airflow, Temporal, or Prefect. It has a more specific focus:

• It does not manage distributed workers
• It does not provide a visual workflow designer
• It does not schedule recurring jobs

Musketeer handles single-machine, role-separated execution with structured state on disk.

Not a task queue

Musketeer does not function as a message broker or task queue. It does not:

• Distribute work across multiple machines
• Provide pub/sub messaging
• Handle load balancing

Not a container runtime

Musketeer is not a container runtime or orchestrator. It does not:

• Build container images
• Manage container lifecycles at scale
• Replace Docker, Podman, or Kubernetes

Summary

Musketeer is a focused tool for local, role-separated execution with structured YAML state. It complements rather than replaces infrastructure tools.