Related canonical identities, organized together. A shared family is not a claim that every release is mutually compatible or equally qualified.
Portable architectural transfer object for migration, interrupt, virtualization and accelerator boundaries, carrying canonical state references, PC/retirement, domain/epoch, translation, event and MCT context.
Source / reference evidenceVersioned side metadata communicates execution class, dependency, precision, locality, deadline, security, reproducibility, migration and accelerator-shape intent without replacing the canonical stream.
Source / reference evidenceMigration is permitted only at precise boundaries with valid contract, no pending store/fault and compatible domain context; implementation-private resume hints never define correctness.
Source / reference evidenceSeparates permanent application-visible instruction semantics from optional execution-shape metadata so implementations and accelerators can evolve without redefining program meaning.
Source / reference evidenceStart with a chip, a software release or a single IP block.