Mission Outcome Loop

Resume from real proof.

projscan routes a developer goal, saves the mission, reads the proof state, and tells the next agent what changed, what remains, and whether the work is ready for version review.

Mission Control Local-first MCP-ready Outcome resume Proof report

1 bundle mission plus proof

45 MCP tools

11 / 12 AST adapters / languages

projscan start --mission

$ projscan start --mission .projscan/mission ProjScan Mission Control Mission: .projscan/mission Status: passed Outcome: proof passed after 3 commands read proof-logs/summary.json and status.jsonl

              What Changed
              - Mission proof passed after 3 command(s).
              - 1 reviewer decision recorded.
              - 0 failed gates remain.
            

              What Remains
              Run ./review.sh and choose a reviewer reply.
              Version candidate: review_candidate
            

              Outcome Commands
              projscan start --mission .projscan/mission
              projscan mission-proof --mission .projscan/mission
              projscan mission-proof --baseline manual-runs.json
              all source stays local
            

              Proof Evidence
              proof-logs/summary.json: passed
              proof-logs/status.jsonl: 3 rows
            

              Review Gate
              capture: git status --short
              capture: git diff --stat
              reply: review version candidate
              do not publish until approved
            

Goal routing

Ask in plain language.

Route privacy, merge readiness, refactor risk, local setup, ownership, dependency, release, and handoff questions to the right command with matched keywords and confidence.

Outcome resume

Start from saved proof.

projscan start --mission reads the bundle proof state and gives the next agent a focused "what changed / what remains" handoff.

Proof report

Measure the saved work.

projscan mission-proof reports proof completion, reviewer approvals, reruns, failed gates, time saved, and local risk avoided.

Proof, review, and adoption evidence

Close the loop.

Developers and agents can resume from a saved mission bundle, summarize pass/fail evidence, and compare local proof against a manual baseline without sending source code anywhere.

projscan mission-proof

              $
                projscan mission-proof --mission .projscan/mission --format json
              Local proof summary
               
              {"passed":1,"failed":0,
               "reruns":0,"reviewerApprovals":1}
               
              Risk avoided
              - proof gate passed before release
              - version review is safe to request
              Next: projscan start --mission .projscan/mission
            

Verify Outcome resume --mission reads summary.json, status rows, and reviewer decisions.

MCP MCP start input mission_dir carries the same proof outcome to agent clients.

List Proof summary mission-proof reports completion, reruns, failed gates, and approvals.

Gate Version review Outcome data says whether to request review or keep fixing failed proof.