Commit graph

11 commits

Author SHA1 Message Date
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
ff579be1aa DEC-2026-004 approved: Qonto provisioning scheduled for next office hour
- 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>
2026-07-19 14:31:02 +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
7425750e2b DEC-2026-003: hub decision id write-back
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-18 13:55:15 +02:00
0978a0796e rhythm: 2026-07-18 daily brief + DEC-2026-003 cutover go package
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>
2026-07-18 13:48:24 +02:00
7c5e644d6f DEC-2026-002 resolved: agent-harness (single shared runtime)
- DecisionQueue: moved to resolved log with rescoped outcome (three-layer
  model; binky-control = tenant #1); hub decision resolved
- Secret lanes doc: identifiers renamed executor-worker → agent-harness
  before any provisioning happens
- Cutover runbook + WP-0004-T06: gate 1 done; deployment gate now points
  at HARNESS-WP-0001-T06/T07 in the agent-harness repo

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 23:37:16 +02:00
3c0404fdba DEC-2026-001: hub decision id written back (retroactive mirror)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 19:26:23 +02:00
d917883f83 DEC-2026-002: register in State Hub decisions view
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>
2026-07-17 17:21:41 +02:00
0f91a98d08 BINKY-WP-0004-T01: kaizen schedule opt-in + executor ownership decision
- .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>
2026-07-17 17:01:19 +02:00
5b1a4f62f5 Ratify company canon v1.0 (DEC-2026-001, approved with edits)
Founder edits: Railiance role refined to reliable deployment & operations;
Operational Knowledge added as fourth ecosystem pillar. Edits propagated to
EcosystemMap and DogfoodPolicy. DEC-2026-001 resolved; workplan task
BINKY-WP-0002-T01 closed in file and hub.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 03:15:11 +02:00
d6d5cf1a1d Add company canon v0 and bootstrap workplan
Canon: INTENT, CompanyReactivationPlan, EcosystemMap, AutonomyPolicy,
SuccessMilestones, OfferCatalog, DogfoodPolicy, ControlLoopCatalog,
DecisionQueue, OfficeHourQueue, RiskRegister, plus founding exploration
in history/. Workplan BNKY-WP-0001 covers canon ratification, the first
internal audit, ecosystem cartography, flagship offer, and operating rhythm.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 02:48:50 +02:00