From 95a862bd5d0d4227624510a73b36e80dcd2d9dca Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 19 Oct 2026 11:28:44 +0200 Subject: [PATCH] docs: clarify signal mapping and runtime ownership Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181 --- SCOPE.md | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/SCOPE.md b/SCOPE.md index a8c1f11..d32ae52 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -16,8 +16,8 @@ Observability for Railiance — monitoring, metrics, logs, traces, and alerting Five Railiance layers independently declare that they intend to be "self-evidencing" or "auditable". None of them owned the place that evidence -goes, and the live cluster has no monitoring namespace at all. This repo fills -that gap: it is the evidence plane the rest of the stack emits into. +goes. This repo owns the signal contract; `rapp-telemetry` owns the privately +deployed monitoring package the stack consumes. The distinction that keeps this repo honest: it owns **the signal**, not **the meaning of the signal**. Conformance rules and consistency checks belong @@ -70,8 +70,9 @@ output. - Status: **private reference implementation** — contract, durable local inbox, platform adapter and missing-emission checks implemented September 6 -- No deployed monitoring runtime or external delivery acceptance established; - live work is tracked in RTEL-WP-0002-T04 +- The monitoring package is privately deployed under `rapp-telemetry`. + Integration and external delivery acceptance for this repo's signal contract + remain tracked in RTEL-WP-0002-T04. - Placement: **Quality dimension, Q2 Observability** — canon defines Q2 as "telemetry and monitoring: metrics, logs, traces". Ratification sits with `railiance-master`; the question is answered, not open @@ -104,3 +105,13 @@ output. - Then: `SCOPE.md`, `AGENTS.md`, `workplans/` - Context: `railiance-platform/history/2026-08-11-railiance-architecture-in-aspiration.md` records the assessment that identified this gap + + +## Provided Capabilities + +```capability +type: operations +title: Private assurance signal contract and Prometheus mapping +description: Validate bounded producer-owned assurance states and observation times, with a local SQLite reference receiver and scripts/prometheus_export.py plus rules/platform-assurance.json for the selected Prometheus package. See docs/prometheus-mapping.md. Package transport, rule loading and acknowledged external delivery are not established by local exporter tests; do not deploy the SQLite reference as a parallel monitoring plane. +keywords: [telemetry, assurance, prometheus, signal, freshness, alerting, contract] +```