Hi Tim,
By essence a rule just returns true or false. Hence the ‘architecturally correct solution’ would be to split your rules in smaller blocks…But
You could call a microflow from the rule, create a rule object and associate it to your session.
Then in the rule at each test you can associate feedbacks to this rule. After calling the rule in your microflow, retrieve the associated feedbacks and present them to the user.
An example is on its way to the appstore, but awaiting approval. (RuleFeedback) in the meantime the mpk is available here:
https://www.dropbox.com/s/ug66no270bygb46/RuleLoggingDemo.mpk?dl=0