Files
helix-forge/.custodian-brief.md
tegwick bd3deec4d6 chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-06-14:
  - update .custodian-brief.md for helix-forge
2026-06-14 19:49:46 +02:00

33 lines
1.5 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — helix-forge
**Domain:** helix_forge
**Last synced:** 2026-06-14 17:49 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Establish ops-hub as the First VSM Inter-Hub Extension
Progress: 4/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.)*
- ! T10 — Inter-Hub API hardening for extension bootstrap `7fa54508`
---
## 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.