diff --git a/BUILD.md b/BUILD.md
index 4bfbffe..eb04577 100644
--- a/BUILD.md
+++ b/BUILD.md
@@ -247,9 +247,9 @@ generation, and signing have succeeded. If a stopped publisher leaves staging
 or backup directories behind, rerun it with ``--force-unlock`` to recover the
 previous repository before starting a new publication.
 
-Repository publication requires a complete release for its manifest version.
-Version 1 contains seven architectures; version 2 also requires `s390x`. The
-packages are `noarch`, and each publication contains that release's full set.
+Repository publication requires all eight current architectures. Version 1
+remains readable but cannot replace the current repository because it lacks
+`s390x`. The packages are `noarch`, and each publication contains the full set.
 
 The release checksums cover the unsigned input packages. If repository signing
 is enabled, `rpmsign` changes the deployed RPM bytes after collection.
diff --git a/genesis-openembedded/README.md b/genesis-openembedded/README.md
index eef1b7e..fe9f78a 100644
--- a/genesis-openembedded/README.md
+++ b/genesis-openembedded/README.md
@@ -89,11 +89,12 @@ repository with a single rename, under one global publish lock, so a failed or
 interrupted publication leaves the previous repository exactly as it was.
 
 Both consumers verify package identities and checksums before publication.
-Version 2 releases require all eight architectures. Seven-architecture version
-1 releases remain publishable. Building a version 2 release requires an
-xcat-core revision with the `s390x` OpenEmbedded target. Merge or deploy that
-xcat-core change first. A management node can install an image for a different
-target architecture.
+Version 2 releases require all eight architectures. Version 1 remains readable,
+but current publishers refuse it because replacing the repository would remove
+`s390x`. Building `s390x` requires an xcat-core revision that reports the target.
+Merge or deploy that xcat-core change first. Builds for the other architectures
+still accept older xcat-core revisions. A management node can install an image
+for a different target architecture.
 
 Without `--genesis-release`, both builders keep their existing behavior. The
 new packages do not provide, replace, or obsolete the old package names.