Prepare bounded telemetry runtime jobs and activity definitions
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
parent
cecef79f31
commit
a32c0f1541
9 changed files with 329 additions and 0 deletions
16
tasks/telemetry-platform-ingest.md
Normal file
16
tasks/telemetry-platform-ingest.md
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
# Receive one platform assurance report
|
||||
|
||||
Prerequisites: RTEL-WP-0002-T04 accepted private executor, immutable source
|
||||
revision, state directory and upstream platform capture/evaluate command. Do
|
||||
not infer these from the candidate definition or launch a coding agent per tick.
|
||||
|
||||
The platform owner supplies a fresh metadata-only evaluator report. In the
|
||||
approved executor run `python3 scripts/runtime.py --contract
|
||||
contracts/platform-assurance.json --state-dir <approved-private-directory>
|
||||
ingest-report <fresh-report-path>` from the pinned telemetry bundle.
|
||||
|
||||
Record the bounded result on the claimed activity-core ops run and complete or
|
||||
fail it. Preserve the identical report for transport retries; runtime derives
|
||||
a stable event ID. Never replace its timestamp with execution time or treat
|
||||
missing upstream output as healthy. No arbitrary shell arguments or recipient
|
||||
addresses are supplied through event data. This job sends no notification.
|
||||
14
tasks/telemetry-platform-watchdog.md
Normal file
14
tasks/telemetry-platform-watchdog.md
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
# Check producer absence independently of ingestion
|
||||
|
||||
Prerequisites: RTEL-WP-0002-T04 accepted private executor and persistent state.
|
||||
Run `python3 scripts/runtime.py --contract contracts/platform-assurance.json
|
||||
--state-dir <approved-private-directory> check` from the pinned telemetry bundle.
|
||||
This records missing emission in the local inbox even if no event was received.
|
||||
Record the result on the claimed activity-core ops run. Do not acknowledge
|
||||
notices automatically. Dispatch to the actual operator only through the accepted
|
||||
notification adapter after recipient/channel authorization.
|
||||
|
||||
A separate failure domain must invoke the read-only `health` command and route
|
||||
stale/missing/unreachable receiver results. That watcher cannot depend solely on
|
||||
this same scheduler, host or receiver database. Its deployment and delivery proof
|
||||
are still T04 acceptance gates. No second workstation cadence is installed.
|
||||
Loading…
Add table
Add a link
Reference in a new issue