Design for an MCP gateway control plane so multiple agent harnesses
share one enforced read-only policy against the Qonto API, instead of
each client trusting its own local tool allow-list. Follows up on
BINKY-WP-0005.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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).
Host LLM_CONNECT_URL discovery uses ClusterIP when DNS is unreachable;
mail path fails hard if triage fails. Mark T06 done and workplan finished;
update residual docs (OperatingRhythm, cutover runbook, llm-rhythm).
Reject Claude Code (or any coding agent) on railiance01. Mail-scan stays
deterministic; triage/briefs use llm-connect HTTP → structured JSON →
deterministic apply. Document in integrations/railiance-llm-rhythm.md and
rewrite WP-0006 tasks accordingly; timers no longer require_claude.
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.
- 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>
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.
- 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>
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>
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>
