audit-core/.custodian-brief.md
custodian-sync 0a3d05ff1c
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-08-15:
  - update .custodian-brief.md for audit-core
2026-08-15 20:46:52 +02:00

26 lines
1 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — audit-core
**Domain:** infotech
**Last synced:** 2026-08-15 18:46 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Honest operational custody against ITC-CAP and the live platform backup
Progress: 0/5 done | workplan_id: `8d775ffb-3c83-4c33-9ffa-05ce52c5ff91`
**Open tasks:**
- · T01 — Restate custody vocabulary in the running service `bbf476eb`
- · T02 — Bind the recovery promise to the live platform backup `06907b2c`
- · T03 — Publish an ITC-CAP case for the live provision `eba29df0`
- · T04 — Publish a Canon Interface Card `c5f5a883`
- · T05 — Persist sender tenant scope and refresh SCOPE `c629d894`
---
## 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.