From ae37a78e3134513f46d72f4e48d3e799002b10dc Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 6 Sep 2026 20:27:30 +0200 Subject: [PATCH] Bind Q2 production architecture to rapp-telemetry Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883 --- README.md | 9 +++++++++ docs/signal-contract.md | 11 +++++++++++ workplans/RTEL-WP-0002-signal-contract.md | 9 +++++++++ 3 files changed, 29 insertions(+) diff --git a/README.md b/README.md index d82ab37..e016c5d 100644 --- a/README.md +++ b/README.md @@ -33,3 +33,12 @@ workload packaging remains outside this repo. Run `python3 -m unittest discover -s tests -v` (Python 3.11+, no dependencies). Live acceptance is tracked by RTEL-WP-0002-T04; local receipts are not external operator delivery proof. + +## Managed production package + +[rapp-telemetry](../rapp-telemetry/README.md) packages Prometheus, Alertmanager +and Grafana for railiance01, with telemetry.coulomb.social as the intended +Grafana hostname. This repo retains Q2 contracts and rule meaning. The local +receiver and activity candidates are reference tooling; do not enable them as +a second production monitoring plane. Runtime deployment remains pending in +the package foundation workplan. diff --git a/docs/signal-contract.md b/docs/signal-contract.md index ead7a19..9024716 100644 --- a/docs/signal-contract.md +++ b/docs/signal-contract.md @@ -99,3 +99,14 @@ executor/profile, immutable bundle, upstream platform report command, state location and notification channel. No resolver, live schedule or second host cron has been introduced. Strict profile-enforcing environments need the accepted profile binding before registration; none is invented in these candidates. + +## Production architecture decision — 2026-09-06 + +The user directed Master-compliant package establishment on railiance01. +`rapp-telemetry` now owns the maintained kube-prometheus-stack release: +Prometheus, Alertmanager and Grafana. Grafana's intended hostname is +telemetry.coulomb.social. The local SQLite receiver/runtime remains a reference +implementation. Do not activate its candidate activity definitions as a parallel +production monitoring plane. Q2 now needs a reviewed Prometheus exporter/rule +mapping preserving the existing state semantics, and actual Alertmanager delivery +acceptance. Package runtime/admission is tracked by RAPP-TELEMETRY-WP-0001. diff --git a/workplans/RTEL-WP-0002-signal-contract.md b/workplans/RTEL-WP-0002-signal-contract.md index 9943dd1..24264dd 100644 --- a/workplans/RTEL-WP-0002-signal-contract.md +++ b/workplans/RTEL-WP-0002-signal-contract.md @@ -86,3 +86,12 @@ recurring-automations playbook. Native parser accepts both; 14 tests pass. Recipient/channel clarification is pending. Runtime/profile and failure-domain binding, off-host custody and actual notification acknowledgment remain unproven; T04 remains wait, with no live schedule enabled. + +Production package established September 6 at user direction: rapp-telemetry, +owned by this Q2 repo and declared against Master's normative schema. Selected +Prometheus/Alertmanager/Grafana via pinned kube-prometheus-stack; planned runtime +railiance01, Grafana telemetry.coulomb.social. RAPP-TELEMETRY-WP-0001-T03/T04 owns +package install, readiness and authenticated exposure. This T04 retains Q2's +exporter/rule mapping and actual delivery/absence acceptance. Existing SQLite +runtime and disabled activities are reference work, not the production service. +No package activation or Q2 delivery acceptance is claimed by repo creation.