Advanced scheduling. Creating an event rule

This is an idea for how to solve a bunch of problems and expand Sandy's abilities for handling a series of related events or tasks. Sandy currently isn't able to handle advanced requirements for keeping track of a sequence of related events. The basic recurring event works, but if a sequence requires more detail or a dependency on something else, it doesn't work as well as it could. I have an idea how an "event rule" could be used to solve this.

The idea is that there be some way of separating out the "event rule" from the actual scheduled events. One "event rule" would be used to create a series of individual events. Each individual event would be able to be scheduled, delayed, marked as @done, or canceled independently of the rule. Each individual event would have a reference number or link back to the rule that created it. The "event rule" can contain more description about exactly what should be scheduled and when. The rule is also editable separately from the individual events that were created from it.

This idea would allow a recurring event to be tailored to better meet requirements. It would solve things like: adding an "end date" to a recurring event, being able to cancel a specific instance of a recurring monthly event but not canceling every future event in the series, and specifying a dependency so that the next event won't be scheduled until the current event is marked @done.

Any sort of recurring event could be stored as an event rule. The idea is that the "rule" would not have a specific date for itself, but it would contain a set of rules for creating a series of dates. The rule itself would not be scheduled or recorded as an appointment, or entered on a calendar. Instead, the rule would be used to create a series of separate individual reminders or todo or some other items, and these individual items would be scheduled and/or entered into Sandy's reminder system. Each of these individual items in the reminder system would have a link back to the larger, more detailed, rule that created it. When the item is done (marked @done or the date passes, etc), then Sandy would follow the link back to the rule that created the item, and follow the rule instructions to create the next event in the series.

This would fix a bunch of problems, and provide more customization options for scheduling a series of events. For example, Sandy currently isn't able to schedule a recurring event that ends on a certain date. Like attending class every week until May 7. See http://getsatisfaction.com/iwantsandy...
With this new idea, there would be a way to specify more details about how the recurring event should work. And when it would end.

There are also some issues with marking a recurring todo @done, because currently it isn't clear if Sandy will interpret the entire sequence to be done, not just that individual instance of the event.
See http://getsatisfaction.com/iwantsandy...

The rule idea would also allow more fine tuning of recurring events. An event would not have to be evenly spaced out such as every week or every month. You could schedule a task to occur on two or three specific days of the year.

This idea could eventually be expanded to allow a series of related tasks. The "rule" could not just describe a recurring event, but it could also be used to describe just about any kind of a series of related tasks. Each item in the list would be scheduled (and/or added to the todo list) after the previous item was finished or marked @done. If this was implemented, then it would be possible to have Sandy keep track of the status of a larger "project" consisting of multiple actions. (as in GTD) As each item is marked "done" then Sandy would schedule and/or add the next item to the todo list.
See http://getsatisfaction.com/iwantsandy...

Does this seem like a reasonable idea? Any comments would be appreciated.