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 · 2026-07-16 15:02:48 +02:00 · f53f05cf53
commit f53f05cf53
parent 86aa02c90a
5 changed files with 139 additions and 19 deletions
--- a/AutopilotWorkQueue.md
+++ b/AutopilotWorkQueue.md
@ -21,14 +21,6 @@ pulls_from: [CompanyReactivationPlan.md digital presence]
 notes: "Decision on primary domain is Yellow — prepare package only"
 ```

-```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"
@ -36,17 +28,6 @@ lane: green
 pulls_from: [EcosystemMap.md cartography v0 caveat]
 ```

-```yaml
-id: AWQ-008
-title: "Design weekly paper-mail scan intake pipeline"
-lane: green
-pulls_from: [audits/OK-Audit-v0-binky.md digital presence]
-notes: "Founder provides scanned paper mail ~weekly. Define drop location, naming
-  convention, triage step (obligation? deadline? receipt → DUO Belegablage?), and
-  routing into queues/RiskRegister. Candidate capabilities: evidence-and-citation
-  cluster, audit-core. Start manual, automate later."
-```
-
 ## Pull protocol

 Take the top item you can complete, mark it `in_progress` with your agent
@ -55,6 +36,16 @@ with a one-line outcome.

 ## Completed

+- **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
--- a/integrations/paper-mail-intake.md
+++ b/integrations/paper-mail-intake.md
@ -0,0 +1,61 @@
+# Paper-Mail Intake Pipeline (AWQ-008)
+
+> Status: designed v1 — 2026-07-16. Founder provides scanned paper mail
+> ~weekly. Start manual, automate later. Weekly check is already proposed in
+> activity-core (`binky-weekly-mail-intake`, disabled) and fits the rhythm
+> bridge until then.
+
+## Flow
+
+```text
+founder scans (~weekly)
+  └─ drop: ~/2binky/mailinbox/            (outside git — originals stay put)
+       └─ triage (agent, weekly; manual for now)
+            ├─ obligation / deadline → OfficeHourQueue or DecisionQueue
+            │     └─ risk-relevant?  → RiskRegister entry/update
+            ├─ receipt / invoice    → stage for DUO Belegablage upload
+            │     └─ ~/2binky/mailinbox/to-duo/   (founder uploads until
+            │        DUO access is agent-reachable; RISK-007)
+            ├─ informational        → archive only
+            └─ all items            → metadata row in mailmeta/mail-log.md
+       └─ after triage: move file to ~/2binky/archiv/<YYMMDD><x>-<slug>/
+          (founder's existing archive convention)
+```
+
+## Conventions
+
+- **Drop location:** `~/2binky/mailinbox/` — flat, PDFs only. Not in any git
+  repo: scan contents (bank, tax, personal data) stay off the forge; the
+  control plane only carries metadata.
+- **File naming:** `YYMMDD-<sender>-<topic>.pdf`, matching the founder's
+  existing `~/2binky` dating style (e.g. `260718-finanzamt-vorauszahlung.pdf`).
+  Date = letter date if visible, else scan date. Unnamed drops are fine —
+  triage renames.
+- **Metadata log:** `mailmeta/mail-log.md` in this repo. One row per item:
+  date, sender, type, deadline (if any), routing decision, archive location.
+  Never scan content, amounts only when needed for queue routing.
+- **Triage questions per item (in order):**
+  1. Does it create an **obligation or deadline**? → queue it (OfficeHour for
+     external contact, DecisionQueue for founder decisions) with the deadline;
+     RiskRegister if missing it would hurt.
+  2. Is it a **receipt/invoice**? → move to `to-duo/`, note in log; founder
+     empties `to-duo/` into DUO Belegablage until agent access exists.
+  3. Neither → log + archive.
+- **Cadence:** weekly, Monday (aligned with `binky-weekly-mail-intake`,
+  Mon 09:37 proposed). The rhythm bridge may run triage when scans are
+  present. Empty inbox = one log line "no mail week YYYY-WW" — silence is
+  not evidence.
+
+## Automation ladder
+
+1. **Now (manual):** agent triages during rhythm/founder sessions.
+2. **Next:** OCR + classification assist (evidence-and-citation cluster);
+   deadline extraction into queue entries automatically.
+3. **Later:** DUO Belegablage upload automated (needs mandate transition,
+   RISK-007, and credentials via the OpenBao lane like AWQ-007); intake
+   events emitted to activity-core instead of cron-checked.
+
+## Founder setup (one-time)
+
+`mkdir -p ~/2binky/mailinbox/to-duo` — then drop scans as they come; no
+naming required, weekly triage handles the rest.
--- a/mailmeta/mail-log.md
+++ b/mailmeta/mail-log.md
@ -0,0 +1,8 @@
+# Paper-Mail Log
+
+> Metadata only — scan contents never enter this repo. Pipeline:
+> `integrations/paper-mail-intake.md`. One row per item, newest first.
+
+| Date | Sender | Type | Deadline | Routed to | Archive |
+|------|--------|------|----------|-----------|---------|
+| — | — | — | — | *(no intake yet — pipeline designed 2026-07-16, awaiting first scan drop)* | — |
--- a/website/one-pager-draft.md
+++ b/website/one-pager-draft.md
@ -0,0 +1,53 @@
+# One-Page Company Website — Draft v1
+
+> Status: draft — 2026-07-16, AWQ-005 (agt-rhythm-bridge). Blue lane: draft
+> only. **Publishing is a Yellow-lane decision** (needs domain choice AWQ-003
+> and founder approval). Copy uses the ratified transition wording from
+> `CompanyReactivationPlan.md`.
+
+## Page copy
+
+---
+
+### Binky Hedgehog GmbH
+
+**Operational knowledge infrastructure for agentic, secure, and
+self-improving organizations.**
+
+Companies increasingly fail not because they lack tools, but because their
+operational knowledge is fragmented, implicit, ungoverned, and not
+executable. We build the infrastructure — and run our own company on it —
+that turns operational knowledge into structured, governed, agent-ready
+company capabilities.
+
+#### What we offer
+
+**Operational Knowledge Audit** — a structured assessment of your company's
+operational knowledge: where it lives, what is implicit, what is ungoverned,
+and what an agent-ready operating model would require. Delivered as a
+concrete findings report with a prioritized capability roadmap.
+
+We run every offer on ourselves first. This company operates as a
+human-on-the-loop, agent-driven organization — our own operations are the
+first customer and the standing proof.
+
+#### Contact
+
+bernd.worsch@binky-hedgehog.com
+
+---
+*Impressum / legal footer — see open items below.*
+
+---
+
+## Open items before publishing (not part of the page)
+
+- **Domain**: `binky-hedgehog.com` is owned; primary-domain decision pending
+  (AWQ-003, Yellow).
+- **Impressum (§ 5 DDG, mandatory for a German commercial site)**: needs
+  registered address, HRB number + Registergericht, Geschäftsführer,
+  USt-IdNr. — exact registry details pending verification (OH-2026-004).
+- **Offer wording**: flagship offer is *drafted*, not published; naming the
+  audit publicly with a price is a Yellow-lane decision (OfferCatalog.md).
+- **Hosting**: static single page; candidate is a Railiance-deployed static
+  host (dogfood evidence) — decide with the domain decision.
--- a/workplans/BINKY-WP-0003-autopilot-and-rhythm.md
+++ b/workplans/BINKY-WP-0003-autopilot-and-rhythm.md
@ -2,6 +2,7 @@
 id: BINKY-WP-0003
 title: "Autopilot Execution & Recurring Rhythm"
 status: done
+state_hub_workstream_id: "865c0ebe-a452-40c1-a346-c0fbd1c83c19"
 ---

 Turn the operating rhythm from pull-based (founder-initiated sessions) into
@ -24,6 +25,7 @@ StB replies and bank/authority notices reach the control plane.
 id: BINKY-WP-0003-T01
 status: done
 priority: high
+state_hub_task_id: "3c789a3f-f693-4958-afe5-bc6ce56728de"
 ```

 ## Task: Generalize audit template v1 from the Binky run (AWQ-001)
@ -36,6 +38,7 @@ repo). Flagship-offer dependency (OfferCatalog.md). Green lane.
 id: BINKY-WP-0003-T02
 status: done
 priority: medium
+state_hub_task_id: "e52770e7-30dc-4869-95d4-6ae494f0c0b2"
 ```

 ## Task: Consolidated cost & run-rate table (AWQ-004)
@ -48,6 +51,7 @@ accessible, founder confirmation for gaps. Green lane.
 id: BINKY-WP-0003-T03
 status: done
 priority: medium
+state_hub_task_id: "ebfe6a71-8388-4fdd-81f6-55fdc40d541d"
 ```

 ## Task: Bridge scheduler — workstation cron for the operating rhythm
@ -61,6 +65,7 @@ the schedule and how to disable it. Blue lane.
 id: BINKY-WP-0003-T04
 status: done
 priority: high
+state_hub_task_id: "8e9b58bb-c628-4b58-9419-e886d83418cf"
 ```

 ## Task: Wire binky-control rhythm into activity-core
@ -74,6 +79,7 @@ state and where dispatched work items land. Green/Blue lane.
 id: BINKY-WP-0003-T05
 status: done
 priority: medium
+state_hub_task_id: "93459c6e-670f-4a8b-8120-04fe12b16c2e"
 ```

 ## Task: Assess llm-connect as workstation-independent executor
@ -90,4 +96,5 @@ note + follow-up workplan proposal. Green lane (assessment only).
 id: BINKY-WP-0003-T06
 status: done
 priority: medium
+state_hub_task_id: "9549a5d0-4c1e-48ba-b55e-e116bae62999"
 ```