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

Prepare bounded telemetry runtime jobs and activity definitions

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 19:32:26 +02:00
parent cecef79f31
commit a32c0f1541
9 changed files with 329 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
history/2026-09-06-runtime-integration-preparation.md Normal file
View file

@ -0,0 +1,19 @@
# Runtime integration preparation — 2026-09-06
Continued RTEL-WP-0002-T04. Activity-core's recurring-automations playbook places
cadence in domain definitions and execution in an accepted claimant/domain
executor; no workstation cron or new scheduler is needed. Implemented a bounded
private runtime command, stable report retry IDs, watchdog receipts and a separate
read-only age probe, and SQLite-native verified snapshots. Snapshot restore tests
preserve pending operator notices and the contract binding.
Added two disabled activity definitions (five-minute ingest, two-minute emission
check), executor instructions, and explicit independent watcher requirements.
Activity-core's own parse_file accepted both. No strict-runtime profile, package
name, recipient acceptance or deployed claim executor was invented.
Validation: 14 tests passed; native activity parser accepted both disabled
candidates. No live schedule was registered, no notification sent and no runtime
or snapshot proof was promoted to off-host recovery. Requested operator/channel
selection before implementing the actual notification destination. T04 remains
waiting for that selection and accepted execution/storage/independence bindings.