<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — helix-forge

**Domain:** helix_forge  
**Last synced:** 2026-06-14 22:28 UTC  
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*

## Active Workstreams

### Expose OpenBao Browser UI at bao.coulomb.social
Progress: 0/6 done  |  workstream_id: `c1b5f54d-2f26-453d-966c-6353df0b6aec`

**Open tasks:**
- · T01 - Decide Browser UI Exposure Boundary  `6f516f34`
- · T02 - Expose OpenBao UI at bao.coulomb.social  `41e52213`
- · T03 - Add KeyCape UI Redirect URI  `fc1d5850`
- · T04 - Add OpenBao UI Redirect URI To platform-admin Role  `4f69cacb`
- · T05 - Verify Browser Login And Metadata-Only Secret Inspection  `31d1da2d`
- · T06 - Update Operator Runbooks  `f25bec03`

### Establish ops-hub as the First VSM Inter-Hub Extension
Progress: 5/10 done  |  workstream_id: `48d91935-197e-4ad4-be07-7bbcd535847c`

**Open tasks:**
- ! T02 — Register ops-hub in Inter-Hub  `8e9bd9b2`
  *(wait: Requires authenticated Inter-Hub admin session or deployment-side migration execution.)*
- ! T03 — Activate the ops-hub capability manifest  `55f5aeed`
  *(wait: Requires ops-hub row and authenticated UI or migration execution.)*
- ! T04 — Create ops-hub API consumer and key  `ad08e729`
  *(wait: Requires authenticated operator API key creation.)*
- ! T05 — Seed first governed ops widgets  `d303884d`
  *(wait: Requires ops-hub row and active manifest before widgets can be seeded.)*
- ! T07 — Instrument the current Gitea registry work as the first ops-hub signal  `ed3e0396`
  *(wait: Requires ops widget, active ops event type, and API key before event submission.)*

---
## MCP Orientation (when available)

If the state-hub MCP server is reachable, call:
`get_domain_summary("helix_forge")`
This provides richer cross-domain context.
If the MCP call fails, use this file as your orientation source.