repo-manager/.custodian-brief.md
custodian-sync c7fbd57800 chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-08-18:
  - update .custodian-brief.md for repo-manager
2026-08-18 12:18:12 +02:00

38 lines
1.4 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — repo-manager
**Domain:** infotech
**Last synced:** 2026-08-18 10:18 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Railiance managed-app wrapper setup
Progress: 1/5 done | workplan_id: `0d6d2ebf-4b74-4908-995c-17b8987ede05`
**Open tasks:**
- · Bootstrap the user-engine wrapper to `declared` `f0e53954`
- · Generate the Kubernetes package skeleton `3ba6828e`
- · Draft platform handoffs `0c2846d9`
- · Implement `rmgr rapp` scaffolding `6cf89776`
### Repository standards conformance and governed scaffolding
Progress: 0/9 done | workplan_id: `b8b3f1e0-b8df-4405-849e-11ec51f80ae5`
**Open tasks:**
- ! Implement conformance checking `2c9b0cb1`
- ! Own governed scaffolding `8e6fa8d7`
- ! Regenerate agent instructions per flavor `8cd3ba11`
- ! Accept the handoff from state-hub `8402b8b6`
- ! Add compatibility and regression tests `faaeb016`
- ! Confirm the canon boundary `7fdd54fe`
- ! Enforce workplan identifier uniqueness `fc7395b0`
- … and 2 more open tasks
---
## 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.