Taking Fibery’s fundamentals as context, how do you consider ‘recurring tasks’ should work?
Is it a single Task entity which has multiple dates associated with it (1 Jan 2025, 1 Feb 2025, 1 Mar 2025, etc.)? In other words, a single entity shows on a calendar/timeline in multiple places.
Is it a set of entities, each with a single date field, that are somehow associated with each other? What significance does this association imply? Do changes to one entity in the set get replicated to other entities in the set, or are they functionally independent?
Is it a Task entity which spawns a clone of itself after a certain period of time (and the clone spawns a clone of itself, etc.)? What is the relationship between an entity’s ‘Due date’ and the date at which spawning should occur?
I think different people have different expectations for what ‘recurring’ entities actually means (and this may depend on the tool(s) you are most familiar with using).