I think we should try to turn considerations into first-class nodes. The Everything motto is: "Everything is a node." But unfortunately that isn't quite true; some data objects managed by the engine are not nodes. Considerations being one of them. Often all it takes to turn something into a node type is to create a new entry in the nodetype table. Unfortunately, in this case, it would take a bit more than that, since, as currently implemented, considerations get deleted when the consideration is resolved (or by janitors' explicit direction). We'd have to add a 'resolved' flag field, better probably, a 'resolved' datetime field. Something like that. With all the consequent code changes.
I reckon we are the only monastery ever to have a dungeon stuffed with 16,