While I understand what you mean, shouldn’t the public APIs still be decorated with @editable regardless? If the the public field such Intensity is a computed field (get/set proxy) that reads and mutates the private stored @editable property, shouldn’t that information still bubble up to the end user to see? In case of the @editable effect at least, this wouldn’t hurt anyone.