....what would be the necessary components for a. A Spacetimestamp?
One component would be, or would be similar to, a 64 bit integer timestamp that is the better solution to the 2038 problem. Any measurement is going to be relative. Any revenue point can be simplified, as long as it can be ascertained what it's simplified from.
We could say somthing like width depth and height from some point related to TAI or UTC but no point remains valid over the appreciable scale of a 64 bit timestamp
That is to say, a Spacetimestamp of usable resolution might be
8.8 * 10^26 m across for the visible universe... let's give it 128bits for micron accuracy. Just because 96 bits isn't enough for millimeter accuracy.
That's 448 bits for 3.1 dimensions. Then you need to start adding on details to have any indication of what the relevant location may be now.
Yet another one user instance
So theoretically a Spacetimestamp would be measured in kilobytes before redundancies ... hamming but better. And yes, hamming should be built in. At the distances this is useful, build hamming in.