railiance-telemetry/README.md
tegwick ae37a78e31 Bind Q2 production architecture to rapp-telemetry
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
2026-09-06 20:27:30 +02:00

44 lines
1.8 KiB
Markdown

# railiance-telemetry
Observability for Railiance providing monitoring, metrics, alerting etc to
enable the self-organizing control loop.
**Status: private reference implementation.** A versioned signal contract,
SQLite receipt/inbox CLI and platform adapter are implemented and tested.
No monitoring runtime or notification schedule is installed by this work.
See [the contract and workflow](docs/signal-contract.md).
## 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/`
## Placement and verification
Quality dimension, Q2 Observability, as recorded in INTENT/SCOPE. Monitoring
workload packaging remains outside this repo.
Run `python3 -m unittest discover -s tests -v` (Python 3.11+, no dependencies).
Live acceptance is tracked by RTEL-WP-0002-T04; local receipts are not external
operator delivery proof.
## Managed production package
[rapp-telemetry](../rapp-telemetry/README.md) packages Prometheus, Alertmanager
and Grafana for railiance01, with telemetry.coulomb.social as the intended
Grafana hostname. This repo retains Q2 contracts and rule meaning. The local
receiver and activity candidates are reference tooling; do not enable them as
a second production monitoring plane. Runtime deployment remains pending in
the package foundation workplan.