Yes, that's the idea. Though, it is still worth thinking about how someone might accidentally leak a table-based capability via API misuse. For example, if tab

Yes, that's the idea. Though, it is still worth thinking about how someone might accidentally leak a table-based capability via API misuse. For example, if table entries are reused over time you might get a sort of use-after-free situation where you mean to share an old capability but accidentally share the new one that replaced it.