tegwick
d2f68f0f53
Company-agnostic flagship-offer template generalized from the Binky dogfood run. audit-core assessed as home candidate — it owns audit event logging, not company audits, so the template stays in binky-control. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
3.1 KiB
| id | title | status |
|---|---|---|
| BINKY-WP-0003 | Autopilot Execution & Recurring Rhythm | active |
Turn the operating rhythm from pull-based (founder-initiated sessions) into scheduled, then event-driven execution. Near-term: work off the highest-value AutopilotWorkQueue items and bridge scheduling with a workstation cron. End state: activity-core triggers the rhythm and llm-connect executes it independently of this workstation, with kaizen-agentic providing the agent personas — real automated work driven by real-world events (company email, paper mail, hub state). Successor to BINKY-WP-0002.
Task: Onboard company email into Net Kingdom / OpenBao (AWQ-007)
Prepare the OpenBao vault path and integration plan for bernd.worsch@binky-hedgehog.com; wire the mailbox toward the agent event loop (email-connect capability). Credential handover from the founder is a single Red-lane step at the end — everything else is Blue-lane preparation. Goal: StB replies and bank/authority notices reach the control plane.
id: BINKY-WP-0003-T01
status: done
priority: high
Task: Generalize audit template v1 from the Binky run (AWQ-001)
Turn audits/OK-Audit-v0-binky.md into a customer-ready, company-agnostic audit template v1 (candidate home: audit-core repo; keep a copy in this repo). Flagship-offer dependency (OfferCatalog.md). Green lane.
id: BINKY-WP-0003-T02
status: done
priority: medium
Task: Consolidated cost & run-rate table (AWQ-004)
Desk, Qonto, DATEV, Stripe, infra: one table with monthly run-rate, feeding the cash/runway view (Finance Steward loop). Sources: audit v0, DUO once accessible, founder confirmation for gaps. Green lane.
id: BINKY-WP-0003-T03
status: todo
priority: medium
Task: Bridge scheduler — workstation cron for the operating rhythm
Schedule a recurring Claude Code session on this workstation that runs queue hygiene, writes the daily brief, and pulls one autopilot item when idle (OperatingRhythm.md). Explicitly a bridge until T05/T06 land; document the schedule and how to disable it. Blue lane.
id: BINKY-WP-0003-T04
status: done
priority: high
Task: Wire binky-control rhythm into activity-core
Write activity-definitions for the recurring items (daily brief + queue hygiene, weekly paper-mail intake check AWQ-008, weekly review) so scheduling lives in the sanctioned coordination layer. Verify activity-core deployment state and where dispatched work items land. Green/Blue lane.
id: BINKY-WP-0003-T05
status: todo
priority: medium
Task: Assess llm-connect as workstation-independent executor
Note (founder, 2026-07-16): llm-connect should enable real automated work triggered by activity-core, running independently from this workstation — and should connect well with kaizen-agentic (agent personas from the hub). Assess: current llm-connect capability, how activity-core dispatch reaches it, how a kaizen-agentic persona is loaded into an llm-connect execution, and what secrets/access it needs (OpenBao, T01 groundwork). Output: architecture note + follow-up workplan proposal. Green lane (assessment only).
id: BINKY-WP-0003-T06
status: todo
priority: medium