You’re right, and I think you’ve done a great job of illustrating where in your case and for your needs, Fibery’s depth and flexibility and integrated data model does exactly what you need, and does it very well. But your situation sounds fairly complex, and I do think that generally speaking Fibery needs more ability to better address the simpler or intermediate cases. The email example is probably not the best one to illustrate this (though I still feel like there’s some benefit to a “lighter” field instantiation model like some contact managers have).
In any case it is certainly drifting away from the original example here, which is that reminder-like functionality is fairly clunky in a database, at least the way Fibery currently works. If you disagree with that, perhaps you just feel differently about the UI/UX vs. capability trade-off. There are plenty of people who do, and it’s a very reasonable perspective to have! Tons of people use Org Mode to do everything, which would absolutely drive me crazy. Others just decide to completely program their own tools, and that’s the other extreme of course. But I think the majority of users (i.e. Fibery’s potential customers) tend to want a bit more “ease of use” and “simplicity”. So I recognize your email setup may feel simple to you, and I absolutely see its benefits and have to agree the downsides are small, but I don’t think everyone feels quite that way about it. More importantly, there are other cases where the kinds of “ease of use” or “simpler ways to achieve a goal” that have been talked about here are more needed, I think (again the reminders example, or watcher status, activity notifications, etc).
Thank you for the thorough outline of your system and its benefits though! That is definitely a Fibery strength and I love it for that when I need such capabilities, to be sure.