Files
activity-core/.custodian-brief.md
tegwick 1a279e9f22 chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-06-17:
  - update .custodian-brief.md for activity-core
2026-06-17 23:59:37 +02:00

36 lines
1.1 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — activity-core
**Domain:** custodian
**Last synced:** 2026-06-17 21:59 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Post-triage operational hardening
Progress: 5/6 done | workstream_id: `5646e13a-13af-4724-bca6-3c0d86f96733`
**Open tasks:**
- ! Three-Run Calibration Feedback `7cbf0a35`
### Intent gap closure
Progress: 4/6 done | workstream_id: `d64cfbba-6da7-4737-afb9-866afa0e9cda`
**Open tasks:**
- ! Close Daily Triage Scheduled-Run Trust Gap `7012e4fd`
- ! Promote Issue-Core Task Emission Safely `3854677b`
### Weekly Coding Retrospection schedule (Saturday evenings)
Progress: 2/3 done | workstream_id: `7387fc50-1f2c-471a-9d85-bb085cbd0b63`
**Open tasks:**
- ! Dry-run verify + enable + docs `9dcbebe7`
---
## MCP Orientation (when available)
If the state-hub MCP server is reachable, call:
`get_domain_summary("custodian")`
This provides richer cross-domain context.
If the MCP call fails, use this file as your orientation source.