diff --git a/04-ISSUES/081-a-cache-consumer-does-not-use-the-login-it-was-granted/01-diagnosis.md b/04-ISSUES/081-a-cache-consumer-does-not-use-the-login-it-was-granted/01-diagnosis.md
index 114aa7c..6beeda3 100644
--- a/04-ISSUES/081-a-cache-consumer-does-not-use-the-login-it-was-granted/01-diagnosis.md
+++ b/04-ISSUES/081-a-cache-consumer-does-not-use-the-login-it-was-granted/01-diagnosis.md
@@ -41,3 +41,9 @@ tightened the bed: it now asserts baserow said it chose its own cache and that t
 for its password, rather than looking for the absence of errors, which a startup race could have
 produced. Upgrading a running node drops any task still queued in the shared cache; the provider
 removes the consumer's login when the grant goes, a path this change does not exercise.
+
+*Proven, 2026-09-22.* The two-node bed passes with baserow as the catalogue shapes it. On the way it
+found the module's data directory narrower than the image ships it: the cache baserow runs for
+itself runs as another user, who could not reach its own directory under a directory closed to
+everyone but baserow's user. The module declares the image's mode now. The shared cache had hidden
+this: baserow never ran its own until this change.