activity-core/.custodian-brief.md
custodian-sync 5de95c1b3d
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-08-03:
  - update .custodian-brief.md for activity-core
2026-08-03 19:26:22 +02:00

28 lines
1,005 B
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — activity-core
**Domain:** infotech
**Last synced:** 2026-08-03 17:26 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Ops run claim queue — durable claimable work for scheduled automation
Progress: 6/7 done | workplan_id: `c8f1eaa3-6d1a-4002-bb1f-fc250ed353fe`
**Open tasks:**
- · T07 — Railiance rollout + dual-path flag `b1ce221b`
## Inbox Hygiene
**Stale unread:** 2 message(s) older than 3 day(s) — triage at session start.
**Missing thread_id:** 2 unread message(s) lack supersession chains.
- ! net-kingdom: NK-IN-0001/0002 promoted → NK-WP-0021 (ops SSO least-privilege) `0bf03792`
---
## 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.