evolving-requirements-orchestration

To manage evolving requirements without task sprawl, reconcile new asks against the active epic by updating the source-of-truth brief before mutating any execution tasks, applying supersession precedence for newer approved changes.

Handling ambiguous founder requests requires a decision-first decomposition loop that breaks vagueness into concrete questions, resolving what changed and what must be true before updating the canonical brief and routing tasks.

Updating active epics when scope changes involves reconciling the new ask against the approved spec, updating the source-of-truth brief first, and then deciding whether to edit, split, or create net-new tasks while preserving provenance.

You should edit an existing task versus creating a net-new task by applying supersession precedence to newer approved requirements, evaluating the change against the canonical brief to prevent duplicate tasks and minimize task churn.

Yes, this requirements orchestration process routes canonical briefs to Notion and execution tasks to Mission Control, applying supersession-aware routing to maintain alignment between the source-of-truth and active task tree.