Aglet

Learn from recurring status label inconsistency

Recurring status inconsistency shows that state meaning is being reauthored at multiple layers. Compare episodes and preserve one source of meaning plus the presentation contexts that must stay aligned.

Keep the lesson for the next incident

  1. Compare divergent mappings

    Align canonical value, record type, page, label, qualifier, tone, filter, action, and transition across episodes. Separate intentional domain-specific terms from accidental synonyms.

  2. Preserve the vocabulary contract

    Document the user-facing meaning, allowed label, tone, filter value, and action boundary for each state. Include qualifiers needed to distinguish similar states without inventing new categories.

  3. Define recurrence recognition

    Trigger review after state constants, presenters, helpers, filters, navigation, or status styles change. Name the contexts and transitions that must be compared before trusting the vocabulary.

What to carry forward

The lesson should preserve one canonical vocabulary contract and a recurrence rule for status changes. Treat consistency as provisional until later transitions and contexts continue to communicate the same underlying state. Preserve a canonical vocabulary map with labels, qualifiers, tones, filters, and actions, and review it after state, presenter, navigation, or copy changes. Keep the map close to the state source and include examples of similar states that need qualifiers.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow