Human Influence Telemetry v0.4.0 — Normative Rubric Stabilization
Human Influence Telemetry v0.4.0 — Normative Rubric Stabilization
Summary
Version 0.4.0 is a breaking normative and data-contract release. It converts all 16 ambiguity classes in HIT-ARFR-001 into a synchronized public assessment contract.
Added
- evidence states for affirmative absence, formal presence, operational capability, observed exercise, and indeterminate records;
- explicit thresholds for
0,1,2, andIE; - dimension-specific Counsel, Judgment, Command, Correction, Repair, and Reform rules;
- Repair trigger states;
- separate institutional-record and assessment-packet integrity;
- deterministic overall Telemetry Integrity derivation;
- sampling, aggregation, actor-attribution, contradiction, evidence-reuse, and citation rules;
- canonical 0.4.0 schema, catalog, handbook, and synthetic assessment;
- 48 executable boundary fixtures covering
FR-01throughFR-16; - explicit migration dispositions for every historical public assessment;
- archived copies of the superseded 0.1.0 contract;
- breaking-change review, migration guide, and adjacent-system claim audit;
- ADR-0003 for chronological empirical-result versioning.
Compatibility
A 0.1.0 assessment does not conform automatically to 0.4.0. Migration is a fresh reassessment and must preserve the original file.
The four historical public assessments remain unchanged. Three are historical_version_bound. Cigna is deferred_locked_protocol. This release does not claim any 0.4.0 public-case finding.
Human protocol
Protocol HIT-IRP-CIGNA-001 remains locked under the 0.1.0 scorer contract. The prior planned v0.3.0 result label is superseded; the eventual result must use the next available repository version. Original submissions and the pre-adjudication result must still be published, passing or failing.
Research boundary
HIT remains Maturity Level 1. Version 0.4.0 does not establish:
- human inter-rater reliability;
- 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.pyThe validator covers the canonical contract, synthetic example, 48 boundary fixtures, historical case preservation, migration dispositions, protocol lock, adjacent-system claim audit, and synchronized metadata.