RPF-WP-0018 T07: route findings F1-F5 and close the workplan

Replies sent to policy-nexus (F1 substrate boundary, F2 ADR surface, F5
frontmatter corpus), rapp-postgres and net-kingdom (F3 rule/number split,
F4 provider-versus-consumer ladders), tenant-engine (placement policy
answering its three asks), adaptive-pricing (co-signature requested) and
railiance-master (bao.coulomb.social still open, second public name
proposed). Routed inbox marked read.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

SCOPE.md

@@ -89,6 +89,11 @@ policy, and lane governance.
   declared, not deployed. OpenBao package boundary and PAT cutover are
   closed. Platform rapp declarations conform (`RAILIANCE-WP-0015`).
   Versioned consumer interfaces: `docs/s3-consumer-interfaces.md`.
+  Tenancy posture and database placement policy are declared
+  (`docs/tenancy-posture.md`, `docs/placement-policy.md`, `RPF-WP-0018`).
+  Two open items they surfaced: `apps-pg` has no backup configured, and
+  both shared clusters owe a declared consumer ceiling before their third
+  consumer. Decisions are now recorded as ADRs in `docs/adr/` (ADR-0003).
 - Known drift: State Hub attributes ~11 capabilities to this repo, including
   S1/S2/S4/S5 concerns it does not own. The four `capability` blocks in this
   file are authoritative; the hub carries stale pre-split attributions