In semi-automatic mode, or for saturating a consistent theory, the typical interaction cycle with Saturate consists of reading a set of (general) clauses, issuing commands to define the reduction ordering, inference system, redundancy checks, system messages and profiling flags, and, finally, starting the saturation process. If saturation terminates or is interrupted (by typing control-C), proofs of generated clauses can be inspected. Saturated systems of clauses can be filed out for later uses as modules of more complex theories.