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

Adopt repo-owned workplan prefix per ADR-007

Browse source 
Retires the shared prefix. Live plans move to the new prefix keeping their
running number; finished and archived files keep the old prefix as
historical record, per the ADR-007 option 2 migration ruling.

Hub UUIDs are unchanged, so reconciliation matches on
state_hub_workstream_id rather than filename and will update the slug in
place instead of registering duplicates.

Assigned in RMGR-WP-0004-T09.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-17 10:48:59 +02:00
parent 7f9cc564b7
commit 773f4822c3
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

80
workplans/RAILIANCE-WP-0001-statehub-bootstrap.md
View file

@ -1,80 +0,0 @@
---
id: RAILIANCE-WP-0001
type: workplan
title: "Bootstrap State Hub integration"
domain: financials
repo: railiance-telemetry
status: proposed
owner: codex
topic_slug: railiance
created: "2026-08-11"
updated: "2026-08-15"
related:
- ADR-0008
- RMASTER-WP-0023
state_hub_workstream_id: "60f5fe7c-9749-40be-9945-6ad608398b3f"
---
# Bootstrap State Hub integration
## Goal
Finish State Hub onboarding for `railiance-telemetry`: confirm the
generated contract files, record that this repo has no runtime yet, and
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
workplans use `RTEL-WP-`. Do not change this file's `id` or hub UUID.
## Review Generated Integration Files
```task
id: RAILIANCE-WP-0001-T01
status: todo
priority: high
state_hub_task_id: "de712c57-79fa-49be-97a2-873e9e1a8bec"
```
Confirm INTENT/SCOPE/AGENTS match the seeded Q2 evidence-plane
boundary. Close leftover README contradictions (placement is Q2, not an
open S3-vs-Quality question). Set the *next* workplan prefix to
`RTEL-WP-`, not `RAILIANCE-WP-`.
## Verify Local Developer Workflow
```task
id: RAILIANCE-WP-0001-T02
status: todo
priority: high
state_hub_task_id: "79febfbb-6a67-40e0-9c24-96ff83ab706e"
```
There is no implementation yet. Record that in AGENTS.md (no install /
test / run). Do not invent a Makefile that deploys monitoring. T03 owns
the first verification command.
## Seed First Real Workplan
```task
id: RAILIANCE-WP-0001-T03
status: todo
priority: medium
state_hub_task_id: "adea3657-c074-443b-9c5e-3c2095dd7c5b"
```
Seed `RTEL-WP-0002` for the **emission contract**: what other layers
emit, retention for restore/rollout proof, and the operator-facing
health surface. Out of that plan: the deployable monitoring package
(future `rapp-*`), conformance *meaning* (owning repos /
`railiance-master`), and any public scrape/UI (forbidden until ADR-0006
`production-approved` plus an ADR-0008 grant; default `exposure` is
`private`).
After workplan file updates, run the sync locally from this repo
checkout:
```bash
statehub fix-consistency
```