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>

AutopilotWorkQueue.md

@@ -0,0 +1,62 @@
+# Autopilot Work Queue
+
+> Status: live document — evergreen Green/Blue work any agent may pull when
+> idle. Keep ordered by leverage; never let it run empty (OperatingRhythm.md).
+
+## Queue
+
+```yaml
+id: AWQ-001
+title: "Generalize audits/OK-Audit-v0-binky.md into a customer-ready audit template v1"
+lane: green
+pulls_from: [OfferCatalog.md flagship dependencies]
+```
+
+```yaml
+id: AWQ-002
+title: "Map self-billed Eigenentwicklung invoices to ecosystem capabilities as IP evidence"
+lane: green
+pulls_from: [RISK-002, EcosystemMap.md IP note]
+notes: "Inputs live in DUO Belegablage / 2binky archive; prepare mapping table, founder verifies"
+```
+
+```yaml
+id: AWQ-003
+title: "Domain inventory: enumerate owned domains, propose primary company domain shortlist"
+lane: green
+pulls_from: [CompanyReactivationPlan.md digital presence]
+notes: "Decision on primary domain is Yellow — prepare package only"
+```
+
+```yaml
+id: AWQ-004
+title: "Consolidated cost & subscription table (desk, Qonto, DATEV, Stripe, infra) with monthly run-rate"
+lane: green
+pulls_from: [audits/OK-Audit-v0-binky.md banking findings]
+notes: "Feeds cash/runway view (Finance Steward loop)"
+```
+
+```yaml
+id: AWQ-005
+title: "One-page company website draft using the transition wording"
+lane: blue
+pulls_from: [CompanyReactivationPlan.md digital presence]
+notes: "Draft only; publishing is Yellow"
+```
+
+```yaml
+id: AWQ-006
+title: "Refine EcosystemMap cartography maturity values as repos are touched"
+lane: green
+pulls_from: [EcosystemMap.md cartography v0 caveat]
+```
+
+## Pull protocol
+
+Take the top item you can complete, mark it `in_progress` with your agent
+name, finish or return it with a note. Completed items move to the log below
+with a one-line outcome.
+
+## Completed
+
+*(none yet)*

OperatingRhythm.md

@@ -0,0 +1,40 @@
+# 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:
+
+```markdown
+# 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.

briefs/2026-07-16-daily-brief.md

@@ -0,0 +1,22 @@
+# Daily Brief — 2026-07-16
+
+## Decide now
+*(nothing — DEC-2026-001 resolved today; no open decision packages)*
+
+## Progress
+- Canon **v1.0 ratified** (DEC-2026-001, approved with edits) — S-ladder foundation in place
+- **OK Audit v0 run on Binky itself**: filings current through JA 2024; four gaps queued (S3 dogfood loop: first full cycle done)
+- Ecosystem Map populated: 85 repos → 12 capability clusters
+- Flagship offer **drafted** (Operational Knowledge Audit, Level 1, price hypothesis 2.5–4.5k EUR)
+- Operating rhythm + autopilot queue established (this document set)
+
+## Risks
+- **New RISK-006 (high/high)**: no active Steuerberater mandate — JA 2025 uncovered; mitigation running (OH-2026-001)
+- **New RISK-007**: DUO receipt backlog + license dependency on former StB
+- RISK-001 downgraded to low/mitigating (filings verified current)
+- Operational: forgejo remote down — commits accumulate locally, auto-push on recovery
+
+## Best next hour
+Skim `audits/OK-Audit-v0-binky.md` (5 min) and confirm the four office-hour
+queue items are complete — they become the first Office-Hour Command Day
+runbook. No other founder action needed today.

workplans/BINKY-WP-0002-operating-kernel-bootstrap.md

@@ -72,7 +72,7 @@ Autopilot Work Queue with evergreen Green/Blue work. Blue lane.
 
 ```task
 id: BINKY-WP-0002-T05
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "98683baa-c7b0-4553-9526-c29841f28d85"
 ```