log routes locally and make them available to other trusted peers #12

can be useful to debug but also for predicting usage and eventually cache ahead of expected execution

consider /metrics as this is the de facto standard for e.g Prometheus

consider past work on provenance, i.e the route, with the data and processed it relied on, should be available after an action is done so that it becomes reproducible and enable the possible to backtrack then compose