From 069ecc369cb74c25be140d028b9884a8f21698fb Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Tue, 29 Sep 2026 13:10:36 +0200 Subject: [PATCH] Note the operator's future cross-store variant direction under ruling 3 Co-Authored-By: Claude Opus 5.5 --- docs/document-variants-target.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/document-variants-target.md b/docs/document-variants-target.md index 42b07bc4..0e62ece1 100644 --- a/docs/document-variants-target.md +++ b/docs/document-variants-target.md @@ -97,6 +97,11 @@ edited in CultCache Studio: observe the change atomically. - Compare-exchange (`Expect`) tests the stored delta. The resolved document is derived. - **3, cross-store bases: no.** A variant and its base live in the same store. + *Future direction (operator, 2026-09-30, from Aetheria moddable ships):* "we'll want cross-store variant + support eventually; modders should be able to add variants of existing items without modifying the + original". Ruling 3 holds for this campaign. A mod store layering variants over a shipped catalog is the + named future consumer that would reopen it. Until then, no consumer builds its own cross-store resolver: + Aetheria's compose step stays out of resolution. - **4, CultNet: deltas.** - **5, runtimes: C# first.** TypeScript, Python, Rust and Kotlin refuse a store or snapshot containing variants, loudly, until each implements resolution.