@async/dispatch

[Goal Seed] Draft

Draft scope: [domains, repos, systems, user flows, or decisions in scope].

This is a high-level task map. Each bullet is intentionally goal-sized and can

be split into implementation tasks later.

Goal Seed

Original goal seed: [raw goal seed]

Refined Goal Charter

  • Refined goal: [refined goal statement]
  • Purpose / bigger picture: [purpose]
  • Success proof / oracle: [proof]
  • Constraints:

- [constraint]

  • Non-goals:

- [non-goal]

  • Open questions:

- [open question]

  • Context gathered:

- [context note]

Cross-Domain Goals

  1. [Name the first cross-domain goal].

- [What must become true.]

- [What should stop happening.]

- [How this goal will be proven.]

  1. [Name the second cross-domain goal].

- [What must become true.]

- [Important constraints or edge cases.]

- [How this goal will be proven.]

[domain-a]

  1. [First domain outcome].

- [Goal-sized implementation direction.]

- [Expected verification or receipt.]

  1. [Second domain outcome].

- [Goal-sized implementation direction.]

- [Expected verification or receipt.]

[domain-b]

  1. [First domain outcome].

- [Goal-sized implementation direction.]

- [Expected verification or receipt.]

  1. [Second domain outcome].

- [Goal-sized implementation direction.]

- [Expected verification or receipt.]

Execution Order

  1. [Foundation or shared capability that must happen first].
  2. [Smallest low-risk domain to prove the pattern].
  3. [Next domain or dependency layer].
  4. [Larger or riskier domain].
  5. [Final external verification and settings].

The exact order can change if discovery finds dependency or state constraints,

but changes should be recorded as draft review decisions before compilation.

Missing Or Easy-To-Miss Work

  1. [External setting or permission that is easy to forget.]
  2. [Docs or command drift that should be searched explicitly.]
  3. [Metadata, packaging, API, or integration surface to verify.]
  4. [Cleanup, retention, migration, or rollback policy.]
  5. [A fallback policy for anything the system cannot express yet.]

Review Questions

  1. [Question the human must answer before board compilation.]
  2. [Tradeoff or ordering question.]
  3. [Scope or non-goal question.]

Ready-To-Compile Checklist

  • [ ] Goal charter matches the current intent.
  • [ ] Human review comments are recorded.
  • [ ] Reference map enrichment is complete, if this work needs stable IDs.
  • [ ] Review comments are resolved or accepted.
  • [ ] Open questions are either answered or explicitly deferred.
  • [ ] The next step is board compilation, not runtime execution.