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>
This commit is contained in:
parent
ee90f31d5c
commit
53165d2a50
6 changed files with 297 additions and 12 deletions
5
.gitignore
vendored
Normal file
5
.gitignore
vendored
Normal file
|
|
@ -0,0 +1,5 @@
|
|||
# state-hub: track .claude/rules
|
||||
# Claude Code local state (track shared rules; ignore machine-specific files)
|
||||
.claude/*
|
||||
!.claude/rules/
|
||||
!.claude/rules/*.md
|
||||
Loading…
Add table
Add a link
Reference in a new issue