Fold Mxit Change

fold:mxit:change — Structured Change Lifecycle

Manage non-trivial work as a self-contained change with proposal, specs, design, and tasks. Each change is a folder. When done, archive it — the decision history is preserved forever.

When to use

• User says "let's add X" or "I want to build Y" (non-trivial feature)
• Work spans multiple files or sessions
• You want to preserve WHY something was built, not just WHAT
• You want to think before coding

Don't use for: Quick bug fixes, one-line changes, or tasks that fit in a single TASKS.md entry.

The change directory

changes/
  add-dark-mode/
    PROPOSAL.md         <- WHY (always required, even for small changes)
    SPECS.md            <- WHAT changes (optional, delta format)
    DESIGN.md           <- HOW (optional, technical decisions)
    TASKS.md            <- Implementation checklist (mxit format)
  fix-auth-timeout/
    PROPOSAL.md         <- Small change, just proposal + tasks
    TASKS.md
  archive/
    2026-03-26-add-websockets/
      PROPOSAL.md       <- Full context preserved
      SPECS.md
      DESIGN.md
      TASKS.md          <- With [done: ...] results on every task