status definitions.

Consistent lifecycle labels make it clear whether a component is only planned, already implemented, under qualification, deployed, deprecated or retired.

planned

Architecture or product scope is defined, but implementation should not be assumed to exist.

implemented

Code exists in the project, but production deployment and operational readiness are not implied.

qualifying

The implementation is undergoing integration, security, deployment or operational checks before it can be treated as canonical.

deployed

A qualified release is available on a named network with verifiable deployment information.

deprecated & retired

Deprecated components remain available for compatibility but should not receive new integrations. Retired components are no longer supported for active use.