ops-warden/.custodian-brief.md
custodian-sync 7a08171dab
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-07-18:
  - update .custodian-brief.md for ops-warden
2026-07-18 14:26:51 +02:00

33 lines
1.3 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — ops-warden
**Domain:** infotech
**Last synced:** 2026-07-18 12:26 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Policy front door: posture-aware access planning + founder interaction surface
Progress: 0/5 done | workplan_id: `6e396e7e-99c5-43aa-98a0-27f157de12a3`
**Open tasks:**
- · T01 — `warden plan` decision front door `32e4a755`
- · T02 — Declared organization posture (build phase) `73ae528c`
- · T03 — Founder interaction surface (local web approval page) `2ea768b7`
- · T04 — Retire file-drop patterns from playbooks `61d25118`
- · T05 — Catalog freshness + agent guidance `2121d102`
## Inbox Hygiene
**Stale unread:** 11 message(s) older than 3 day(s) — triage at session start.
**Missing thread_id:** 9 unread message(s) lack supersession chains.
- ! the-custodian: ACTION: railiance01 state-hub deploy for workstream caller migration `467153f3`
- ! secrets-engine: Re: Need the warden-sign live apply/handoff (FLEX-WP-0007 T4) `80456912`
---
## 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.