Translator Compatibility Note

Status: Compatibility and migration evidence. This is not a target architecture contract.

The target runtime route is:

Service object sources
  -> World canonical model
  -> Canonical runtime dataset
  -> Runtime adapter
  -> Platform renderer

Every runtime consumes the same logical runtime dataset from World. Runtime differences belong in runtime state management, scene construction, rendering, interaction, and projection. They do not require runtime-specific service contracts or runtime-specific World payloads.

Older work used the term "translator" for components that projected a World model into capability-specific payload shapes such as expanded screen or spatial room contracts. That work is useful migration evidence because it proved object identity, actions, permissions, contexts, field state, findings, and fallbacks can survive different presentations. It is not the target architecture.

Compatibility translators may remain temporarily to emit old /world/session, surface_runtime, field_runtime, panel, stack, rail, or dock shapes for existing runtimes during migration. They must not be used as the source of new runtime requirements.

New runtime work must use the Runtime Contract and World Model Contract. New service work must use the Object Source Contract.