Files
activity-core/.custodian-brief.md
tegwick 987cf5a75c chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-05-14:
  - update .custodian-brief.md for activity-core
2026-05-14 23:51:06 +02:00

29 lines
1.2 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — activity-core
**Domain:** custodian
**Last synced:** 2026-05-14 21:51 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### activity-core WP-0004 — Railiance Deployment & Service Ops
Progress: 0/7 done | workstream_id: `759b1255-aa78-42b5-8fab-c5fcf168f5f4`
**Open tasks:**
- · [repo:activity-core] T58: Dockerfile (multi-stage, uv-based) `2a81f9ba`
- · [repo:activity-core] T59: docker-compose.railiance.yml (full stack, no Elasticsearch) `67981de4`
- · [repo:activity-core] T60: GET /health endpoint `7c7a1617`
- · [repo:activity-core] T61: .env.example — complete env var reference `2a2a8d02`
- · [repo:activity-core] T62: Makefile ops targets `55ac37b5`
- · [repo:activity-core] T63: SIGTERM graceful shutdown (worker + event_router) `65b3229b`
- · [repo:activity-core] T64: docs/runbook.md — railiance deployment section `83dcd765`
---
## 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.