audit-core/.custodian-brief.md
custodian-sync 0f331151df
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 0s
chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-08-16:
  - update .custodian-brief.md for audit-core
2026-08-16 00:58:32 +02:00

26 lines
951 B
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — audit-core
**Domain:** infotech
**Last synced:** 2026-08-15 22:58 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Integrity verification for operational custody
Progress: 0/5 done | workplan_id: `97946512-eb0a-4282-8c1f-f53d9ee25bfa`
**Open tasks:**
- · T01 — Specify the chain and the proof bound `d4423fd5`
- · T02 — Persist the chain on accept `5830bb1a`
- · T03 — Verify surface `fee1f93c`
- · T04 — Attest the chain head outside platform-pg `b6d03d6a`
- · T05 — Declare tamper_evidence only as far as the proof `9fd70d3c`
---
## 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.