The bulk update request #251 is active.

create alias permanent_chastity (0) -> permanent_chastity_device (563)
create implication permanent_chastity_device (563) -> chastity_device (22272)
create implication key_disposal (117) -> permanent_chastity_device (563)
create implication sealed_chastity_device (8) -> permanent_chastity_device (563)
create alias no_key (0) -> key_disposal (117)
create alias key_disposed_of (0) -> key_disposal (117)
create alias disposed_key (0) -> key_disposal (117)
create alias disposed_of_key (0) -> key_disposal (117)
create alias key_destruction (0) -> key_disposal (117)

Reason: Continuation of the discussion here and the unalias request here.

Now that permanent_chastity is no longer aliased to chastity, a better tag relationship structure can be created.
To re-iterate a previous point made, chastity can be considered permanent if at least one of these three things is true:
1. The permanence of chastity is mentioned through dialogue
2. A key is either visibly destroyed, or in the process of being destroyed
3. The device itself is visibly unremovable. For example, a keyhole is sealed.

As such, both key_disposal and sealed_chastity_device fall under permanent chastity and thus can imply it.

EDIT: The bulk update request #251 (forum #295948) has been approved by @Millcore.

The bulk update request #251 (forum #295948) has been approved by @Millcore.

Ehm I think key disposal can be used for more situations than chastity. That implication should be removed.