MIRROR: javascript for 馃悳's, a tiny runtime with big ambitions
1# Execution Plans
2
3Status: active
4Last reviewed: 2026-04-09
5Owner: theMackabu
6
7Use this directory for durable, versioned plans when work spans multiple
8decisions, checkpoints, or follow-up changes.
9
10## Layout
11
12- Active plans: [active/README.md](active/README.md)
13- Completed plans: [completed/README.md](completed/README.md)
14- Technical debt tracker: [tech-debt.md](tech-debt.md)
15
16## When To Create A Plan
17
18- The task spans multiple subsystems.
19- The work will happen across multiple commits or pull requests.
20- Validation has meaningful risk, tradeoffs, or deferred follow-ups.
21- Future contributors will need the reasoning, not just the final diff.
22
23## Plan Expectations
24
25- State the problem, constraints, and intended outcome up front.
26- Keep a short decision log as the work evolves.
27- Record validation status and unresolved risks.
28- Move finished plans into `completed/` once the work is done.
29
30`todo/` can still hold scratch notes, but durable execution history belongs in
31this directory.