SKU Update Process

Guidelines for updating SKU standards, adding new codes, and contributing to the system.

Overview

The SKU standard is maintained in this repository. Changes to platform codes, system types, or guidance should be proposed here and reviewed by the platform team.

When to Change the Standard

Update the standard when:

• a new deployment platform needs a code
• a new system category needs a code
• naming rules are unclear or incomplete
• examples no longer reflect real usage
• validation guidance needs to change

Adding a New Platform Code

1. Check whether a suitable code already exists.
2. Update Platform Identifiers with the new code and notes.
3. Add at least one realistic example if the code changes how teams choose platforms.
4. Update any local tooling or CI validation used by the team.
5. Submit the change for review.

Adding a New System Type

1. Check whether an existing type already fits.
2. Update System Types with the new code and guidance.
3. Add or revise examples where needed.
4. Update any local tooling or CI validation used by the team.
5. Submit the change for review.

Review Checklist

• the new code is unique
• the code is necessary
• the description is specific enough for teams to apply consistently
• examples reflect realistic use
• related docs are updated

Contribution Workflow

1. Create a branch in this repo.
2. Update the relevant SKU docs.
3. Update any local tooling that enforces the standard.
4. Open a PR for review.