...
Again, you only need a register a ruleset once on any engine.
Deploy
Deploying includes two different tasks: flushing cached artifacts from the ruleset in the engine and installing the ruleset in any picos it needs to run in.
Flushing
Because the engine compiles and caches the ruleset, whenever you make changes to the source, you need to flush the ruleset. The Git pre-commit hook you installed in the Build step does that automatically for local engines (hosted on the local machine). If you're not deploying to a local engine you will need to set up a method for flushing the ruleset as part of deploying it. You can do this manually from the registered rulesets page (at rulesets.html) on the pico engine or using a URL.
installing
Install the ruleset in your pico by navigating to the Rulesets tab in the pico interface. For rulesets that you've already registered, you can simply select their name from the pulldown menu and click "install ruleset". 
Note that you can register and install the ruleset in one step from this page for convenience by installing from a URL.
Test
The pico engine UI includes support for testing your rulesets. See the detailed instructions for more information on how to configure and use that feature.
...