Publish cluster resource evidence and gate ThreePhoenix

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa

workplans/RCLUSTER-WP-0007-threephoenix-ha-cluster.md

@@ -10,7 +10,7 @@ topic_slug: railiance
 repo_goal_id: "6ea441f7-7fe3-4598-922b-38baf20c0580"
 state_hub_workstream_id: "9e208376-23f1-40c7-9813-fac1f7d6ad3b"
 created: "2026-02-25"
-updated: "2026-08-15"
+updated: "2026-08-22"
 related:
   - REEF-RAILIANCE-WP-0003
   - RAIL-BS-WP-0014
@@ -48,6 +48,21 @@ grant.
 The bootstrap copy of this file is retired. Do not re-open
 `RCLUSTER-WP-0007` in `railiance-bootstrap`.
 
+## Implementation gate
+
+This workplan remains `backlog`; its tasks must not move to `progress` until
+the preflight in `docs/threephoenix-implementation-gate.md` passes. In
+particular, three independent source-backed reef members must be approved,
+provisioned, and S1-converged, with their shared power, storage, host, and
+network dependencies recorded. The current Railiance01 node plus guests on one
+physical host do not satisfy that gate.
+
+Passing the gate also requires an approved private inter-node network design,
+join-token custody/rotation through the platform custody path, and explicit
+operator approval for destructive node actions. This repository must not buy
+provider capacity, open public listeners, install Longhorn, or mutate the live
+single-node cluster merely to make the target appear ready.
+
 ## Why This Belongs Before Forgejo
 
 Forgejo will be the source forge, package base, and Actions surface for the
@@ -267,6 +282,10 @@ This workplan should precede the Forgejo production cutover. It should also
 shape the Stage 2 and Stage 3 gates in `RAIL-BS-WP-0006` so canaries and
 promotions operate against the real HA substrate.
 
+The first executable dependency is the machine-checkable/manual preflight in
+`docs/threephoenix-implementation-gate.md`; until it passes, this plan is design
+and dependency preparation only.
+
 It is the substrate dependency for:
 
 - `reef-railiance/REEF-RAILIANCE-WP-0003` T04. After the S2 drill passes, the

workplans/RCLUSTER-WP-0014-capacity-utilization-and-allocation-evidence.md

@@ -4,11 +4,11 @@ type: workplan
 title: "Publish cluster capacity, utilization, and allocation evidence"
 domain: financials
 repo: railiance-cluster
-status: ready
+status: finished
 owner: codex
 topic_slug: railiance
 created: "2026-08-11"
-updated: "2026-08-15"
+updated: "2026-08-22"
 related:
   - RAIL-BS-WP-0007
   - RESOURCE-WP-0003
@@ -42,7 +42,7 @@ fin-hub allocate. No booked EUR in this repo.
 
 ```task
 id: RCLUSTER-WP-0014-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "a144bf1d-0402-4526-9bda-17846390270c"
 ```
@@ -56,11 +56,17 @@ metrics, and source commands.
 Done when repeated observations use a stable machine-readable interface and
 resource-control can distinguish headroom, reservations, and actual usage.
 
+**Outcome (2026-08-22):** `make cluster-observe REMOTE=railiance01` now emits
+versioned, timestamped JSON with node allocatable/observed resources,
+namespace/workload requests and limits, PVC/PV/storage-class state, stable
+units, source commands, and explicit gaps without reading Secrets or pod
+environments.
+
 ## T02 — Publish the failure-domain and storage contract
 
 ```task
 id: RCLUSTER-WP-0014-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "6460d9aa-3ded-420a-bf01-f0ccdeee0a02"
 ```
@@ -73,11 +79,16 @@ current capacity.
 Done when consumers can calculate correlated-failure risk and recognize which
 state remains local to `railiance01`.
 
+**Outcome (2026-08-22):** the evidence contract reports one Ready node,
+`local-path` storage, `threephoenix_ready: false`, and the missing independent
+region/zone labels. Target HA and Longhorn capacity are not represented as
+current facts.
+
 ## T03 — Define technical allocation-driver evidence
 
 ```task
 id: RCLUSTER-WP-0014-T03
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "e5ff9b6c-e883-4356-9eca-b31757661d2f"
 ```
@@ -90,8 +101,22 @@ do not convert the result into booked spend.
 Done when resource-control can create an explainable allocation and fin-hub can
 reconcile it to referenced financial facts.
 
+**Outcome (2026-08-22):** `cluster-raw-drivers-v1` publishes CPU requests,
+memory requests, PVC bytes, observed usage, totals, residual capacity, and
+uncertainty, while leaving formula selection and booked cost to
+`resource-control`.
+
 ## Acceptance
 
-- [ ] Capacity evidence separates allocatable, requested, limited, and observed.
-- [ ] Current single-host/local-storage risk is machine-readable.
-- [ ] Allocation drivers reconcile to explicit totals and residuals.
+- [x] Capacity evidence separates allocatable, requested, limited, and observed.
+- [x] Current single-host/local-storage risk is machine-readable.
+- [x] Allocation drivers reconcile to explicit totals and residuals.
+
+## Completion evidence
+
+- `python3 -m unittest discover -s tests -p 'test_*.py' -v`: 2 tests passed.
+- Live read-only capture:
+  `docs/evidence/resource-reef-railiance-k3s/observations/20260822T100349Z.json`.
+- Observed totals: 1 node, 53 workloads, 25 claims; 4,000m allocatable CPU,
+  3,830m requested CPU, 16,770,076,672 allocatable memory bytes, and
+  137,438,953,472 requested PVC bytes.