Write the four rules by analogy with existing proposal and application rules in hts9.soar. You will need:
If the operator gets selected (e.g., if you make it best), it has to do something (i.e. modify an attribute) that will trigger the termination rule, or else an operator no-change impasse will be created. So make sure that you include a rule to have it do something. You might also wish to modify how the initial state gets created, but this depends on how the operator is implemented and what it assumes.
In order to make this file easy to use and make debugging easier,
you will probably want to a put a line in your new file that loads
source hts9.soar). That way, when you load the
new operator file, the ht code gets loaded too. Alternatively, you
can first load hts9.soar by hand.