- Align agent files with on-disk workplan prefixes (infer from workplan ids) - Set workplan domain to registered domain_slug; add topic_slug where applicable - Repair frontmatter delimiter formatting; migrate legacy task status literals - Regenerate AGENTS.md, CLAUDE.md, and .claude/rules from State Hub templates
5.0 KiB
id, type, title, domain, repo, status, owner, topic_slug, created, updated
| id | type | title | domain | repo | status | owner | topic_slug | created | updated |
|---|---|---|---|---|---|---|---|---|---|
| OPS-WP-0002 | workplan | Bootstrap ops-hub as an Inter-Hub Operations extension | infotech | ops-hub | active | codex | inter_hub | 2026-06-06 | 2026-06-06 |
Bootstrap ops-hub as an Inter-Hub Operations extension
Goal
Turn the HelixForge HF-WP-0001 handoff into the first concrete ops-hub
implementation track.
ops-hub should become the Operations / System 1 Inter-Hub extension for
operational truth: environments, hosts, clusters, services, endpoints,
releases, backups, incidents, risks, runbooks, readiness gates, and migration
waves.
This repo owns domain-specific implementation assets. inter-hub remains the
generic framework, registry, authentication, manifest, widget, event, and
bootstrap API substrate.
Current Gate
As of 2026-06-06, public production Inter-Hub still returns 404 for:
https://hub.coulomb.social/api/v2/hubs
Do not run manual database seeding unless the operator explicitly chooses that fallback. The preferred bootstrap path is the supported Inter-Hub API once production exposes the current bootstrap surface.
Gate criteria:
- Unauthenticated
GET /api/v2/hubsreturns401, not404. - OpenAPI lists
/hubs,/hub-capability-manifests,/api-consumers, and/policy-scopes. - The bootstrap/smoke client can create or reuse the
ops-hubhub, activate its manifest, create the runtime API consumer/key, seed initial widgets, and persist the first governed ops event.
Handoff Sources
/home/worsch/helix-forge/workplans/HF-WP-0001-establish-ops-hub-first-extension.md/home/worsch/helix-forge/wiki/OpsHubInventory.md/home/worsch/helix-forge/wiki/OpsHubReadinessGates.md/home/worsch/helix-forge/wiki/OpsHubBootstrapRunbook.md/home/worsch/helix-forge/wiki/ops-hub-manifest.draft.json/home/worsch/helix-forge/wiki/ops-hub-widgets.seed.json
Port HelixForge Handoff Artifacts
id: OPS-WP-0002-T01
status: done
priority: high
Create repo-local docs and seed data for the ops vocabulary, initial inventory, readiness gates, bootstrap runbook, manifest draft, and widget seed.
Done when the ops-hub repo can be understood without opening HelixForge for
routine implementation details. Keep links back to HelixForge for architectural
context.
Completed 2026-06-06:
- Ported initial inventory to
docs/initial-inventory.md. - Ported readiness gates to
docs/readiness-gates.md. - Ported bootstrap runbook to
docs/bootstrap-runbook.md. - Ported manifest and widget seeds to
seeds/. - Added
docs/README.mdas the handoff index.
Define Repository Source Layout
id: OPS-WP-0002-T02
status: done
priority: high
Choose and create the first source layout for bootstrap/smoke tooling,
collectors, adapters, and tests. Add the repo-native lint, test, build, and run
commands to AGENTS.md.
Done when future code changes have an obvious home and a verification command.
Completed 2026-06-06:
- Added
pyproject.toml. - Added Python package layout under
src/ops_hub/. - Added operator scripts under
scripts/. - Added tests under
tests/. - Documented current verification commands in
AGENTS.md.
Implement Inter-Hub Production Gate Probe
id: OPS-WP-0002-T03
status: done
priority: high
Build a small probe that checks the public Inter-Hub bootstrap API gate:
/api/v2/hubsresponse is401unauthenticated.- OpenAPI lists the required bootstrap paths.
- The result is machine-readable and suitable for a scheduled ops signal later.
Done when the probe can run locally without secrets and reports the current gate as pass/fail with clear reasons.
Completed 2026-06-06: scripts/interhub-gate-probe.py checks unauthenticated
/api/v2/hubs status and required OpenAPI bootstrap paths, emits JSON, and
exits nonzero while the gate is closed.
Implement Bootstrap Smoke Client
id: OPS-WP-0002-T04
status: wait
priority: high
Implement the authenticated bootstrap/smoke client once Inter-Hub production exposes the supported bootstrap API.
The client should use IHUB_BASE and IHUB_OPERATOR_KEY and should create or
reuse:
ops-hubhub row- active capability manifest
- runtime API consumer/key
- initial governed ops widgets
- first
ops-endpoint-verifiedevent
Done when a dry-run and an attended real run both produce repeatable evidence without direct DB access.
Waiting on: Inter-Hub production API gate from T03.
Seed First Operational Signal
id: OPS-WP-0002-T05
status: wait
priority: medium
Submit the first governed ops signal for the Gitea registry endpoint once the manifest, widget, event type, and API key exist.
Initial signal:
{
"eventType": "ops-endpoint-verified",
"endpoint": "https://gitea.coulomb.social/v2/",
"expectedStatus": 401,
"viewContext": "railiance-apps/workplans/RAIL-AP-WP-0001"
}
Done when the event is visible in Inter-Hub and traceable to the owning Railiance workplan.
Waiting on: T04 and an available ops-hub runtime API key.