The official Orleans 10.4.0 generated serializer encodes owned internal DTOs. ADR-060 defines the current contract. Public HTTP/MCP JSON, exact user content, sortable keys, opaque ZoneTree bytes, canonical hashes and blob payloads retain their concrete owning boundaries.
Abstractions supplies attributed contracts, application envelope validation and
counting destinations for native encoding. Orleans owns codecs, type metadata,
collections, references and field evolution. The standalone serializer uses one
standard registration and native sessions. There is no custom serializer assembly
selection, per-assembly provider cache, wire walker or field inspection codec.
JsonElement uses the official Orleans SystemTextJson codec, without a custom DOM
surrogate. All other active attributed DTOs use generated binary codecs.
Core owns model validation, canonical identity and persisted command outcomes. Storage.ZoneTree owns physical metadata, WAL and file recovery. Orleans carries grain calls. ClientApi owns actual public JSON and authorized admission. MCP checks its actual decoded principal and projection limits rather than parsing Orleans wire fields.
REQ-IS-001..009 / AC-IS-001..009 retain active attributed DTOs and stable aliases, required domain values, native pooled serialization, exact byte accounting, versioned application/storage metadata, bounded payloads, typed grain contracts, signed claims, unsupported-version refusal and exact-source qualification. Native Orleans owns its supported field evolution; KeyLoad adds no private wire grammar. Application validation is required before effects.
The acceptance matrix identifies current operation-level verification. Source/build checks, focused local tests, real process recovery, Aspire SDK/MCP, coverage and delivered-source Linux execution are separate gates. No power-loss, endurance or speed claim follows from a local round trip. Serialization diagnostics remain separate from end-to-end database comparisons.
ReceiveAcrossLanes remains an Orleans parent orchestration capability. Only its individual Receive leaves are canonical Core commands; unsupported generic commands fail before effects. Active generated aliases and field IDs remain stable. Exact user text, canonical operation fingerprints, current persisted authority and joined cleanup stay owned by their actual features.