The Content Release a watched doc resolves under, or undefined for a raw
read — how a reactive adapter turns the watch-set's perspective into the
per-doc release its store needs. Instance / ancestor / system.release docs
read raw (readsRaw); a content doc resolves under the leading
release in the stack. The engine never forms the versions.<release>.<id>
id — the adapter does (Studio's editState version arg, the SDK handle
{releaseName}). A non-array perspective (raw/published/drafts)
carries no release, so content falls back to draft/published.
Note: this resolves a single release — the documented instance.perspective
shapes ([release] / [release, "drafts"]). The stores' per-doc reads take
one release, so a multi-release stack can't be observed through them; the
engine's own fetch path (hydrateSnapshot) — and the SDK adapter's
query-store route for stacks without a 'drafts' entry — honour the full
stack via client.fetch({perspective}).
The Content Release a watched doc resolves under, or
undefinedfor a raw read — how a reactive adapter turns the watch-set's perspective into the per-doc release its store needs. Instance / ancestor /system.releasedocs read raw (readsRaw); a content doc resolves under the leading release in the stack. The engine never forms theversions.<release>.<id>id — the adapter does (Studio'seditStateversion arg, the SDK handle{releaseName}). A non-array perspective (raw/published/drafts) carries no release, so content falls back to draft/published.Note: this resolves a single release — the documented
instance.perspectiveshapes ([release]/[release, "drafts"]). The stores' per-doc reads take one release, so a multi-release stack can't be observed through them; the engine's own fetch path (hydrateSnapshot) — and the SDK adapter's query-store route for stacks without a'drafts'entry — honour the full stack viaclient.fetch({perspective}).