I am happy to announce that after one change from its public review period, the payload-interop specification has been released as 1.0.0 stable!
From the README:
The Domain Payload Object pattern was first described by Vaughn Vernon at https://vaughnvernon.co/?page_id=40
Whereas a Data Transfer Object provides properties found on domain objects, a Domain Payload Object provides entire domain objects. Its purpose is to transport those domain objects across the architectural boundary from the domain layer to the user interface layer.
The Domain Payload Object is not for intra-domain use. It is only for transporting a domain result across the domain layer boundary back to the calling code, typically the user interface layer.
Further, the Domain Payload Object is independent of any particular user interface. As part of the domain layer, it should have no knowledge of HTTP or CLI contexts.
This project defines only a reading interface, so that any user interface code can know how to get both the result and the status out of the Domain Payload Object.
This project does not define a writing or mutation interface. Creation and manipulation of Domain Payload Objects are core application concerns, not user interface concerns. The domain-specific nature places it outside the scope of an interoperability specification.
Try it out on your next project!