coulomb/binky-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
binky-control/OperatingRhythm.md
tegwick 8043bf532d Establish operating rhythm (BINKY-WP-0002-T05) 
OperatingRhythm.md (daily brief format, queue hygiene, weekly review),
AutopilotWorkQueue.md seeded with 6 evergreen items, first daily brief
written for 2026-07-16.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 09:15:38 +02:00

1.6 KiB
Raw Blame History

Operating Rhythm

Status: v0 — 2026-07-16 (BINKY-WP-0002-T05). The cadence that keeps the control plane honest. Blue lane: agents run it; the founder consumes it.

Daily brief

One brief per active day, written by whichever agent closes the day's work, stored in briefs/YYYY-MM-DD-daily-brief.md. Hard cap: one screen. Format:

# Daily Brief — <date>

## Decide now          (0–3 items, each linked to DecisionQueue)
## Progress            (what moved, milestone-relevant only)
## Risks               (changes to RiskRegister only — no restating)
## Best next hour      (single highest-leverage founder action)

Rules:

  • Decide now only lists prepared decision packages. Never raw questions.
  • Best next hour is one item. If nothing needs the founder, say so — "no founder action needed today" is a valid and desirable outcome.
  • Anything that can't fit the cap goes into a queue, not the brief.

Queue hygiene (every agent session touching this repo)

  1. DecisionQueue.md — resolved items moved to the log; nothing older than 14 days without escalation (RISK-003 rule).
  2. OfficeHourQueue.md — every queued item has prepared material before the next command day; stale items pruned.
  3. AutopilotWorkQueue.md — never empty; agents with idle capacity pull from the top.
  4. Workplan files match hub state (fix-consistency covers drift).

Weekly review (founder, ~15 min)

Read the newest brief + SuccessMilestones.md. One question: did anything move a milestone? If two consecutive weeks show activity without milestone movement, RISK-005 escalates.