Version History

Methodology Changelog

This page provides a public, versioned history of methodology changes so readers can trace how scoring and publication rules evolve over time.

Updated: 2026-04-04 | Current active version: v1.2.

Verification Summary

What to check for Methodology Changelog

This page provides a concise, evidence-first guide for Methodology Changelog. Focus: provide actionable verification steps and real-world checks so procurement decisions are based on repeatable evidence, not promotional claims. Run a short pilot in a test account (3 sessions), capture browser versions, proxy settings, and checkout eligibility responses. Document failures with timestamps and screenshots and use them to decide whether to proceed with annual commitments. Include a brief case note at the end of each pilot with a go/no-go recommendation. Share the evidence pack with procurement and ops for reproducible validation.

Current Version

v1.2 (Active)

  • Profile integrity weight adjusted to 38% to reflect repeated-session risk impact.
  • Worker parity checks promoted from advisory to required in critical flows.
  • Connection hygiene blockers clarified for persistent DNS and WebRTC mismatch.

Release History

Version Timeline

Version Date Change summary Impact note
v1.2 2026-04-04 Reliability weight rebalance and worker parity hard requirement Raises threshold for annual-plan recommendations in unstable setups
v1.1 2026-02-18 Added explicit no-buy criteria and correction visibility protocol Improved traceability for procurement pauses and reversals
v1.0 2025-12-12 Initial weighted scoring model and publication guardrails Established baseline for evidence-first decision framework

Change Governance Rules

  • Any scoring change requires version bump and public impact note.
  • Any new blocker requires migration guidance for current readers.
  • Material fixes are mirrored in metadata and benchmark references.

Future Change Queue

  • v1.3 candidate: stronger degraded-proxy resilience measurements.
  • v1.3 candidate: explicit confidence score for low-volume pilot data.
  • v1.3 candidate: severity gradient for governance drift under scale.

How To Audit Updates

Three-Step Traceability Workflow

Step 1: review current methodology version and weights.
Step 2: read version impact notes in this changelog.
Step 3: confirm benchmark report version tags before using rankings operationally.