ENTITY Documentation Portal
Developer manual · ENTITY v3.4.3 · release evidence

Release Engineering

A release is an evidence target. Once published, qualification may add separately hashed evidence about it, but release-critical bytes and historical claims must not be silently rewritten.

Current v3.4.3 release identity

ArtifactValue
Supported releasev3.4.3
Signed tag objecte92b34221838fc09d7e72cc2e7a7f19c53a2b5f7
Release commit528b70aabd05b1e930b77e4933f157731e47274f
Release treef13e42f515dcc4cd985e9b832e0ecfec416ce423
BTDU component3.4.2 unchanged

The annotated v3.4.3 tag is signature-verified and points to the exact release commit above.

Current qualification

Predecessor and inherited evidence

v3.4.3 is a bounded remediation release based on immutable v3.4.2 predecessor commit 6dfa3d6cc738d9369cf092d2782676bf4f2a46e4. v3.4.2 remains historical evidence. Compiled Rust clean-room/conformance qualification and real-world BTDU training qualification are inherited into v3.4.3 only because their qualified scope was unchanged; those records were not re-executed as v3.4.3 runs.

Freeze rule

Post-release testing may add evidence; it may not rewrite the release artifact or relabel historical evidence. If qualification changes model weights, source, executables, schemas, protocol behavior or other release-critical hashed material, the modified system becomes a subsequent candidate/release.

Promotion sequence

  1. Qualify candidate and capture exact commit/tree/manifests.
  2. Run required repository/security/conformance checks.
  3. Merge through the intended protected/review path.
  4. Create the signed release tag and GitHub Release.
  5. Publish release-origin evidence/sidecars.
  6. Mark the prior release superseded without rewriting its tag/history.
  7. Continue post-release qualification as separately hashed evidence.

Supersession

Supersession changes current support status, not historical bytes. v3.4.2 remains available as the predecessor evidence target and for reproducing qualification that was actually performed against it; v3.4.3 is the current supported ENTITY runtime.

Evidence naming rule

Every qualification record should state whether it is executed on v3.4.3, inherited unchanged-scope from v3.4.2, Protocol 1.0 conformance, or external/independent evidence. Do not collapse those classes into one “PASS.”