diff --git a/docs/site/src/content/docs/tutorials/first-run-with-solmara-lab.mdx b/docs/site/src/content/docs/tutorials/first-run-with-solmara-lab.mdx
index ad0ec17e..67b204d1 100644
--- a/docs/site/src/content/docs/tutorials/first-run-with-solmara-lab.mdx
+++ b/docs/site/src/content/docs/tutorials/first-run-with-solmara-lab.mdx
@@ -38,10 +38,14 @@ Do not use the generated local keys in production.
 For a standalone local project generated from your own data, use the `registryctl` tutorials:
 [run a protected registry API](../publish-spreadsheet-secured-registry-api/) or
 [evaluate a claim with Registry Notary](../verify-claim-registry-api/). Clone Solmara Lab when you
-want the full multi-service country demo. The hosted path remains visible for inspection, but its
-credential continuation is held by [GH#330](https://github.com/registrystack/registry-stack/issues/330)
-and the incomplete [GH#198](https://github.com/registrystack/registry-stack/issues/198)
-fresh-reader run.
+want the full multi-service country demo. The planned final 1.0 release-candidate reader run in
+[GH#198](https://github.com/registrystack/registry-stack/issues/198) requires a tagged Registry
+Stack candidate and a Solmara Lab release that atomically pins the matching `registryctl`, Registry
+Relay, Registry Notary, and image digests. Where Registry Notary applies, the run must also prove
+one Registry Notary instance and one Notary-owned PostgreSQL database per Registry Relay authority,
+including restart persistence.
+{/* TODO[evidence]: Replace this issue-tracked plan with a stable public run artifact and
+    immutable Solmara Lab release link before presenting the gate as completed evidence. */}
 
 ## Prerequisites