binky-control/AutopilotWorkQueue.md

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

id: AWQ-011
title: "agent-harness brief-weekly via llm-connect (Friday review prep)"
lane: green
status: closed
outcome: promoted
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. Promoted to REIN-A-0003; production proof succeeded as
  ops_run ad0b05c4-8ad8-40c7-9985-75481728ae30 on 2026-08-08."
state_hub_intake_id: "019f8a9d-008b-7086-8f84-d72bd0d0a2a5"

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."
state_hub_intake_id: "019f8a9d-074e-7b27-a7c0-8a13153bcc7a"

id: AWQ-013
title: "Clarify IP ownership boundary: which repos/assets belong to the GmbH vs Bernd privately"
lane: green
status: open
origin: residual
origin_ref: UPC-WP-0002-T04
pulls_from: [CompanyReactivationPlan.md "Contracts & IP", AWQ-002, EcosystemMap.md IP note, RISK-002]
notes: "Gap found 2026-08-16 by UPC-WP-0002-T04 residual sweep: the Reactivation
  Plan states this is 'needed before selling ecosystem products', but no live
  work record owned it — it existed only as an unchecked checklist box. It gates
  G5/G6 (publish the OK Audit offer, then take money for ecosystem products),
  which is the immediate commercial move after the G1 OH drain, so it should not
  stay implicit.
  Distinct from AWQ-002: that one assembles IP *evidence* (self-billed
  Eigenentwicklung invoices → capabilities). This one is the *ownership
  determination* that consumes that evidence.
  Agent-lane part (green): build the inventory table — every repo/asset in the
  ecosystem, current holder, funding source (GmbH-invoiced vs private time),
  and any transfer/licence already documented. Founder verifies.
  Determination itself is NOT green: allocating or transferring IP between
  Bernd privately and the GmbH is Red-lane (contracts, possibly tax-relevant
  as verdeckte Einlage / Entnahme — worth a question to the StB once the
  OH-2026-001 mandate lands). Prepare, do not decide.
  2026-08-16 — green-lane evidence pass done: inventory/ip-ownership-inventory.md.
  Key inversion: ownership is NOT undetermined — LICENSE §2 (TRSL V1C1) already
  names Binky Hedgehog GmbH as Licensor 'holding the rights necessary' on 104 of
  117 repos. The open question is whether that published assertion is documented.
  No assignment/Einbringung/service-contract-with-IP-clause found anywhere in the
  estate (may exist in 2binky or the 2019 formation papers — founder check, step 1).
  Two further gaps found: (a) TRSL hangs on a Phase Manifest and NO manifest
  instance exists in any repo, only the spec+schema in target-revenue, so the
  licence identifies no Software/target/future-licence; (b) 12 repos have no
  LICENSE at all, incl. rapp-user-engine, rapp-tenant-engine, rapp-secrets-engine,
  soul-frame; and railiance-bootstrap asserts a third party ('Railiance
  Contributors', MIT). Blocked on AWQ-002 for the funding-source column."
state_hub_intake_id: "01a007c6-c11e-7bb6-bffa-62f0a54a3bb5"

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"

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"

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.