the-custodian/.custodian-brief.md
custodian-sync 6f9c3f7fa3
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-07-21:
  - update .custodian-brief.md for the-custodian
2026-07-21 00:29:11 +02:00

32 lines
1.3 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — the-custodian
**Domain:** infotech
**Last synced:** 2026-07-20 22:29 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Work-record stage 3 — intake entity, promotion transition, generated index
Progress: 1/6 done | workplan_id: `81632950-7948-4a8f-b526-911683713e72`
**Open tasks:**
- · Task: fix-consistency registration for intake/decision/engagement kinds `00272ba0`
- · Task: Promotion transition — one call, both artefacts, both synced `43e04a5a`
- · Task: Generated per-repo work-record index (design + first cut) `985273dc`
- · Task: Regenerate binky-control queue view tails as [auto] `bc4f249f`
- · Task: Suggestion-table close-out `af5b6c2e`
## Inbox Hygiene
**Stale unread:** 1 message(s) older than 3 day(s) — triage at session start.
**Missing thread_id:** 1 unread message(s) lack supersession chains.
- ! state-hub: STATE-WP-0070 done — phase-3 handoff to CUST-WP-0055 `0efa13f0`
---
## 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.