Files
helix-forge/.custodian-brief.md
tegwick 51f7a084ee chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-05-16:
  - update .custodian-brief.md for helix-forge
2026-05-16 04:07:55 +02:00

1.5 KiB

Custodian Brief — helix-forge

Domain: helix_forge
Last synced: 2026-05-16 02:07 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: 3/10 done | workstream_id: 48d91935-197e-4ad4-be07-7bbcd535847c

Open tasks:

  • ! T02 — Register ops-hub in Inter-Hub 8e9bd9b2 (blocked: Requires authenticated Inter-Hub admin session or deployment-side migration execution.)
  • ! T03 — Activate the ops-hub capability manifest 55f5aeed (blocked: Requires ops-hub row and authenticated UI or migration execution.)
  • ! T04 — Create ops-hub API consumer and key ad08e729 (blocked: Requires authenticated operator API key creation.)
  • ! T05 — Seed first governed ops widgets d303884d (blocked: 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 (blocked: Requires ops widget, active ops event type, and API key before event submission.)
  • ► T10 — Inter-Hub API hardening for extension bootstrap 7fa54508
  • · T09 — Decide whether to create a separate ops-hub repository 0e5842fd

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.