Hello. Here are some notes that might be helpful, or might be totally worthless.  If someone wants to follow-up with me on this material, post a reply, and I'll dialogue with you. OK.  Here are the notes.... ---------------------------- Dip into each of the elements of the triple, (context, action, result), to learn about how someone else achieves a result. You start by describing a result to a person.  If he doesn't achieve that result, as far as he knows, either your question's answered, or you go on to find that part of the result, or a more general form of the result, that you both do accomplish. What you are comparing is means to an end, not just the accomplishment of the end.  So once you have your client describing how he accomplishes the result, you are getting information to compare to your own behavior.  The how of the result's accomplishment can include information about the context in which the action is performed. Provide means to elicit, at any scale, the sequence, selection, iteration of actions.  A person will use commonsense, or some set of criteria, involving checking the client's triple description against her own, to decide what part of the triple (context, action, result) needs to be elicited for each action under consideration.  I don't think it's helpful to treat actions as totes, so you can distinguish iterated actions from totes.  An iterated action is just an iterated action, not a tote. An action has results, when it is iterated, and a separate set of results when the end of its iterations are reached.  Sometimes a person will want to know more about the iterated action, or its results at some iterations, or over a range of iterations, and sometimes a person will just want to know the results after the iterations are over. Context means the necessary and/or sufficient conditions that allow an action to be performed.  It can also be a trigger.  Actions can be contiguous in sequence but have time between them, and yet still have the same superaction, because of the particulars of the action's description.  Actions can also be triggered by contexts, rather than have a single start and ending point. Simultaneous actions can be described as a triple of doubles, ((context 1, context 2), (action 1, action 2), (result 1, result 2)), which shows simultaneous execution of two actions in different contexts.  You can guess how this would extend to additional actions that execute simultaneously. -nj ps: Pseudocoding procedures developed for procedural software design should be of help here.  So all you programmers reading this should have some ideas to contribute.  Just remember, that I'm proposing a model that could be easily used to question oneself and to interview another.