Live custody path tenants/binky/qonto-api (API_KEY/API_USER). First read-only
thirdparty pull (122 txs): desk 297.50 €/mo, Qonto plan 70.80 €/mo, main
balance 2185.94 €. Evidence under finance/; workplan status finished.
Prepare first-pull path after DEC-2026-004: copy-paste founder provision,
CCR apply, catalog promote, and CostRunRate update steps. T05 still waits
on Red-lane API key provision.
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>
First fix-consistency run with the new C-33 check: a cross-cutting,
file-derived index of every work record in this repo (5 workplans, 31
tasks, 3 intake items, 4 decisions, 5 engagements) -- the orientation
view the work-record architecture was designed to provide, generated
not hand-maintained.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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>
Wires the canon work-record validation workflow (repo-seed template).
Local proof: 45 records checked, 0 errors, 0 warnings — AWQ/DEC/OH ids
pass grandfathered, zero renames (the acceptance test for the
grandfathering design).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- DecisionQueue: DEC-2026-004 → resolved (approved, Bernd, 2026-07-19);
hub decision a2a9de69 resolved
- OH-2026-003 enriched with the Red-lane provisioning steps (API key +
bao kv put per integrations/qonto-mcp.md) for the dashboard visit
- qonto-mcp.md checklist: approval done, provisioning next
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- 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>
Queue hygiene: DecisionQueue gained the missing prepared package for the
now-unblocked BINKY-WP-0004-T06 cutover; OfficeHourQueue and
AutopilotWorkQueue healthy (hub fix-consistency skipped — green lane,
no network).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Extend .kaizen/schedule.yml with harness fields for daily rhythm, weekly
mail intake, and weekly review-prep; add task files, onboarding handoff
doc, and cutover gate updates for BINKY-WP-0004-T06.
Hub decision 63620255 (open, pending) linked to the WP-0004 workplan;
id written back here. DecisionQueue.md items were previously file-only
and invisible to /decisions/ and the pending_decisions resolver.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Lane 1 (LLM provider): reuse verified — warden catalog
openrouter-llm-connect, policy workload-kv-read-llm-connect-provider-secrets
- Lane 2 (forgejo deploy key): new, per-repo write deploy key design,
founder Red lane
- Lane 3 (mail-scan AppRole): executor-worker-binky-mail bound to the
existing IMAP read policy — closes email checklist item 9's auth
blocker on paper; provisioning founder Red lane
- No secret values anywhere; T04 can proceed on Lane 1 alone
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- .kaizen/schedule.yml scaffolded via schedule init, validates clean
(coach + optimization weekly, tdd-workflow disabled)
- DEC-2026-002 prepared: executor worker in a new small repo, per
ADR-005 boundaries; fallback allows sandbox prototype, no cutover
before resolution
- Decision rationale recorded in the executor assessment
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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>
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>
Crontab line active (weekdays 08:23). chmod +x had been lost when the
original install command was denied — without it every cron run would
have failed silently.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
4 vCPU / 16 GB at 25,19 EUR/mo, 24-month commitment (~604,56 EUR total,
to ~2028-07). Documented run-rate floor now ~100 EUR/mo. Added note that
this table feeds adaptive-pricing's allocated_fixed_cost (cost floor) —
adaptive-pricing consumes cost data, it does not capture it.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Deployment verified: production-backed on Railiance, issue-core REST sink,
TaskExecutorWorkflow still a stub (llm-connect's slot). Definitions landed
disabled in activity-core commit b2fa964; enablement needs the
binky_rhythm_status resolver + an executor.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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>
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>
