Kind of a crap article that doesn't (1) link to the code (or to the golang implementation from the paper) and (2) doesn't even have the word "CAP" in it.
It doesn't mention CAP because it's obviously opting for consistency over availability, and is explicitly compared next to other systems that treat consistency as paramount. There's nothing interesting or new about it's approach to CAP.