Public: anyone can read this; the crew can change it.

Vision upkeep: a thought that changes the vision becomes a small pull to docs/VISION.md, and the direction follows #655

Closed trevatoowner opened this 1mo ago scoutcrew has it

trevatoowner opened this 1mo ago

Pillar: P7 Steering (#593), linked to the alignment work (#610-#615). First wave. One run, fresh from main.

Why. The owner: "the continuous thought that I am relaying is how this will work, so you and the forge need to be built for it." He steers by streaming thoughts, mid-flight, sometimes repeating or reversing earlier ones. Nothing may be lost or mangled.

Outcome. When a thought changes what the forge is for or how it is built, the planner proposes the edit to docs/VISION.md as a small pull and the repository's direction text follows it, so the document every run reads stays current.

Today. docs/VISION.md lands with #616; the direction is a setting a person edits; nothing keeps them in step.

The path: the owner says something that changes the vision; the reply under the thought links a pull with the one-paragraph edit; primary action Ship (or say what to change); next the feed.

Acceptance.

[ ] Triage kind vision opens a pull editing docs/VISION.md (the smallest change that says it) with the thought quoted in the description.
[ ] When that pull merges, the direction text is regenerated from the vision's order of work and rules (under 2,000 characters) and written through the settings path, with an event.
[ ] A person still lands the pull (rule 10).
[ ] Minimal, not bare: one primary next action; the pull's looks show the path at phone and desktop widths and say what it removes.

Done means reachable:

Page: the pull linked under the thought
MCP: thought {id} links the pull
Test: vision thought opens a pull; merge updates the direction; length bound
Look: the pull and the updated direction on settings

Removes: hand-edited direction drift; say so.

Start from: src/crew/brief.ts, src/core/repos.ts (direction), src/web/pages/settings.ts, docs/VISION.md.

Depends on: #652, #616.

Must not touch: the release workflow, the chart, other repositories.

atlascrew commented 16d ago

Split. Pull #5761 had three review rounds, and each found a new problem with how landing a vision pull rewrites the direction. The proposing half was sound throughout. It is now three issues:

#5833: a vision thought opens the pull, linked under the thought, on /asked and in MCP thought. Landing it changes no setting.
#5834: an admin merge rewrites only a fenced block of the direction and keeps the owner's words. A writer merge posts no comment in anyone's name. An orphan start marker changes nothing. (After #5833.)
#5835: the pull shows the direction it will write, and Settings marks which part follows the vision. (After #5834.)

Also opened: #5836 (MCP vision), and #5837 (P0: every merge follow-up acts as the merger or as the forge, never as someone else).