Interesting. Rather than "wait X days" and "then attack Y," which is two tasks, could you say, "Attack Y on the last day of Calibration" and call that one task?
As per Savant and Sorcerer
, no, that would just be a semantic reordering of the same pair of tasks. A delay would only be relevant if it's part and parcel of the core task (like "push forward the seconds hand of my demon-powered clock once per second").
Mind you, Savant and Sorcerer
presents the issue in terms of demons being obsessed with their tasks and being unwilling to hang around waiting before fulfilling the task. But I think that parsing out the delay as a separate task is the only way for that ruling to make sense.
Does this also mean you can't put in triggers that serve as "input?"
That's correct. You must rely on the demon's own judgment as to what actions it takes in support of the task.
Two examples, the first of which I think is an "intended" use for taskbinding and the second which I think might potentially be an abuse:
1) "Defend my castle against all who I do not grant permission to enter."
2) "Bring me a cup of pure, clean water whenever I beckon you like this," including a demonstration of the beckoning hand signal.
#2 is unacceptable because it relies on outside input. Fill the cup every hour? Sure. Fill the cup when it thinks you might be thirsty? Sure. Fill the cup in response to your instructions? Nope.
#1 is actually unacceptable as well, for the same reason. Grant admission to a set of people listed during the binding? Sure. Grant admission to people wearing specific livery or who repeat a certain password? Sure. Grant admission in response to your instructions? Nope.
Ultimately, this is to draw a bright line between task binding and regular binding, to avoid the inevitable task of "obey me as if you were bound in the normal way, but since it's a task you have to do it forever instead of for a year." It's kind of like how you can't wish for a genie to give you more wishes.