However, if you're claiming to make a system including "the best" of these three tools, any reader will expect the obvious property that Jujutsu can faithfully simulate all possible workflows from these tools.
Since it is essentially a layer on top of Git, I am fully convinced that it can simulate Git (for example by using Git directly if needed). But since you fail to explain your algorithms and core ideas in the docs, I'm also convinced that it can't simulate draft changesets from Mercurial.
Since I know what it takes to simulate patch commutation (from Pijul), especially together with the snapshot-based nature of Git, I also doubt that it can simulate that. Obviously, I'd be happy to be proven wrong, because I'd learn something really cool!
I've asked you this question before somewhere else: I still don't know whether Jujutsu satisfies the most basic property any user expects from merges: associativity. If not, it's ok, Git, Mercurial, SVN, Fossil also fail to guarantee it on all merges.
I'm also surprised you aren't claiming to do better than Darcs. Even though I've never used `darcs replace`, and I failed to implement that command in Pijul, I'm nevertheless a bit jealous, because I find that quite elegant.