ENTITY v3.3.0 released - independent implementers and reviewers wanted

[blackmore-technology-group]

ENTITY v3.3.0 is now published from protected main.

Release: https://github.com/blackmore-technology-group/ENTITY/releases/tag/v3.3.0

Protected release commit: 9c79f987207592cb6791e1a8956f23351cdfb2d3 (GitHub-signed and verified)

What v3.3 adds

v3.3 formalizes the bridge between external-world claims and authoritative ENTITY state:

Reality -> Observation -> Claim -> Evidence -> Attestation -> Verification -> Authoritative ENTITY State -> Right -> Usage -> Economic Consequence

It adds first-class Evidence Objects, typed claim states, scoped attestation authority, external reality anchors, contestability/supersession, and evidence-backed causal economic attribution.

The central boundary is deliberate:

ENTITY does not make reality indisputable. It makes claims about reality attributable, evidentiary, contestable, machine-verifiable and economically traceable.

Cryptographic verification, protocol verification and reality/evidence verification remain separate.

Release evidence

• complete regression: 144/144 PASS
• targeted v3.3 suite: 16/16 PASS
• sealed v3.3 reality vectors: 20/20 PASS (10 valid / 10 invalid)
• canonical sealed kit SHA-256: f8b39ee01fb7346f33a57530e925b545d2bf9a770c7ec60724e28a4971d55a46
• schema SHA-256: 6e1c7e621e0aa84627e009febf8999503b7a61f92627b885ed10a19f2ef7d767
• deterministic result SHA-256: 82bd1f1fb328edd37a26d8ea60ede5a599c7d9af5027bffd73b9e52843b5a51d
• release overlay: 22/22 files verified
• fresh-clone release gate: PASS
• protected GitHub checks / CodeQL: PASS

We want criticism and independent reproduction

BTG already has controlled native ENTITY baselines in Rust, TypeScript, C#, Go, Swift and Java for the v3.2 campaign. Those are useful cross-language evidence, but they are not independent third-party validation.

The next question is harder:

Can someone outside BTG independently reproduce ENTITY semantics from the public material without using BTG implementation code?

You do not have to implement the whole protocol to participate.

Small entry tasks

• Linux v3.3 reproduction: [GOOD FIRST ISSUE][FROZEN BASELINE] Reproduce ENTITY v3.4.2's inherited sealed Global Passport campaign on Linux #20
• macOS v3.3 reproduction: [GOOD FIRST ISSUE][FROZEN BASELINE] Reproduce ENTITY v3.4.2's inherited sealed Global Passport campaign on macOS #21
• minimal Evidence Object example: [GOOD FIRST ISSUE] Add a minimal v3.4.3 Evidence Object and claim-transition example #22
• claim-state ambiguity review: [REVIEW][HELP WANTED] Review ENTITY v3.4.3 claim-state transitions for ambiguity or unsafe escalation #23
• external-anchor threat model: [THREAT MODEL][HELP WANTED] Challenge ENTITY v3.4.3's external reality-anchor boundary #24
• verifier benchmark: [GOOD FIRST ISSUE][FROZEN BENCHMARK] Benchmark ENTITY v3.4.2's inherited 24-vector Global Passport verifier #25
• fresh-clone onboarding audit: [GOOD FIRST ISSUE] Audit the ENTITY v3.4.3 onboarding path from a fresh clone #26
• causal-attribution counterexamples: [REVIEW][HELP WANTED] Find false-causality counterexamples in ENTITY v3.4.2 economic attribution #28

Narrow independent implementation

• independent v3.3 reality-vector classifier: [INTEROP][HELP WANTED][FROZEN TARGET] Independently implement the sealed Global Passport classifier carried by ENTITY v3.4.2 #27

The full graduated path is here:
https://github.com/blackmore-technology-group/ENTITY/blob/main/docs/INTEROPERABILITY_CHALLENGE.md

Engineering evidence and claim boundaries:
https://github.com/blackmore-technology-group/ENTITY/blob/main/docs/ENGINEERING_EVIDENCE.md

Start here if you are new to ENTITY:
https://github.com/blackmore-technology-group/ENTITY/blob/main/START_HERE.md

A failing vector, ambiguous rule, portability problem or clean counterexample is useful. The goal is to make the protocol survive independent scrutiny, not to collect endorsements.