Human Influence Telemetry v0.5.0 — Executable Assessment Conformance
Human Influence Telemetry v0.5.0 — Executable Assessment Conformance
Summary
Version 0.5.0 is an implementation release. It adds reusable complete-record conformance for the stable 0.4.0 normative assessment contract.
The repository and conformance engine advance to 0.5.0. The specification, assessment schema, dimension catalog, handbook, and scoring semantics remain 0.4.0.
Added
- reusable semantic validation for complete HIT assessment records;
- actor and evidence-claim reference checks;
- actor-to-claim attribution reciprocity;
- finding and evidence-state consistency checks;
- Repair-trigger and Telemetry Integrity derivation checks;
- aggregation-scope and citation-precision checks;
- stable machine-facing error codes;
- deterministic text and JSON reports;
- one valid and fifteen invalid complete-record vectors;
- machine-readable compatibility metadata;
- non-mutating migration planning for historical
0.1.0records; - public CLI commands and smoke tests;
- package-oriented
src/architecture.
Commands
python -m src conformance --all
python -m src conformance --path assessment.json
python -m src migration-plan --path historical-assessment.jsonCompatibility
A conforming 0.4.0 assessment remains compatible with release 0.5.0. No normative reassessment is required merely because the implementation version changed.
Historical 0.1.0 assessments remain historical-validation-only artifacts. Automatic conversion to 0.4.0 is prohibited. A migration plan requires fresh reassessment and preservation of the original file.
Preserved boundaries
Release 0.5.0 does not modify:
- specification, schema, catalog, or handbook
0.4.0; - protocol
HIT-IRP-CIGNA-001; - the frozen Cigna packet;
- scorer eligibility, threshold, or critical-disagreement rules;
- historical public case findings;
- H3 or Maturity Level 1.
No 0.4.0 public-case finding is claimed.
Research boundary
Release 0.5.0 does not establish:
- human inter-rater reliability;
- evidence truth or completeness;
- field effectiveness;
- causal validity;
- legal compliance or standards conformity;
- certification;
- independent adoption;
- runtime enforcement;
- signed-receipt interoperability;
- policy-pack harmonization;
- evidence portability.
Validation
Before tagging, the exact release commit must pass:
python scripts/check_fixture_format.py
python scripts/validate.py
python -m src conformance --all
python scripts/validate_v050_cli.pyThe release validator checks repository metadata, contract preservation, historical case hashes, protocol locks, compatibility metadata, complete-record conformance artifacts, and release documentation.