I'm currently writing a design to add the possibility to mark a field or attribute for an entity as read-only in preparation for imminent removal. The idea is that, once the field has been thus marked and the change has propagated everywhere in production, we can run a job against our database to remove that field from the data permanently.
What is the best descriptive short term for this state? Currently, we're thinking of calling such fields "deprecated". To me, however, this often just means "strongly discouraged" - you're not supposed to use it, but you might end up doing so anyway (vid. the Java
@Deprecated annotation). Is there a stronger term for this that implies that the field will in fact never be written to again? I've thought of
defunct so far.