should mop::observable be an actual part of the mop?

[doy]

It's not quite clear if the intention is to allow user classes to be able to do with mop::observable or not. It's also not mentioned at all in the docs, and the bootstrap doesn't actually end up with it being visible at all. Should it be a real thing, or just an implementation detail?

[stevan]

It is for internal use only.

[doy]

Actually, looking at the bootstrap, it does end up being true that mop::observable ends up in the list produced by mop::meta('mop::class')->roles and such. Is this what we want? If it is, should we document mop::observable as a separate thing? If not, should we fix that?

[stevan]

I think maybe we should move mop::observable into mop::internal:: and make it an implementation detail.

[doy]

Done.