67283b66c2
Updated by fix-consistency on 2026-09-28: - update .custodian-brief.md for railiance-telemetry Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e6f1-443f-7783-9920-a16b2ffc467f |
||
|---|---|---|
| activity-definitions | ||
| contracts | ||
| docs | ||
| history | ||
| rules | ||
| scripts | ||
| tasks | ||
| tests | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| INTENT.md | ||
| LICENSE | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
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.
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
INTENT.md— why this exists and what it is becomingSCOPE.md— in scope, out of scope, how it fitsAGENTS.md— session protocolworkplans/
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 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. The package records private installation and restore proof; delivery acceptance remains blocked in RTEL-WP-0002-T04. The Prometheus mapping supplies a tested report exporter and failure/absence rules for package integration.