Sector domain and category decided with the repository owner on 2026-08-25.
Classification is not mechanical: the sector describes intended users, so a
confident wrong value is harder to correct than a missing one.
Refs CUST-WP-0067-T05
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
The remote row pointed at 127.0.0.1:18000, a reverse tunnel back to the
workstation. On railiance01 the State Hub runs in the cluster on that same
machine, so the request left the box and came back to reach a local service.
Refs CUST-WP-0067-T07
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
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>
The placement question seeded as open is answered by canon rather than by a
new decision. OAS section 8 defines Q2 Observability as 'telemetry and
monitoring: metrics, logs, traces' - this repo in canon's own words.
The 2026-08-11 coherence review found Railiance had been modelling itself on
one of OAS's six required dimensions and treating everything else as unplaced.
Observability was never homeless; the dimension it belongs to was not in use.
Notes Q7 Governance as the sibling concern - the conformance loop, the other
half of the self-evidencing aspiration this repo serves.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Fills the gap identified in the 2026-08-11 Railiance architecture assessment:
five layers declare they intend to be self-evidencing or auditable, and nothing
owned the place that evidence goes. The live cluster has no monitoring
namespace at all.
Positions telemetry as the evidence plane - it owns the signal, not the meaning
of the signal, so conformance rules stay with the repos that own them. Flags
stack-dimension placement as an open question for railiance-master rather than
asserting a level, so this repo does not repeat railiance-forge's unplaced
state.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
