With  MCO-1609  we will need to signal that the tests that evaluates OCL are passing or not. We have experience creating those tests straight into the origin repository, but doing so may require a bit more effort, specially because we do not have control over the review process of that repo.

If OTE is a viable solution we can create the OCL tests in our own repo and manage the lifecycle of them, reducing the time we need to invest to get OCL component rediness done.