coulomb/railiance-telemetry
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Place telemetry on the Quality dimension as Q2 Observability

Browse source 
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>
This commit is contained in:
tegwick 2026-08-11 22:54:30 +02:00
parent ee90f31d5c
commit 53165d2a50
6 changed files with 297 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

27
INTENT.md
View file

@ -125,19 +125,26 @@ of it:
---
## Open Placement Question
## Placement: Quality dimension, Q2 Observability
Railiance's stack dimension defines five levels (S1–S5). Observability is
cross-cutting: it draws signal from every level and is consumed by all of them.
This repo is **not** a stack level and not an exception to the stack model. It
is a concern on the **Quality dimension**, sub-level **Q2 Observability**, whose
canon definition (`canon/standards/orthogonal-architecture_v1.0.md` §8) is:
Whether this repo is best modelled as an S3 platform capability (it runs
stateful services and is consumed by others), or as a concern on the Quality
dimension rather than the Stack dimension, is **not settled here**. It is a
decision for `railiance-master`, which owns the taxonomy.
> *Telemetry and monitoring. Examples: metrics, logs, traces.*
This is stated explicitly because leaving placement undeclared is exactly how
`railiance-forge` ended up outside the stack model without anyone deciding it
should be.
That is this repo, in canon's own words.
The question was originally raised as open — S3 platform capability, or Quality
concern? — and answered by the 2026-08-11 coherence review, which found that
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 simply not in use.
Ratification sits with `railiance-master`, which owns the taxonomy. Related:
the conformance loop is **Q7 Governance and Change Management** — a sibling
concern on the same dimension, and the other half of the self-evidencing
aspiration this repo exists to serve.
---