[GOOD FIRST ISSUE] Add a minimal v3.4.3 Evidence Object and claim-transition example

[blackmore-technology-group]

Goal

Add one small, runnable/documented example showing how the current ENTITY v3.4.3 release uses the evidence/claim-state model without representing a supported claim as objective truth.

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

Version boundary: ENTITY v3.4.3 is current; BTDU remains component 3.4.2 unchanged. Historical sealed v3.4.2 evidence is not modified by this example task.

This is intentionally bounded. No new protocol feature is required.

Suggested example

A document-backed claim is enough:

1. create or describe an ENTITY evidence object;
2. bind it to an evidence-backed claim;
3. show an ASSERTED → EXTERNALLY_VERIFIED transition with governed evidence where supported by the current public model;
4. show one invalid variant that must fail, such as missing evidence or an invalid truth-boundary transition;
5. where useful, show how that evidence context is carried into a Global Passport rather than silently upgraded.

Boundary to preserve

• signature/record validity proves integrity or attribution, not objective external truth;
• stronger claim state requires governed evidence;
• a valid Global Passport does not make external-world assertions objectively true;
• provenance is not automatically ownership;
• history is superseded rather than silently rewritten;
• BTDU relationships do not silently create authority or rights.

Target

Use the public v3.4.3 tag and identify the exact files/schemas used.

Completion evidence

Open a concise PR under examples/ or another justified documentation location with a command/test proving the valid example passes and the invalid example fails.

Keep this narrow. A small understandable example is more valuable than a broad redesign.