Skip to main content

WEEK-GOV — Weekly Governance Contract

Purpose​

Govern the week as a surface of time, roles, outputs, blockers, routines, and continuity.

The weekly board is not the full operating system. It is the dispatch surface that decides what gets activated this week.

Contract​

A week is governed when:

  • active fronts are visible;
  • day roles are respected;
  • 1-3 visible outputs are named;
  • homeostasis and maintenance are not invisible;
  • externalization has at least one possible slot;
  • Friday or Sunday leaves a bridge to Monday;
  • the board remains usable on paper.

Inputs​

  • Weekly board
  • Previous weekly packet
  • Carry State
  • Active fronts
  • Known blockers
  • 14-day cycle status, if active
  • Quarterly/seasonal frame, if under review

Outputs​

  • Weekly orientation
  • Active fronts
  • Visible outputs
  • Blockers / not-now list
  • Monday bridge
  • Routes to activate this week

Tick valid when​

The week has a readable shape and the first serious block can be selected without reconstructing context.

Stop rule​

Do not turn weekly governance into full quarterly planning unless that is the explicit scheduled agenda.

Last updated on