diff --git a/workplans/TREV-WP-0016-wave2-resource-right-sizing.md b/workplans/TREV-WP-0016-wave2-resource-right-sizing.md
index b9163a0..665a7be 100644
--- a/workplans/TREV-WP-0016-wave2-resource-right-sizing.md
+++ b/workplans/TREV-WP-0016-wave2-resource-right-sizing.md
@@ -4,7 +4,7 @@ type: workplan
 title: "Wave-2 resource right-sizing from the 2026-10-21 allocation review"
 domain: infotech
 repo: target-revenue
-status: ready
+status: finished
 flavor: implementation
 owner: claude
 topic_slug: infotech
@@ -26,10 +26,8 @@ Origin: the 2026-10-21 node allocation review (`RESOURCE-WP-0008-T03`, feeding `
 
 ```task
 id: TREV-WP-0016-T01
-status: wait
+status: done
 priority: medium
-needs_human: true
-blocking_reason: "Wave-2 cluster write; founder approval for wave 2 not yet given (2026-10-21 interview)"
 state_hub_task_id: "385c3c88-d5b1-55e3-88b7-ada3547985f6"
 ```
 
@@ -66,3 +64,7 @@ Status stays `wait` / `needs_human`. Local commit only: not pushed, not applied.
 - Diff: resource fields only on the Deployment and Cluster. A sync also runs the Sync-hook Jobs `target-revenue-migrate` and `target-revenue-bootstrap-binky` again, which is the normal behaviour of this path. Tests pass.
 - Restart: yes. The single-instance CNPG cluster restarts PostgreSQL.
 - Apply: push, bump the `targetRevision` pin in `railiance-platform/argocd/railiance01/applications/target-revenue.application.yaml` (another worker's repo), then `argocd app sync target-revenue`.
+
+## Applied — 2026-10-22 (TREV-WP-0016-T01)
+
+Applied under the founder's wave-2 authorization (the-custodian docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md), after a full-render diff against live that showed resources only. ArgoCD pin f110a4e (railiance-platform d0d0db7). The first sync stopped while the CNPG restart was in progress; a second sync succeeded. The app is at 5m/64Mi and target-revenue-pg at 50m/80Mi, healthy; Synced and Healthy. Evidence: the-custodian docs/evidence/2026-10-22-wave2-apply.md.