2026-08-11 19:44:48 +00:00
|
|
|
# railiance-telemetry
|
|
|
|
|
|
2026-08-11 21:51:42 +02:00
|
|
|
Observability for Railiance providing monitoring, metrics, alerting etc to
|
|
|
|
|
enable the self-organizing control loop.
|
|
|
|
|
|
|
|
|
|
**Status: seeded.** `INTENT.md` is written; there is no implementation yet. The
|
|
|
|
|
live cluster currently has no monitoring namespace — this is greenfield.
|
|
|
|
|
|
|
|
|
|
## Why this repo exists
|
|
|
|
|
|
|
|
|
|
Five Railiance layers independently declare that they intend to be
|
|
|
|
|
"self-evidencing" or "auditable" — infra, cluster, platform, apps, and forge.
|
|
|
|
|
None of them owned the place that evidence goes. This repo is that place.
|
|
|
|
|
|
|
|
|
|
It owns **the signal**, not **the meaning of the signal**: conformance rules and
|
|
|
|
|
consistency checks stay with the repos that own those concerns, and telemetry
|
|
|
|
|
carries and surfaces their output.
|
|
|
|
|
|
|
|
|
|
## Start here
|
|
|
|
|
|
|
|
|
|
1. [`INTENT.md`](INTENT.md) — why this exists and what it is becoming
|
|
|
|
|
2. [`SCOPE.md`](SCOPE.md) — in scope, out of scope, how it fits
|
|
|
|
|
3. [`AGENTS.md`](AGENTS.md) — session protocol
|
|
|
|
|
4. `workplans/`
|
|
|
|
|
|
|
|
|
|
## Open question
|
|
|
|
|
|
|
|
|
|
Stack-dimension placement (S3 platform capability, or a Quality-dimension
|
|
|
|
|
concern outside the stack) is **undecided** and belongs to `railiance-master`.
|
|
|
|
|
See `INTENT.md` → "Open Placement Question". It is called out explicitly so this
|
|
|
|
|
repo does not drift into the unplaced state `railiance-forge` ended up in.
|
