binky-control/DecisionQueue.md

# Decision Queue

> Status: live document — decisions awaiting the founder, as prepared
> approval packages (`AutonomyPolicy.md`). Agents append; Bernd resolves.
>
> **Resolving a decision (CUST-WP-0061-T05, 2026-07-21):** set
> `status: resolved` (plus `outcome`, `resolved_at`, `resolved_by`) directly
> on the item's own yaml block in place — don't move it to a separate log.
> `WORK-RECORDS.md` (generated by `statehub fix-consistency`) is the
> always-current view of every decision including resolved ones; that
> replaces the "## Resolved decisions" log below as the going-forward
> record. Existing log entries are historical (pre-canon) and stay as
> prose.

## Item template

```yaml
id: DEC-2026-NNN
title: ""
lane: yellow | orange | red
status: prepared | resolved | deferred
created_at: ""
needed_by: ""
attention_cost: ""
agent_recommendation: ""
evidence: []
options: [approve, reject, revise, defer]
fallback_if_no_response: ""
```

## Open decisions

### DEC-2026-005 — Qonto Governed Assistant: ratify Phase 1 architecture (BINKY-WP-0007-T01)

```yaml
id: DEC-2026-005
title: "Adopt domain-assistant architecture for Qonto access; repo home; v1 policy freeze; MCP transport; vendor MCP as internal backend"
lane: yellow
status: resolved
outcome: "approved as recommended (all five)"
resolved_at: "2026-07-22"
resolved_by: Bernd
consequence: "Domain-assistant (option B) adopted; new dedicated qonto-assistant
  repo is the build home; v1 hard-denies all spend/volume-cost tools with no
  exceptions; production MCP transport is remote streamable-HTTP only (stdio
  for local dev against the same binary); vendor qonto-mcp-server will not be
  run as an internal backend. BINKY-WP-0007-T01 done; T02 (service skeleton)
  unblocked."
created_at: "2026-07-22"
needed_by: ""
attention_cost: "~5 min — five bundled yes/no calls, one per line below"
agent_recommendation: "Approve all five as recommended (B / new qonto-assistant repo / hard freeze / streamable-HTTP only / no vendor MCP)."
evidence:
  - integrations/qonto-governed-assistant/ArchitectureBlueprint.md
  - workplans/BINKY-WP-0007-qonto-governed-assistant.md
  - integrations/qonto-mcp.md
options: [approve, reject, revise, defer]
fallback_if_no_response: "No Phase 1 build work starts (BINKY-WP-0007-T02+) until this resolves; T01 stays open."
questions:
  - q: "1. Adopt the domain-assistant architecture (blueprint option B: our own MCP+REST service owns the policy) over wiring vendor Qonto MCP into every harness, or a generic gateway alone?"
    recommendation: "Approve option B — only approach that encodes semantic no-spend policy in one place."
  - q: "2. Repo home for the assistant: new dedicated `qonto-assistant` repo (already present in the state-hub registry) vs. waiting for a future generic `finance-connect` monorepo?"
    recommendation: "New `qonto-assistant` repo now — don't block dogfood on a monorepo that doesn't exist yet."
  - q: "3. v1 policy freeze: hard deny on all spend / volume-cost tools (transfers, cards, invoicing sends, plan changes), no exceptions in this phase?"
    recommendation: "Approve the freeze — matches existing Red-lane-forever stance from DEC-2026-004."
  - q: "4. MCP transport: remote streamable-HTTP only for production clients (no local stdio in prod)?"
    recommendation: "Approve — stdio only for local dev against the same binary."
  - q: "5. Ever run vendor `qonto-mcp-server` as an internal-only backend behind our policy gate?"
    recommendation: "No (blueprint default) — we already proved a direct REST client; fewer moving parts, no unmaintained vendor code in the trust boundary."
state_hub_decision_id: "089ed6d0-b491-488f-a051-122201babbfc"
```

## Resolved decisions

### DEC-2026-003 — Go for executor cutover (retire the cron bridge)

```yaml
id: DEC-2026-003
title: "Execute BINKY-WP-0004-T06: enable harness-scheduled Binky definitions, retire workstation cron bridge"
lane: yellow
status: resolved
outcome: approved and executed
resolved_at: "2026-07-21"
resolved_by: Bernd (prior approve) + agent cutover execution
state_hub_decision_id: "d47d288f-a76f-4e2f-b039-330028824397"
created_at: "2026-07-18"
consequence: "Workstation cron line removed 2026-07-21; railiance host timers
  installed (scripts/railiance-rhythm/); three completion event types verified.
  Continuous intake residual closed by BINKY-WP-0006 (finished 2026-07-22)."
evidence:
  - integrations/executor-cutover-runbook.md
  - integrations/harness-tenant-onboarding.md
  - OperatingRhythm.md
```

### DEC-2026-004 — Qonto MCP: create API key, provision OpenBao lane (read-only use)

```yaml
id: DEC-2026-004
title: "Provision Qonto API credentials for the self-hosted Qonto MCP server (read-only harness lane)"
lane: red
status: resolved
outcome: approved
resolved_at: "2026-07-19"
resolved_by: Bernd
state_hub_decision_id: "a2a9de69-5bc1-434a-9a61-508ff3c12edf"
consequence: "Founder executes the Red-lane provisioning at the next office
  hour, bundled with OH-2026-003's Qonto dashboard review: API key under
  /settings/integrations + bao kv put tenants/binky/qonto/api (procedure in
  integrations/qonto-mcp.md), plus plan tier/fee note for CostRunRate row 4.
  Design as approved: self-hosted qonto/qonto-mcp-server, read-only via
  harness tool allow-list, payments founder-only forever. BINKY-WP-0005-T05
  (first read-only pull) unblocks after provision."
evidence:
  - integrations/qonto-mcp.md
  - workplans/BINKY-WP-0005-qonto-mcp-integration.md
```

### DEC-2026-002 — Agent harness: one shared runtime repo

```yaml
id: DEC-2026-002
title: "Executor worker ownership: new thin repo vs. inside activity-core"
lane: yellow
status: resolved
outcome: "approved, rescoped: single shared `agent-harness` repo for ALL projects"
resolved_at: "2026-07-17"
resolved_by: Bernd
state_hub_decision_id: "63620255-59d0-4109-bdee-4d0644c450e5"
consequence: "Three-layer model: blueprints in kaizen-agentic; instances as
  declarative manifests + .kaizen state in consuming repos (no code, no
  credentials, named tool profiles, pinned harness major); agent-harness is
  the single credential holder / policy enforcer, deployed once on Railiance,
  multi-tenant — binky-control is tenant #1. executor-worker prototype
  adopted as the harness seed. Recorded as agent-harness ADR-001 +
  docs/architecture.md; foundation work in HARNESS-WP-0001."
```

### DEC-2026-001 — Ratify company canon v0

```yaml
id: DEC-2026-001
title: "Ratify company canon v0 (INTENT, AutonomyPolicy, and companion docs)"
lane: red
status: resolved
state_hub_decision_id: "14383059-7698-4566-a664-858e3d49ee8d"
outcome: approved with edits
resolved_at: "2026-07-16"
resolved_by: Bernd
edits: "Railiance role refined to reliable deployment & operations (code → SaaS ecosystems and products); Operational Knowledge added as fourth ecosystem pillar (value from experience). Edits propagated to EcosystemMap.md and DogfoodPolicy.md."
evidence:
  - INTENT.md (v1.0)
  - AutonomyPolicy.md
consequence: "Canon v1.0 in force; AutonomyPolicy lanes active; Green/Blue work may proceed unattended."
```