--- id: RAIL-HO-WP-0008 type: workplan title: "Publish railiance01 resource and commercial evidence" domain: financials repo: railiance-infra status: ready owner: codex topic_slug: railiance created: "2026-08-11" updated: "2026-08-11" related: - RESOURCE-WP-0003 state_hub_workstream_id: "7122657f-87c8-46b5-a725-a1af1ba0af12" --- # RAIL-HO-WP-0008 — railiance01 resource and commercial evidence ## Goal Provide the non-secret infrastructure facts needed to maintain `resource:hosteurope:railiance01` in resource-control without making resource-control authoritative for host provisioning or fin-hub's booked cost. Origin: `RESOURCE-WP-0003-T04` delegated evidence gap. ## T01 — Identify the provider resource and lifecycle ```task id: RAIL-HO-WP-0008-T01 status: todo priority: high state_hub_task_id: "cde55584-229d-4e27-8fc8-0f54d78c71ed" ``` Record the Host Europe product/service class, non-secret provider resource ID, account reference suitable for joins, country/region or residency evidence, order or commissioning date, renewal date, cancellation deadline, and contract term. Reference source evidence without committing invoices, credentials, customer numbers, or payment instruments. Done when resource-control can update the provider and lifecycle fields with provenance, while unknown or restricted fields remain explicitly classified. ## T02 — Publish host capacity and utilization evidence ```task id: RAIL-HO-WP-0008-T02 status: todo priority: high state_hub_task_id: "8b0e5547-23ae-4516-b6d7-9c196882d088" ``` Define a stable non-secret observation containing provisioned and usable CPU, memory, root/local storage, traffic allowance where known, and timestamped host-level utilization. Distinguish provider limits from operating-system and Kubernetes observations. Done when at least one reproducible observation can be consumed by resource-control and its source and cadence are documented. ## T03 — Record infrastructure operations labor and exit inputs ```task id: RAIL-HO-WP-0008-T03 status: todo priority: medium state_hub_task_id: "8bdaa96f-400b-455f-87db-d5c11e287142" ``` Define the recurring host-maintenance activities and measurable operator-labor inputs, plus the host replacement/cancellation evidence required before exit. Do not estimate another repository's workload labor. Done when resource-control can separate host infrastructure, recurring labor, and migration effort in forecasts and optimization cases. ## Acceptance - [ ] Provider identity and lifecycle evidence is non-secret and attributable. - [ ] Capacity and utilization observations have timestamps and provenance. - [ ] Host labor and exit inputs can be consumed without duplicating booked cost.