Crew board of directors

What it is

A checkpoint is one board meeting. It is due on the crew's own timer of active work — time in which the crew's records actually changed — not on the wall clock, so a mission that sits idle slides instead of being reviewed for the sake of it. Twelve hours of nothing opens one anyway, so a stalled crew can never go unseen.

A resolution is valid only when all three directors answered AND the chair wrote one. Anything less is recorded as unknown with the reason, never as a verdict, and an unknown changes nothing at all.

The board is OFF per mission until someone puts that mission on the pilot, because a scheduled board is real model spend (three directors, up to three debate rounds and a chair).

Where to find it

• The crew dashboard, in the Overseers hub, in the Board of directors card: the latest resolution with its verdict, priorities and dissent; the ones before it; the crew's timer (its interval, the lead's reason for it, how active work is measured, and when the next one is due); and how many board points still wait for the lead's ruling.
• GET /crew/board — the same read for an agent, with ?history=N.
• POST /crew/board/run — one board by hand for the lead's own mission.
• POST /crew/board/pilot — put a mission on the pilot, or take it off.
• POST /crew/board/timer — the lead sets its crew's interval, { hours, reason }.
• Board points appear as ordinary findings on the same dashboard, tagged Board of directors.

How it behaves

• One way off only tells you why. The first valid way-off resolution raises exactly one card explaining what the board saw and what it would do first. Nothing moves.
• Two way offs an hour apart replace the lead. A second valid way-off ruling at least an hour behind the first hands the post to a fresh lead through the same fresh-start machinery a full conversation uses. Two closer together than an hour change nothing. A board that finds a fresh start already armed waits for the next checkpoint instead.
• The new lead reads the board first. When the board sent the post on, the successor's briefing carries the board's resolution — verdict, top three priorities, dissent — ABOVE the outgoing lead's own hand-off note, and that note's heading says it was disputed by the board, with the date.
• An adjustment must be answered. Each point becomes a proposal on the crew's own finding road: a task the lead closes as done naming the move that makes it stick (a move, a check, a playbook change, or an owner card), or drops with its reason. A point nobody rules on stays visible on the dashboard and is raised to the lead until it is answered. A point whose twin is still open is not raised twice.
• The board answers a question the mission review used to ask. While a crew's board is its outside view, the six-hourly mission review drops its goal-alignment lens; every other lens keeps running, and a crew whose board is off keeps every lens. One switch decides, on by default.
• An owner message makes it look again. A message from the owner to the lead makes that crew's board check the mission immediately, whatever its timer says.
• The lead tunes the rhythm. The interval defaults to four hours and the lead may set one to twelve with a stated reason, which the dashboard shows. A tighter interval suits many workers, fast change or a recent adjustment; a looser one suits a run of on-course rulings.
• Everything survives a restart. The interval, the accrued minutes and the next due time live in the database and are read back, so a crash resumes the same clock rather than restarting it.

Related

• Board of directors contract — the invariants this page describes, each with the check that guards it.
• Agent Crews · Agent Crews — part 2
• Crew task delivery — where each crew task has got to.
• Judged checks — the other way a crew proves a promise the app can read.