From e6dedcdefde1c0e15b2a77dc87abae59534bc968 Mon Sep 17 00:00:00 2001 From: Jeremi Joslin Date: Fri, 24 Jul 2026 00:12:50 +0700 Subject: [PATCH 1/2] docs: clarify the Solmara reader gate Signed-off-by: Jeremi Joslin --- .../docs/tutorials/first-run-with-solmara-lab.mdx | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) 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..501ff9f3 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,11 @@ 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 pinned atomically to that candidate. +{/* 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 From bcd5b97dc4fcb098ecce6ee85279bd3e7fd8294c Mon Sep 17 00:00:00 2001 From: Jeremi Joslin Date: Fri, 24 Jul 2026 00:27:43 +0700 Subject: [PATCH 2/2] docs: complete the Solmara reader criteria Signed-off-by: Jeremi Joslin --- .../content/docs/tutorials/first-run-with-solmara-lab.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) 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 501ff9f3..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 @@ -40,7 +40,10 @@ For a standalone local project generated from your own data, use the `registryct [evaluate a claim with Registry Notary](../verify-claim-registry-api/). Clone Solmara Lab when you 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 pinned atomically to that candidate. +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. */}