railiance-telemetry/history/2026-09-28-loose-end-review.md
tegwick b6d0f78f93 Complete local Prometheus mapping and record live acceptance blockers
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e6f1-443f-7783-9920-a16b2ffc467f
2026-09-28 09:42:04 +02:00

38 lines
2.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Loose-end review — 2026-09-28
Reviewed both repository workplans: RTELE-WP-0001 is finished with all three
tasks done; RTEL-WP-0002 has T01–T03 done and T04 waiting. No proposed, ready or
other unfinished workplans exist in this checkout. No whole task can honestly
close without live acceptance, but T04's exporter/rule implementation is now done.
Added a strict stdout Prometheus exporter, a dated 24-signal contract including
`eso.token-renewal`, failure/absence rules, and native rule fixtures. Preserved
the original contract for existing SQLite bindings and producer evaluation time
for absence detection. Updated the README's stale package-deployment claim.
Validation:
- `python3 -m unittest discover -s tests -v`: 19 passed.
- Prometheus 3.5.0 `promtool check rules rules/platform-assurance.json`: two valid rules.
- `promtool test rules tests/prometheus-rules.json`: seven scenarios passed
(never seen, fresh, exact budget, stopped producer, future clock, disappeared
scrape and failed token renewal).
- `promtool check metrics`: passed on exported platform September 27 evidence.
That compatibility check used the original evaluation time, not a claim that
yesterday's evidence is fresh today.
Reviewed platform source at `c3607ff`, including
`docs/evidence/2026-09-27-service-assurance.json` and the source contract, and
rapp-telemetry records at `6d2e9fe`. The package records private install/restore
as complete. Its T04 retains delivery, outside-node watchdog and recurring
backup admission. No live infrastructure was modified or notification sent.
The September 23 platform inbox request is acknowledged as read. Its existing
RPF-WP-0046-T06 retains exact failed-Job/48-hour delivery acceptance; the current
S3 renewal signal uses 36 hours and must not be silently redefined here.
RTEL-WP-0002 is now blocked; T04 remains wait for accepted package transport,
confirmed recipient/channel, actual acknowledged failure/absence, independent
watchdog and recurring backup ownership. Bernd Worsch supplies recipient and
admission decisions; rapp-telemetry/platform retain runtime/custody integration.
No tasks or workplans were created, and no unfinished workplan was closed.