audit-core/.custodian-brief.md
custodian-sync 4392d51333
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Has been cancelled
chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-08-29:
  - update .custodian-brief.md for audit-core

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4040362@bnt-lap001
Assistant-Session: 4fd0fd24-2ee8-4413-bd67-43bd79ca73f1
2026-08-29 14:47:54 +02:00

35 lines
1 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — audit-core
**Domain:** infotech
**Last synced:** 2026-08-29 12:47 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Evidence-role conformance under Security Layer Model v0.7
Progress: 0/10 done | workplan_id: `46a96b03-bc08-53b5-9c93-4071adabf734`
**Open tasks:**
- ! Tasks `382575ca`
- · Tasks `f545b0e4`
- · Tasks `6de9945f`
- · Tasks `acae6085`
- · Tasks `f36470af`
- · Tasks `0a8d6eed`
- · Tasks `f572dfeb`
- … and 3 more open tasks
### Tenancy posture declaration and read-path enforcement
Progress: 7/8 done | workplan_id: `a9a248b2-d26c-503e-a8fc-4f3675e6ed51`
**Open tasks:**
- ► Tasks `4e3ab790`
---
## 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.