[lukemaj]

What: Model Router's Mission is broader and more abstract: dependable delegated work, with coordination (a separate dispatcher or the planner) chosen by measured evidence. The Objective adds the Agent Observer comparison of both modes.
Why: The user (2026-09-29) wants Prism fast and reliable and is "not married to the dispatcher"; the old Mission fixed "a dispatcher owns the job" as design.
So what: You merge; the Vision is unchanged, and #146 builds the comparison.

Direction change confirmed by the user in the planner thread on 2026-09-29 with these exact contents (Mission "yes", Objective "ok"). VISION.md is unchanged. Re-read all three after writing: the Vision's counterpart that "decides how intelligence is applied" is consistent with the Mission choosing model, harness, effort and coordination from evidence; the Objective keeps today's dispatcher milestones and adds the measured comparison. Sizes: VISION 384, MISSION 596, OBJECTIVE 1588 bytes.

Elon record

• Requirements and who asked: the user (2026-09-29): broader, more abstract Mission; Objective stays specific; the dispatcher is kept only if evidence supports it.
• Deleted: "from then on a dispatcher owns the job" and "talks to the dispatcher directly" as fixed design; T3 specifics from the Mission (they stay in the Objective and RUNNER.md).
• Bottleneck: the Mission ruled out the planner-dispatch experiment (Optional dispatcher: let the planner dispatch, then compare both modes with Agent Observer #146) by definition.
• Checked myself: re-read the committed Vision and the new Mission and Objective together; versionctl release-check OK for v0.41.1.

Note: PR #145 also bumps the version (0.42.0); whichever merges second needs its version rebased.

🤖 Generated with Claude Code