activity-core/.custodian-brief.md
custodian-sync c123417b7e
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-18:
  - update .custodian-brief.md for activity-core
2026-08-18 10:29:04 +02:00

34 lines
1.2 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — activity-core
**Domain:** infotech
**Last synced:** 2026-08-18 08:29 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Daily bounded SBOM catch-up via sbom-nexus
Progress: 0/4 done | workplan_id: `bfe2945e-38df-40d1-94d4-6e4a003ef66d`
**Open tasks:**
- ! Implement ingest side-effect for N targets `0d09c0d3`
- ! Retire weekly task flood `18bcfc21`
- ! Prod enable and evidence `f09144f6`
- · Draft definition and resolver contract `b216976e`
### Hub port and schedule alignment for State Hub retirement
Progress: 0/4 done | workplan_id: `1b18849c-db3a-40a0-8f22-7af7fd4dbcfc`
**Open tasks:**
- ! Align ops evidence sink `3fbadbfe`
- · Map current State Hub / core-hub callers `03021be2`
- · Retarget consistency sweep `f8107e2b`
- · Execution queue boundary `a34b42c3`
---
## 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.