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

Bind Q2 production architecture to rapp-telemetry

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
tegwick 2026-09-06 20:27:30 +02:00
parent a32c0f1541
commit ae37a78e31
3 changed files with 29 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
workplans/RTEL-WP-0002-signal-contract.md
View file

@ -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.