MAINT — Maintenance Hour
When
Use during M1, M2, or M3 maintenance slots.
Purpose
Reduce friction, clean operational state, and prepare the next execution block.
Inputs
- Maintenance quicklist
- Weekly board
- Inbox fragments
- Broken links
- Small operational debt
- House/body/finance/carry route if relevant
Steps minimum
- Choose one maintenance target.
- Bound it to the slot.
- Execute the smallest useful repair.
- Mark done, deferred, or next pointer.
- Avoid expanding into deep work.
Good MAINT examples
- Prepare the next focus block.
- Clean a link or file path.
- Close a small admin loop.
- Run CLN-30.
- Update a missing state field.
- Review a small checklist.
Bad MAINT examples
- Full refactor.
- Redesigning the whole board.
- Rebuilding a project plan.
- Unbounded debugging.
- Opening ten new fronts.
Output
Reduced friction or prepared execution.
Tick valid when
One real source of friction has been reduced, or a maintenance item was explicitly parked with a next pointer.
Stop rule
No open-ended repairs. If it exceeds the maintenance slot, convert it into a focus block or backlog item.