coulomb/railiance-telemetry
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Observability for railiance providing monitoring, metrics, alerting etc to enable the selforganizing control loop.
4 commits 1 branch 0 tags 111 KiB
Find a file
tegwick 53165d2a50 Place telemetry on the Quality dimension as Q2 Observability 
The placement question seeded as open is answered by canon rather than by a
new decision. OAS section 8 defines Q2 Observability as 'telemetry and
monitoring: metrics, logs, traces' - this repo in canon's own words.

The 2026-08-11 coherence review found Railiance had been modelling itself on
one of OAS's six required dimensions and treating everything else as unplaced.
Observability was never homeless; the dimension it belongs to was not in use.
Notes Q7 Governance as the sibling concern - the conformance loop, the other
half of the self-evidencing aspiration this repo serves.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-11 22:54:30 +02:00
workplans Place telemetry on the Quality dimension as Q2 Observability 2026-08-11 22:54:30 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-11 21:52:34 +02:00
.gitignore Place telemetry on the Quality dimension as Q2 Observability 2026-08-11 22:54:30 +02:00
AGENTS.md Place telemetry on the Quality dimension as Q2 Observability 2026-08-11 22:54:30 +02:00
INTENT.md Place telemetry on the Quality dimension as Q2 Observability 2026-08-11 22:54:30 +02:00
LICENSE Seed INTENT, SCOPE, README for the observability layer 2026-08-11 21:51:42 +02:00
README.md Seed INTENT, SCOPE, README for the observability layer 2026-08-11 21:51:42 +02:00
SCOPE.md Place telemetry on the Quality dimension as Q2 Observability 2026-08-11 22:54:30 +02:00
WORK-RECORDS.md Place telemetry on the Quality dimension as Q2 Observability 2026-08-11 22:54:30 +02:00

README.md

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

  1. INTENT.md — why this exists and what it is becoming
  2. SCOPE.md — in scope, out of scope, how it fits
  3. 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.