...
The goal of this task is to review and perhaps change the type of data the user is sharing with others. The precondition is that one or more relationships have been previously established, and the desire to review or edit is generated either by curiosity, or by some recent behavior that a user might want to share or not share in some existing relationship. Because the user can see all of his/her own data here, the task may be performed multiple times per week. We expect people to be curious about their own data and how it appears to others. This activity can be learned by doing -- it just involves scrolling, clicking, zooming, and panning. Viewing is inherently very safe, and editing can be made more safe by including the option to undo actions.
TA Feedback.
This is a good start, but there are some big things missing. You don't actually discuss classes of users, just specific interviewees. Try to think about who your users are more holistically - right now they're sort of points along a 1D continuum.
You also don't seem to really get a good feel for what the tasks your users use to solve your problems, and instead you describe actions that your app will let users take. Don't forget that the next step is to make three separate designs - you shouldn't already have picked one. Think of task analysis as the analysis of tasks that need to be done to solve the problems.
Please also move your interview information to the GR1 page. I'd appreciate it if you made these changes, since we'll be working off this document for the whole rest of the project.