Commit graph

15 commits

Author SHA1 Message Date
99d4b450fc chore(consistency): write back AWQ-011/012 intake UUIDs
All checks were successful
Work Records / validate (push) Successful in 20s
Hub registration for residual intakes from BINKY-WP-0006 handoff.
2026-07-22 18:19:22 +02:00
062947c91a docs: residual convention + AWQ-011/012 handoffs for WP-0006
All checks were successful
Work Records / validate (push) Successful in 23s
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
5f5f74c017 CUST-WP-0061-T05: retarget queue closures to WORK-RECORDS.md (generated)
All checks were successful
Work Records / validate (push) Successful in 22s
Convention change, not new code: closing an item now means setting its
terminal status (status: closed/resolved/done + outcome where
applicable) directly on the item's own yaml block in place, instead of
deleting it and hand-writing a bullet in a separate "Completed"/
"Resolved decisions" log. WORK-RECORDS.md (CUST-WP-0061-T04, generated
by fix-consistency's C-33) already lists every closed/resolved/done
record with status/lane/source -- that supersedes the hand-maintained
logs as the going-forward view.

- AutopilotWorkQueue.md: closing note added; "## Completed" relabeled
  "(historical -- pre-canon, 2026-07-21)", frozen as-is, nothing
  migrated or deleted
- DecisionQueue.md: closing note added -- its "## Resolved decisions"
  entries were already structured as in-place yaml blocks with
  status: resolved (ahead of AWQ's convention already), so this only
  clarifies the log is superseded going forward, no structural change
- OfficeHourQueue.md: closing note added -- items already live under
  "## Queued items" with status: queued|prepared|done in place, no
  separate log ever existed here
- OperatingRhythm.md: queue-hygiene checklist updated to describe
  in-place status transitions instead of "moved to the log"; added
  item 5 noting WORK-RECORDS.md needs no hand-maintenance

Re-ran fix-consistency: WORK-RECORDS.md content unchanged (correctly
idempotent -- these were prose-only edits, no yaml block content
changed).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-21 01:54:40 +02:00
5f43038353 C-32 registration: link real AWQ-002/003/006 to hub intake records
All checks were successful
Work Records / validate (push) Successful in 40s
Live verification of the new fix-consistency C-32 check
(state-hub CUST-WP-0061-T02): AWQ-002, AWQ-003, AWQ-006 were open,
never-registered intake items in AutopilotWorkQueue.md. C-32 created
real hub intake records for each and wrote state_hub_intake_id back —
the exact registration gap the work-record canon was built to close,
caught on real, non-synthetic data on its first run.

(A throwaway BINKY-IN-9001 test block used to trigger this run was
never git-tracked and has been removed from disk; its hub record was
closed declined as cleanup.)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-21 00:47:49 +02:00
3cfb9f553c BINKY-WP-0005: Qonto MCP integration — workplan registered, design + DEC-2026-004
- AWQ-010 promoted to workplan BINKY-WP-0005 (hub 6139db83, tasks T01-T05
  registered via fix-consistency C-06); queue item moved to Completed
- integrations/qonto-mcp.md: self-hosted qonto/qonto-mcp-server chosen over
  hosted mcp.qonto.com OAuth connector (no-native-integrations policy);
  OpenBao lane tenants/binky/qonto/api mirroring company-email custody;
  read-only via harness tool allow-list, payments Red lane forever;
  consumers: Finance Steward rhythm, CostRunRate TBC rows, OH-2026-003
- DEC-2026-004 prepared (founder Red lane: API key + bao kv put), hub
  decision a2a9de69

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-19 14:26:55 +02:00
06afc317f1 mail triage 2026-07-18 (founder) + AWQ-010 Qonto MCP integration
- E-mail triage log section added: jamesandersons spam resolved by
  founder; IHK Sommerfest invitation (August, founder calendar call);
  Qonto MCP mailing -> actionable
- AWQ-010: Qonto MCP integration prep (read scopes first, ops-warden/
  OpenBao credential lane, no native integrations; complements DUO =
  DATEV Unternehmen Online as main accounting, does not replace it)
- OH-2026-003 enriched: MCP integration is an argument FOR keeping
  Qonto; check API/plan prerequisites while in the dashboard

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-18 17:03:07 +02:00
9cf9788599 rhythm bridge 2026-07-17: queues clean, daily brief; AWQ-003 evidence from mailbox scan (Sedo account, IONOS registrar)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 10:57:11 +02:00
4fb7cc7726 AWQ-009 done: Stripe webhook failure = stale Blobr preprod endpoint
DNS for api.preprod.blobr.dev (and blobr.dev) no longer resolves; Stripe
has sent monthly failure digests since April. Deletion is a founder
dashboard action, prepared as OH-2026-005 incl. webhook-endpoint
inventory while in the dashboard.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 10:54:52 +02:00
686d2d3dbf email lane live: first read-only mailbox scan (93 messages)
Scan c3c7e784 via warden/OpenBao lane, evidence CSV in mailmeta/reports/
(metadata only; sqlite state gitignored). Checklist item 8 done. New
AWQ-009: Stripe webhook delivery failure noticed 2026-07-05 — first
real-world event caught by the lane. Two suspicious external mails
logged, not acted on.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 00:47:50 +02:00
f53f05cf53 rhythm bridge 2026-07-16: queue hygiene clean; AWQ-005 website draft; include AWQ-008 paper-mail intake artifacts + hub id sync
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 15:02:48 +02:00
306a8cd232 BINKY-WP-0003-T03: cost & run-rate table v1 (AWQ-004)
Evidence from 2binky archive: FSW DATEV pass-through 483,69 EUR/yr, HUB31
desk contract renewed to 2027-04, private-card company costs (bubble.io,
AI subs), open 450 EUR Binect receivable. Audit corrected: desk landlord
is HUB31; Binect is income side.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 10:59:04 +02:00
d2f68f0f53 BINKY-WP-0003-T02: OK audit template v1 (AWQ-001)
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>
2026-07-16 10:56:17 +02:00
bc49a24c4c BINKY-WP-0003-T01: company email → OpenBao integration plan (AWQ-007 prep)
Vault path prod/binky/company-email/imap, secrets-engine catalog draft,
email-connect read-only IMAP wiring. Credential handover stays a single
Red-lane founder step.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 10:50:29 +02:00
e287b90510 Founder review corrections: company email exists; two real-world intake loops queued
bernd.worsch@binky-hedgehog.com corrected in audit + reactivation plan.
AWQ-007: onboard company email/credentials into Net Kingdom / OpenBao.
AWQ-008: weekly paper-mail scan intake pipeline.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 10:27:31 +02:00
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