answer_change_message.json

{  
  "client_id": 11827435,
  "context": {
    "survey_id": 1,
    "question": {
      "name": "filling_out_for_myself",
      "metadata": {
        "type": "locally-stored"
      }
    }
  },
  "answer": {
    "answered_at": "2018-02-06T18:15:25Z",
    "responses": [    
      "true"
    ]
  }
}

This works for me. The only thing I -might- tweak is nesting "survey_id" and "question" keys under a "context"

Making it for single answers only makes sense. I wonder if we want to have different options for the circumstance that has led to you getting this payload

action: "answer_change"
initiated_by: "user|cx|migration" // or client12312 == the current kids client mom?

or something. Maybe that's premature.

Sam - I think that would be awesome, but it's a feature we'd have to build - there's no notion of what caused a change right now anywhere near the code that publishes this message.

I guess we could depend on the name of the rabbit stream to know it is an answer update.