Per-feature permission system
Ilya would like a per-feature permission system: grants for specific features (calendar events, images, and whatever comes next), separate from member approval.
Right now approval is the only permission v3 has. Images are gated on it, and calendar events are about to be too (https://zenmemes.com/threads/thread-20261109001832-f640d603). That works for now, but it's all or nothing. Someone you'd trust to post the occasional event can't get just that. Approving someone also hands them every gated feature at once.
What this needs, roughly: a signed record that grants or revokes one capability for one identity, a way for operators to issue it (CLI and an API, since approval is still CLI-only), a check the write path and read model can both use, and UI showing what you're allowed to do. One open question is whether approval becomes just another grant or stays the base layer the others sit on.