Roles

Musketeer supports a role-separated execution model built around three operational responsibilities: Originator, Examiner, and Executor. These are not personalities. They are control boundaries.

Originator

The Originator forms intent. This role is responsible for:

• Shaping the task
• Refining scope
• Defining constraints
• Identifying acceptance criteria
• Preparing the handoff package

The Originator is where exploration and framing happen. Its job is not to execute. Its job is to clarify what should be done and under what conditions.

Examiner

The Examiner challenges the work. This role is responsible for:

• Testing assumptions
• Checking alignment to intent
• Identifying ambiguity
• Exposing drift
• Strengthening the handoff or reviewing the result

The Examiner is the adversarial layer. Its job is not to make the task bigger. Its job is to reduce false confidence.

Executor

The Executor performs bounded work. This role is responsible for:

• Acting against explicit instructions
• Staying inside defined boundaries
• Producing concrete outputs
• Returning results for review
• Avoiding silent redefinition of the task

The Executor is not there to invent the mission. It is there to carry it out cleanly.

Why this structure matters

The value is not that three models are involved. The value is that these responsibilities remain separated.

In some environments, one model may fill more than one role. In others, different providers may fill different roles. A human may fill one role while models fill the others. Musketeer is not tied to a specific vendor lineup.

The operating principle

Separate the roles. Bound the work. Keep control. That is the model.