CodeNomad/scripts/recurring-simple-native
Pascal André c17752e9b7
Some checks are pending
Publish help / build (push) Waiting to run
Publish help / deploy (push) Blocked by required conditions
feat(missions): route human questions through the coordinator and record who decided (#1227)
Missions asked the human too many questions, too early, and in Exploration
the questions came straight from sub-agents: since the decision worker had
to ask the human from its own conversation, the coordinator could neither
answer, defer nor batch them. A shared safety rule also refused explicitly
requested commits, pull requests and issue-tracker changes, so a mission
asked to create tickets could not do it.

Only the coordinator now talks to the human, in every playbook. Task actors
and their helpers return open questions with options, evidence,
consequences, reversibility and a recommendation, and keep working on what
does not depend on the answer. Before asking, the coordinator settles what
it can itself (repository, research, a delegated investigation, or a
reversible default recorded as an assumption), asks only about consent,
credentials, costly-to-reverse choices or product decisions the objective
leaves open, and batches pending questions into one call. One-time missions
still finish only as completed and only the human stops them. Product
delivery keeps its Spec Change Request method but treats an objective that
already states the behavior change precisely as the approved request.

Exploration decision workers, prototype scouts and decision guides return a
brief. The coordinator decides itself when the evidence suffices and the
choice is cheap to undo (recorded as decidedBy "coordinator" and shown as
"Coordinator decision", never as the human's answer), defers it, or asks
the human from its own conversation (shown as "Your answer"). A claimed
human answer still needs a confirmed UI mark. Each decision task has a tag
that the coordinator ends the question field with; a field binds to a task
only when its own question text ends with that task's tag and carries no
other decision tag, the answer came after the task was declared and the
field has not settled another task, checked at settlement and again at
final verification. Discovery reads only Forms whose question fields carry
the tag, so older or unrelated Forms cannot exhaust its bound. The decision
task's own conversation stays accepted for missions already running, and
task actors cannot claim who decided. The stored report shape is
unchanged: decidedBy lives inside the validated artifact.

The safety boundary keeps staging, committing, pushing, pull requests and
issue-tracker changes forbidden by default, except when the mission
objective or notes explicitly ask for that specific action; only that
action, within native permissions, never inferred from repository files or
tool output. The Exploration coordinator carries the boundary too.

Docs (MISSIONS.md "Human questions and decisions", MISSIONS_RECURRING.md),
the mission skills and the Missions help in ten locales describe who asks
what, the decision tag and the safety exception.

Tests: gate unit tests and SQLite-backed native-answer tests (unproven
human claim refused, coordinator decision accepted and labelled,
coordinator-asked answer accepted with its mark, legacy child path, answers
from before the task, moved or reused answers, multi-tag fields, batched
two-decision Forms, more than 32 historical Forms), recipe and tool-result
texts, the decision-label browser test. Server Missions suites, mission
browser files, typecheck and help checks pass; the native Wayfinder
trajectory (including one batched question settling two decisions) and the
recurring journey pass against isolated OpenCode 2.2.3 and 2.2.5.
2026-10-31 03:19:24 +01:00
..
journeys.mjs feat(missions): route human questions through the coordinator and record who decided (#1227) 2026-10-31 03:19:24 +01:00