How well would TB fare as a more general datastore for tasks that aren't specifically accounting? I guess the hard part may be mapping the source domain model neatly into a double-entry accounting representation. Some diverse examples off the top of my head (and my guess): chat messages (no); logging (no); application metrics (yes, but it doesn't fit very well because metrics can trade a lot of features for throughput?); tracking inventory (definitely); tracking deployment and status of cloud resources [like k8s' etcd] (probably?).