binky-control/AutopilotWorkQueue.md
tegwick 062947c91a
All checks were successful
Work Records / validate (push) Successful in 23s
docs: residual convention + AWQ-011/012 handoffs for WP-0006
Align AGENTS, AutonomyPolicy, SCOPE, OperatingRhythm with fleet residual
role (live intakes, not SCOPE prose). Capture BINKY-WP-0006 leftovers as
AWQ-011 (brief-weekly) and AWQ-012 (open-weights retarget).
2026-07-22 18:15:45 +02:00

125 lines
5.9 KiB
Markdown

# 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).
>
> **Closing an item (CUST-WP-0061-T05, 2026-07-21):** set `status: closed`
> and `outcome: promoted | declined | absorbed` directly on the item's own
> yaml block in place — don't delete it and hand-write a bullet below.
> `statehub fix-consistency` (C-32/C-33) registers the closure and
> regenerates `WORK-RECORDS.md`, which is the generated, always-current
> view of every closed item (id, status, lane, source) — that replaces the
> "## Completed" log below as the going-forward record. The entries already
> in "## Completed" are historical (pre-canon) and stay as prose; nothing
> there needs migrating.
>
> **Residuals from finished workplans:** capture here as intakes with
> `origin: residual` and `origin_ref: <parent-WP-id>` (or spawn a workplan).
> Residual is a role, not a kind — see work-record-types § Residuals.
## Queue
```yaml
id: AWQ-011
title: "agent-harness brief-weekly via llm-connect (Friday review prep)"
lane: green
status: open
origin: residual
origin_ref: BINKY-WP-0006
pulls_from: [BINKY-WP-0006-T05/T06, OperatingRhythm.md weekly review]
notes: "Same pattern as brief-daily: structured JSON via llm-connect + markdown
apply + commit. Wire scripts/railiance-rhythm/run-review.sh; hub event
binky_weekly_review. Promote to workplan if scope grows beyond one session."
```
```yaml
id: AWQ-012
title: "Optional: retarget railiance llm-connect rhythm to open-weights model"
lane: green
status: open
origin: residual
origin_ref: BINKY-WP-0006
pulls_from: [BINKY-WP-0006-T03, integrations/railiance-llm-rhythm.md]
notes: "Current google/gemini-2.5-flash works; cost/open-weights lock deferred.
Measure triage quality on fixture CSV before changing ConfigMap. May land in
activity-core/llm-connect rather than binky-only."
```
```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"
state_hub_intake_id: "019f81b5-3a56-7a01-ae75-f0f5373d4edc"
```
```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.
Evidence from mailbox scan c3c7e784 (2026-07-17, agt-rhythm-bridge):
(a) Sedo account exists (automailer@sedo.co.uk 'Your account at sedo.com',
2026-05-22) — possible parked/marketed domains, check Sedo portfolio;
(b) binky-hedgehog.com mail is hosted at IONOS — IONOS contract list is
the likely authoritative registrar inventory. Full enumeration needs
IONOS + Sedo account access (not available to agents; founder or
office-hour pull)."
state_hub_intake_id: "019f81b5-4080-74de-b4b3-571452510a04"
```
```yaml
id: AWQ-006
title: "Refine EcosystemMap cartography maturity values as repos are touched"
lane: green
pulls_from: [EcosystemMap.md cartography v0 caveat]
state_hub_intake_id: "019f81b5-45ac-7bb8-a238-652c2443e7f6"
```
## 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 (historical — pre-canon, 2026-07-21)
> New closures go in the item's own block (`status: closed`) — see the
> note at the top of this file. This section is frozen history.
- **AWQ-010** (2026-07-19, agt-claude-workstation): promoted to workplan
**BINKY-WP-0005** (registered in hub). Integration package delivered:
`integrations/qonto-mcp.md` design (self-hosted qonto-mcp-server, NOT the
hosted OAuth connector; read-only via harness allow-list; OpenBao lane
`tenants/binky/qonto/api`) + DEC-2026-004 for the founder Red-lane API-key
provision. First pull (T05) waits on the decision.
- **AWQ-009** (2026-07-17, agt-claude-workstation): Stripe webhook failure
diagnosed — stale endpoint `api.preprod.blobr.dev` from the defunct Blobr
integration, DNS dead, monthly Stripe digests since April. Fix is a
founder dashboard action → prepared as OH-2026-005. No live revenue
impact identified from this endpoint itself.
- **AWQ-005** (2026-07-16, agt-rhythm-bridge): one-page website copy drafted
at `website/one-pager-draft.md` using the ratified transition wording;
flagship offer described without public pricing. Publishing blockers listed
in the draft: domain decision (AWQ-003), Impressum details (OH-2026-004),
offer-publishing decision — all Yellow.
- **AWQ-008** (2026-07-16): paper-mail intake pipeline designed —
`integrations/paper-mail-intake.md` + metadata log `mailmeta/mail-log.md`.
Drop: `~/2binky/mailinbox/` (one-time `mkdir -p ~/2binky/mailinbox/to-duo`
by founder); weekly Monday triage; scans stay out of git. Operation starts
with the first scan drop.
- **AWQ-004** (2026-07-16, BINKY-WP-0003-T03): cost & run-rate table v1 at
`finance/CostRunRate.md`. New findings: private-card company costs
(bubble.io $32/mo + AI subs), open 450 € Binect receivable, desk contract
runs to 2027-04; desk rent + Qonto plan amounts await the Qonto pull
(OH-2026-003).
- **AWQ-001** (2026-07-16, BINKY-WP-0003-T02): audit template v1 at
`templates/OK-Audit-Template-v1.md` — customer-ready, company-agnostic;
flagship-offer dependency cleared. Note: `audit-core` repo is event
logging, not the right home; template stays here for now.
- **AWQ-007** (2026-07-16, BINKY-WP-0003-T01): company-email → OpenBao
integration prepared — vault path, secrets-engine catalog draft, and
email-connect wiring in `integrations/company-email-openbao.md`. Remaining
steps (provider facts, Red-lane credential handover) tracked in that
document's checklist.