Unauthorized Feature Implementation

A subject introduces functionality into an organizational codebase that falls outside approved requirements, defined scope, or organisational intent. This includes the addition of features, behaviors, or integrations that have not been authorized through product, security, or governance decision-making processes.

The infringement is defined by the presence of code that should not exist within the system, regardless of how it was introduced or whether it passed through standard development workflows. In some cases, such changes may appear technically valid or beneficial, but still violate organizational control, compliance requirements, or strategic direction.