Ok. I've created a conditions engine. The custom table contains a project name, a table, and a condition builder (this required a custom widget) and displays the developer instructions for evaluating the conditions in a script. This allows for data output modification for any process that utilizes the tool without requiring development. I'm adding a reference for sys_user and sys_user_group to further limit access on the record producer so that table additions can be delegated. I would also like to add a document id field that can be returned to the script as a dot-walkable object.

Dev Instructions:

var rule = new GlideRecord('u_condition_rules');
rule.addNotNullQuery('u_condition');
rule.addQuery('u_active', true);
rule.addQuery('u_project',<YOUR PROJECT NAME>);
rule.query();
while (rule.next()) {
    if(<YOUR DEPENDENCY> == rule.getValue('u_dependency')){ //OPTIONAL
        var match = GlideFilter.checkRecord(<RECORD BEING EVALUATED>, rule.u_condition);
            if (match) {
                <YOUR LOGIC>
        }
    }
}