Implement private Q2 signal contract and durable reference receiver

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883

workplans/RTEL-WP-0002-signal-contract.md

@@ -0,0 +1,79 @@
+---
+id: RTEL-WP-0002
+type: workplan
+title: "Provide the Q2 receiving contract and prove signal delivery"
+domain: financials
+repo: railiance-telemetry
+status: active
+owner: codex
+created: "2026-09-06"
+updated: "2026-09-06"
+related:
+  - RTELE-WP-0001
+  - RPF-WP-0036
+state_hub_workstream_id: "08a5db92-7293-50d3-b589-55287b9850b3"
+---
+
+Bounded initial Q2 reference implementation for platform assurance. Producer
+meaning stays in S3; deployable monitoring packaging stays with a selected
+package owner. No public listener, credential custody or incident workflow.
+
+## Define metadata-only receiving and retention contract
+
+```task
+id: RTEL-WP-0002-T01
+status: done
+priority: high
+state_hub_task_id: "ac73553d-5bd4-5dff-8307-95a29bffe474"
+```
+
+Implemented `docs/signal-contract.md` and a pinned platform stream contract.
+Exact identities/signals, finite states, payload limit, freshness, replay,
+proposed retention and local recipient semantics are explicit. Live acceptance
+of the proposed budgets and recipient remains T04, not implied by this schema.
+
+## Implement durable receipt and operator inbox reference
+
+```task
+id: RTEL-WP-0002-T02
+status: done
+priority: high
+state_hub_task_id: "dacc9e2d-9321-5d39-afc4-88326f5c6930"
+```
+
+SQLite acceptance and notices commit together; strict rejection, duplicate
+idempotence, explicit acknowledgments and bounded retention are tested. This
+is a local private CLI implementation; acceptance says local-inbox-only.
+
+## Prove platform adaptation and absent-emission semantics locally
+
+```task
+id: RTEL-WP-0002-T03
+status: done
+priority: high
+state_hub_task_id: "a8ed3588-4240-5278-b03f-04c3237a52f9"
+```
+
+Adapter preserves producer evaluation time and classifications. Tests prove
+failure survives receiver restart, inbox addressing/acknowledgment, never-seen
+and stopped-producer detection, replay refusal, wrong-scope rejection and
+retention of unacknowledged evidence. Local simulated-time tests establish
+implementation behavior, not actual scheduled notification delivery.
+
+## Accept private runtime and controlled end-to-end delivery
+
+```task
+id: RTEL-WP-0002-T04
+status: wait
+priority: high
+state_hub_task_id: "ceb14fdc-b3fd-5a22-870d-d835a9d52055"
+```
+
+Choose package/runtime execution owner with cluster/activity-core; confirm the
+operator recipient, producer/watchdog cadence, retention/storage/backup and
+private authenticated access. Install only through accepted authority. Prove a
+controlled failure and stopped producer reach and are acknowledged by the named
+operator, and receiver/scheduler failure is independently detectable. Preserve
+receipts across restart; demonstrate capacity/retention handling. Only these
+receipts can satisfy RPF-WP-0036-T04. No package repo name or deployment grant is
+invented here. This live task holds the residual explicitly.

workplans/RTELE-WP-0001-statehub-bootstrap.md

@@ -4,11 +4,11 @@ type: workplan
 title: "Bootstrap State Hub integration"
 domain: financials
 repo: railiance-telemetry
-status: proposed
+status: finished
 owner: codex
 topic_slug: railiance
 created: "2026-08-11"
-updated: "2026-08-15"
+updated: "2026-09-06"
 related:
   - ADR-0008
   - RMASTER-WP-0023
@@ -25,14 +25,14 @@ seed the first *signal-contract* workplan. Do not deploy a monitoring
 stack here. Placement is Quality / Q2 (INTENT/SCOPE). That is not an
 open `railiance-master` question.
 
-This id uses the historical `RAILIANCE-WP-` prefix. New telemetry
+This id uses the historical `RTELE-WP-` prefix. New telemetry
 workplans use `RTEL-WP-`. Do not change this file's `id` or hub UUID.
 
 ## Review Generated Integration Files
 
 ```task
 id: RTELE-WP-0001-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "4aca4677-6712-553b-ac26-0682fdf211de"
 ```
@@ -46,7 +46,7 @@ open S3-vs-Quality question). Set the *next* workplan prefix to
 
 ```task
 id: RTELE-WP-0001-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "b6632ce1-dc84-532d-b277-adce8510a304"
 ```
@@ -59,7 +59,7 @@ the first verification command.
 
 ```task
 id: RTELE-WP-0001-T03
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "4877f6e2-8298-5bab-b6a8-9a1ec1718289"
 ```
@@ -78,3 +78,7 @@ checkout:
 ```bash
 statehub fix-consistency
 ```
+
+Completed September 6: reviewed integration and Q2 boundary, corrected README,
+documented the standard-library test workflow and seeded RTEL-WP-0002. Live
+runtime/notification acceptance remains explicitly in RTEL-WP-0002-T04.