Files
issue-core/.custodian-brief.md
tegwick bed83be0ec chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-06-19:
  - update .custodian-brief.md for issue-core
2026-06-19 21:07:30 +02:00

1.1 KiB

Custodian Brief — issue-core

Domain: custodian
Last synced: 2026-06-19 19:07 UTC
State Hub: http://127.0.0.1:8000 (adjust if running on a remote machine)

Active Workstreams

Deploy issue-core as a service on railiance01 (ArgoCD GitOps pilot)

Progress: 0/7 done | workstream_id: 896ace77-21b3-450b-8fb7-254aefc8c570

Open tasks:

  • ! ArgoCD bootstrap (railiance-platform dependency) + issue-core Application 9b199b1d
  • ► Container image published to a pullable registry 3723e896
  • ► Kubernetes manifests (namespace, Deployment, Service) in GitOps source 38887dd6
  • ► In-cluster backend config (cluster Gitea / markitect) 10923f1e
  • · OpenBao secret: ISSUE_CORE_API_KEY ad52527f
  • · Wire activity-core to the live service 96b14cdb
  • · End-to-end verification + GitOps runbook 8d853b8e

MCP Orientation (when available)

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