• I could add l2 aT and l2 aK, they will probably be used again sometime.
• I have (?*>) and (<*?) for aT<py and aK^.py. I could use (**>) = aT<my and (<**) = aK^.py and while I'm at it (+*>) = aT<so and (<*+) = aK^.so.

• I could add l2 aT and l2 aK, they will probably be used again sometime.
• I have (?*>) and (<*?) for aT<py and aK^.py and (+*>) and (<*+) for aT<so and aK^.so. I could use (**>) = aT<my and (<**) = aK^.py.

(<*~) =
  f' $ fb < ap pM

yyc$sk$h_<*~(mY<xys)>~ʃ

(<~) =
  f' $ fb < ap pM

yyc$sk$h_<~(mY<xys)>~ʃ

Old versions

Reflection

This is ok. I'm not too happy with it but I initially expected much worse. This really has more of a glue problem than anything else.

• I could add l2 aT and l2 aK, they will probably be used again sometime.
• I have (?*>) and (<*?) for aT<py and aK^.py. I could use (**>) = aT<my and (<**) = aK^.py and while I'm at it (+*>) = aT<so and (<*+) = aK^.so.

The above are minor fixes, but I think the thing that would really fix the glue problem is having a version of (>~) which just returns the result from the left-hand side instead of the right hand-side. So:

(<*~) =
  f' $ fb < ap pM

In which case this could look like:

yyc$sk$h_<*~(mY<xys)>~ʃ

Although this wouldn't make this answer shorter than implementing either of the above, this does seem like the solution lightest on the glue and an operation which has a large reuse potential

Old versions