Fills the gap identified in the 2026-08-11 Railiance architecture assessment: five layers declare they intend to be self-evidencing or auditable, and nothing owned the place that evidence goes. The live cluster has no monitoring namespace at all. Positions telemetry as the evidence plane - it owns the signal, not the meaning of the signal, so conformance rules stay with the repos that own them. Flags stack-dimension placement as an open question for railiance-master rather than asserting a level, so this repo does not repeat railiance-forge's unplaced state. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.3 KiB
railiance-telemetry
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
INTENT.md— why this exists and what it is becomingSCOPE.md— in scope, out of scope, how it fitsAGENTS.md— session protocolworkplans/
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.