Joe Bryan

I'm making an assumption that should be stated explicitly: `$pith` will be used as an internal type, for `wire`, `%clay` paths, in namespace handlers, &c. From outside, paths will be...

> We keep learning that Clay is only really good for managing source code. @belisarius222 can you expound on this? %clay is not very suitable for arbitrary outside data (due...

This is not ready and in need of further work, see https://github.com/urbit/urbit/pull/5939#discussion_r943880778.

This is not ready, see my linked draft PR.

The additional `%note`s are because `+decorate:ax` only uses the annotation, it doesn't consume it. You also need to call `+clear:ax` in the right spot (and figure out where that is)....

Further context: - bail motes (runtime exceptions): https://github.com/urbit/urbit/issues/3263#issuecomment-670707729 - an older, longer writeup on the state of recovery tools: https://github.com/urbit/urbit/issues/3645#issuecomment-709631355 - implementation details of loom persistence: https://github.com/urbit/vere/issues/528

This fix still can't be shipped without ensuring that pilots will not need to replay past the history of the jet mismatch in question. The planned epoch system accomplishes this.

I was actually thinking of #5861, which is the more severe jet mismatch that many have encountered. This PR is the same in principle, but much less severe in practice....

The failure is unrelated (just monorepo things).

I've dropped `?/` and `?\` from this PR (that implementation is at `jb/wthx-moar`).