issue-core/.custodian-brief.md
custodian-sync c2023211b5
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 issue-core
2026-07-21 00:09:17 +02:00

26 lines
1 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — issue-core
**Domain:** infotech
**Last synced:** 2026-07-20 22:09 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Align issue-core with the work-record canon (connector, not landing zone)
Progress: 0/5 done | workplan_id: `ee47385f-aadb-4dba-b39f-148ac1444c3d`
**Open tasks:**
- · Task: Rewrite INTENT.md — connector, not landing zone `ae1e2a1e`
- · Task: Rewrite SCOPE.md — mapping table, not ingestion primary path `cd0422f6`
- · Task: Audit and update README / ROADMAP for the same framing `746d090d`
- · Task: Design the UUID ↔ external-id mapping surface (design only) `61ba9b84`
- · Task: Fix activity-core's IssueSink call site to match `944e0510`
---
## 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.