> It looks like if you use both checkedLink and valueLink you're gonna have a bad time. Can we invariant() that if a checkedLink is present you cannot provide a valueLink?

Of course :+1: 

> Also, does this mean that onChange() is ambiguous? What's changing, checked or value?

Kind of, it depends on the type of the input, `checked` for "checkbox", `value` for everything else.
Is that a problem? If I read the HTML spec for checkboxes correctly, `value` is not intended to be changed and all other inputs (except `radiobox`, but everything that applies to checkboxes should apply to them as well) do not have a `checked` attribute, so it would be unambiguous.
Also, changing a checkboxes 'checked' attribute [fires a `change` event](http://www.w3.org/html/wg/drafts/html/CR/forms.html#checkbox-state-(type=checkbox)) in the browser, so keeping the name `onChange` would be in line with the spec.