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.
10 commits 1 branch 0 tags 68 KiB
Find a file
codex c42cb88d31 chore(classification): add repo classification 
Sector domain and category decided with the repository owner on 2026-08-25.
Classification is not mechanical: the sector describes intended users, so a
confident wrong value is harder to correct than a missing one.

Refs CUST-WP-0067-T05

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-25 14:02:41 +02:00
workplans Adopt repo-owned workplan prefix per ADR-007 2026-08-17 10:48:59 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-15 20:55:19 +02:00
.gitignore Place telemetry on the Quality dimension as Q2 Observability 2026-08-11 22:54:30 +02:00
.repo-classification.yaml chore(classification): add repo classification 2026-08-25 14:02:41 +02:00
AGENTS.md docs(agents): repoint remote State Hub URL to the in-cluster address 2026-08-25 00:21:51 +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 chore(consistency): refresh WORK-RECORDS after bootstrap status change 2026-08-15 20:56:47 +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.