The scope to write into; must match one of the session's write patterns.
A derived scope must not share its first dot-segment with any source's
scope (the server rejects it with LINEAGE_SCOPE_UNDER_SOURCE_PREFIX):
put derivatives in the app's own namespace.
OptionallineageThe data points this record was derived from: ids
(deriveDataPointId) or { ownerAddress, scope } pairs the SDK
derives the id from. Distinct, at most MAX_LINEAGE_SOURCES, all
belonging to the same owner as the target scope, never the record's own
id. Sent lowercased as the record's lineage field, inside the signed
bytes. [] is an explicit root statement and is sent; absent or null
makes no statement. Pairs also let the SDK apply the naming rule
(assertDerivedScopeNaming) before anything is signed.
Optionalfetchfetch to use; defaults to globalThis.fetch.
Optionalinit: RequestInitOptionalinit: RequestInitOptionalheadersExtra request headers.
OptionalmetadataCaller metadata stored with the record (X-Vana-Metadata, part of the
signed $binary record). Must not contain lineage (use the option) or
a reserved key.
A binary write: the bytes are stored as a
$binaryrecord.