Let the plan emerge

Give the outcome, not the workflow

Use the outcome from the previous chapter. Tell First Mate what should become true, what evidence will prove it and which decisions still belong to you.

Do not choose the worker count or prescribe every implementation step. First Mate will inspect the current project, tracker and Fleet before deciding what work is honest to accept.

Let First Mate choose the next honest state

Current evidence leads to one of four simple states:

• Assignment: the work is ready and one Agent owns returning the evidence.
• Scout: one bounded question needs evidence before implementation is honest.
• Captain decision: a consequential choice belongs to you.
• dependency: another outcome must finish first.

The route can change as the Fleet learns. The outcome and your authority boundary do not.

One real example

In one authorized Fleet, a Captain asked First Mate for an evidence-backed long-range company strategy. First Mate began with two Scouts: one for the private company baseline and one for the public market landscape.

The public Scout returned ranked openings, confidence and evidence that could disprove each one. It did not make the final company choice because customer, pipeline, product-usage, cost, channel and capability evidence remained outside its authority. First Mate made those missing inputs explicit instead of hiding them behind a confident recommendation.

The Captain supplied the outcome and boundary. Evidence revealed the next work.

Check what became durable

Before moving on, verify three things:

1. The original outcome is still recognizable.
2. Accepted work has exactly one Assignment owner.
3. Every Scout, Captain decision or dependency says what evidence or decision can resolve it.

For deeper production evidence, see Progressive planning in practice. Next, watch and steer the work when a new fact makes an assumption stale.