Aglet

Investigate an unexpected API enum value

Investigation should show whether an unknown value is new, malformed, or misread. Build known and unfamiliar fixtures, trace the parser to every branch, and compare stored representation with action. Keep response version, mapping code, and source data as separate hypotheses.

Build a useful investigation brief

  1. Build enum fixtures

    Create every documented value, one future-looking value, a misspelled token, a null or absent field, and a value that would control an irreversible action. Record expected parse, state, and side effect before running.

  2. Trace exhaustive branches

    Follow raw bytes through decoder, enum conversion, fallback, persistence, UI, and action guard. Capture the first unknown branch and whether the raw token survives. Record client and response versions without copying unrelated payloads.

  3. Vary the source boundary

    Change only token spelling, response version, parser table, field presence, or action context. Compare a safe unsupported state with a familiar default. If the source does not define the value, state the missing contract evidence and stop.

What to carry forward

The investigation is ready when each fixture shows raw token, parser branch, stored state, and side-effect decision. Recommend a narrow compatibility or evidence change. Keep the meaning of a genuinely new value unresolved until its owner confirms it.

Technical background: Project documentation on GitHub.

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