Define product stage vocabulary and repository pinning policy

[Scriptception]

Problem

Terms such as in development and shipping are used inconsistently, and there is no documented rule for which repositories occupy the limited organization profile pins.

User outcome

Visitors can interpret product status consistently and the most useful supported repositories remain easy to find.

Scope

• Define a small public stage vocabulary with evidence requirements and transition ownership.
• Define criteria and review cadence for up to six pinned repositories.
• Record stage and pin decisions as publication-safe manifest data or settings documentation.
• Describe treatment of archived, internal, experimental, and documentation-only repositories.

Non-goals

• Publishing confidential prioritization or portfolio scores.
• Using commit recency as the sole stage signal.

Acceptance criteria

• Each stage has a plain-language meaning and required evidence.
• Every promoted product has one valid stage.
• Pinned repository choices have an owner and scheduled review.
• Archived and non-public projects cannot be pinned by the generation workflow.

Validation

• Apply the vocabulary to all currently promoted products and resolve ambiguity.
• Review the public organization profile in signed-out and member views.

Relationships

• Feeds canonical manifest and profile generation.
• Paired with website catalog reconciliation.