Skip to main content

User Guide — Rolling Through the Week

Use this system lightly. The board is for orientation. The cards are for action. The support index is for links. The full context is for redesign.


Core Rule​

Do not make the weekly board carry the whole system.

The weekly board shows:

  • time blocks;
  • route ticks;
  • contracts alive;
  • visible outputs;
  • blockers;
  • not-now.

Everything deeper lives elsewhere.


Start of Week​

Use WEEK-GOV.

Decide:

  • primary front;
  • 1-3 visible outputs;
  • which routes matter this week;
  • what is not-now;
  • whether FIN-W, CARRY-W, HOUSE, BODY, GYM need attention.

Do not plan every project.


Morning​

Use BOOT.

Ask:

  • What is today’s role?
  • What does the next pointer say?
  • What is the first runnable block?
  • What output would make the block real?
  • What should not be opened?

Then start.


Maintenance Slots​

Use MAINT.

Good maintenance:

  • prepares next block;
  • closes small loops;
  • checks finance/carry/body/house routes;
  • fixes broken context;
  • reduces friction.

Bad maintenance:

  • open-ended debugging;
  • full redesign;
  • project sprawl;
  • avoidant cleaning of everything.

Focus Blocks​

Use FOCUS.

A focus block should leave one of:

  • artifact;
  • draft;
  • commit;
  • message;
  • report;
  • deployment;
  • state update;
  • next pointer.

No evidence means the block may have been thinking, not operating.


Gym / Body / House​

These are not side quests.

They are homeostasis.

Use:

  • GYM-GOV for training quality;
  • BODY-GOV for useful body signals;
  • HOUSE-GOV / CLN-30 for environment.

Keep them bounded.


Finance​

Use FIN-W Friday and/or Sunday-Monday.

The goal is not deep financial analysis.

The goal is:

  • no missed vencimiento;
  • no ambiguous payment;
  • no unregistered important item;
  • no forgotten claim/reply.

Externalization​

Use EXTERNAL, preferably Thursday.

A week should try to change at least one external surface:

  • send;
  • publish;
  • contact;
  • deliver;
  • ask for feedback.

This keeps the system from becoming private refinement.


Closing the Day​

Use CLOSE.

Write the smallest useful next pointer.

Do not run a full review.


Closing the Week​

Use CARRY-W and Monday Bridge.

CARRY-W reconciles project state.

Monday Bridge makes restart cheap.

The Monday Bridge lives on its own sheet, not inside the weekly board diagram.


When Stuck​

If stuck, do not add more system.

Ask:

  1. Is the next action unclear?
  2. Is the right route card missing?
  3. Is the state source missing?
  4. Is there too much active work?
  5. Is this actually a maintenance problem?
  6. Is this an externalization problem?

Then route accordingly.