Catalog system
Kuya Army control plane
product · product · Go
Kuya Army control plane for internal runtimes, dispatch, and dataset tools. Resources (servers, Redis, queues) hang off this tree. It is operator infrastructure, not a customer site.
- Version
- —
- Latency
- Not probed
- Last check
- Last deploy
- None
Health
Uptime
Not probed
Readiness
Checklist
- URL Not configured missing
- SSL No public URL missing
- Health Not configured missing
- Docs Not configured missing
- E2E Not configured missing
- Deploy Not configured missing
Knowledge
Documentation
No public documentation URL is configured.
Releases
Deploy history
No deployments recorded.
Tree
Subsystems
Internal GitHub runner dashboard. Health URLs stay operator-only. The public board may list the name; it never lists the probe address.
- app
- service
Internal dispatcher for Kuya Army tasks. Nested under the control plane. Operators expand Kuya Army to see this service.
- service
- service
Go task runtime on kuya-army-1. It depends on Redis and AMQP resources of the control plane. There is no public HTTP product here.
- service
- service
- amqp
Internal agent runtime for Kuya Army. Operator health only. Nested under the control plane with the other runtimes.
- service
- service
Orchestrator dashboard for Kuya Army. Internal TypeScript app. Tracker lists it so the control-plane tree is complete.
- app
- service
Writing Assist API, localhost on kuya-army-1 and proxied through orchestrator. Internal Python service. It is not a public mill on this board.
- service
- service
Dataset Builder intake on kuya-army-1. Internal Go service. Nested under the control plane beside the catalog mill.
- service
- service
Dataset Builder catalog on kuya-army-1. Internal Go service. Operators find it under Kuya Army, not as a public product.
- service
- service
AMQP runner proxy on kuya-army-1. No HTTP surface. It exists so runner jobs reach the right host.
- service
- service
- amqp