binky-control/.custodian-brief.md
custodian-sync 5e22a45cbf chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-07-17:
  - update .custodian-brief.md for binky-control
2026-07-17 12:20:35 +02:00

35 lines
1.3 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — binky-control
**Domain:** infotech
**Last synced:** 2026-07-17 10:20 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Bootstrap State Hub integration
Progress: 0/3 done | workplan_id: `6342819a-0567-4922-8a19-fc9ed68ad6b8`
**Open tasks:**
- · Review Generated Integration Files `f348200e`
- · Verify Local Developer Workflow `26d0b9ff`
- · Seed First Real Workplan `30562538`
### Workstation-Independent Executor
Progress: 0/6 done | workplan_id: `b800f91d-a377-45ec-8ff3-6e763c524dff`
**Open tasks:**
- · Task: Align executor ownership with kaizen WP-0006 and opt in binky-control `5741487d`
- · Task: binky_rhythm_status resolver in activity-core `b44af058`
- · Task: OpenBao lanes for the executor worker `e4740aa0`
- · Task: Executor worker MVP — one task end-to-end on Railiance `3cb36d02`
- · Task: Recurring mailbox scan through the executor `2fd2f523`
- · Task: Cut over — enable Binky definitions, retire the cron bridge `eb8c9860`
---
## MCP Orientation (when available)
If the state-hub MCP server is reachable, call:
`get_domain_summary("infotech")`
This provides richer cross-domain context.
If the MCP call fails, use this file as your orientation source.