[REVIEW][HELP WANTED] Review ENTITY v3.4.2 claim-state transitions for ambiguity or unsafe escalation

[blackmore-technology-group]

Goal

Review the current ENTITY v3.4.2 claim-state taxonomy and transition semantics as a specification/interoperability exercise, then identify any ambiguous or unsafe escalation path.

Current release: https://github.com/blackmore-technology-group/ENTITY/releases/tag/v3.4.2

Relevant claim states include:

OBSERVED, ASSERTED, INFERRED, ATTESTED, EXTERNALLY_VERIFIED, ADJUDICATED, DISPUTED, REVOKED, UNKNOWN.

Questions to test

Examples of useful review questions:

• Is it clear which transitions require evidence?
• Can a weaker state be made to look stronger without a governed transition?
• Can Global Passport/profile composition accidentally strengthen a claim state?
• Can BTDU topology or derived context accidentally strengthen a claim state?
• Are DISPUTED and REVOKED distinguishable enough for independent implementers?
• Is supersession/history preservation unambiguous?
• Could two reasonable independent implementations interpret the same transition differently?

Scope

This is review-first. You do not need to redesign the taxonomy or implement ENTITY as a whole.

Useful outputs include:

• one concrete ambiguous transition;
• a counterexample;
• a small transition table;
• a clarification PR;
• an additional valid/invalid vector;
• or a short interoperability review explaining why the selected transition appears unambiguous.

Use the v3.4.2 tag, cite the exact source/specification material reviewed, and explain the interoperability or security consequence of any ambiguity you identify.

A reproducible failure or ambiguity is useful evidence.