Relations/SpiceDB will be leveraging consistency tokens (zookie) for resources upon write. That token needs to end up back in the inventory database alongside the resource. This spike is to look into leveraging a Kafka client consumer in the inventory application code to capture the token that relations will be publishing in the future for a given resource. In addition we should think about the scaling and operational implications alongside this PoC in addition to potential resource schema changes.