Consistent Hashing Ring Visualizer implementation

Binding contract

This record describes what an executable surface must bind and validate. It does not claim that a public calculator, package, or production route is deployed.

Record owner

Guth Instruments

Lifecycle

verified-clean

Evidence ID

t6-110

Effect

Computation or source lookup only

Input and validation requirements

The specified calculation is undefined for ring_size = 0 and requires explicit input rejection. Additionally, the specification does not define the hash function details or whether clockwise corresponds to increasing or decreasing numeric positions; the latter changes the mapping for the same valid input.

Required corrections

No binding erratum is attached to this unique-name record. Implementers must still preserve the declared units, domain, and failure behavior.

Inspectable interface fixture

The sample below is evidence for interface and validation tests, not a production implementation.

{
  "inputs": {
    "hash_function": "H(s) = sum of UTF-8 byte values",
    "ring_size": 16,
    "nodes": [
      "A",
      "B",
      "C"
    ],
    "keys": [
      "alpha",
      "beta",
      "gamma"
    ],
    "topology_change": "none"
  },
  "expected_outputs": {
    "node_positions": {
      "A": 1,
      "B": 2,
      "C": 3
    },
    "key_positions": {
      "alpha": 6,
      "beta": 12,
      "gamma": 3
    },
    "key_to_node": {
      "alpha": "A",
      "beta": "A",
      "gamma": "C"
    },
    "rebalance_delta": {
      "moved_keys": 0,
      "moved_fraction": 0
    }
  },
  "working": "Node positions: H(A)=65, 65 mod 16=1; H(B)=66, 66 mod 16=2; H(C)=67, 67 mod 16=3. Key positions: H(alpha)=97+108+112+104+97=518, 518 mod 16=6; H(beta)=98+101+116+97=412, 412 mod 16=12; H(gamma)=103+97+109+109+97=515, 515 mod 16=3. Clockwise ownership: alpha at 6 passes 7..15, wraps to A at 1; beta at 12 also wraps to A at 1; gamma is exactly at C's position 3, so it maps to C. No topology change means 0 of 3 keys move, so moved fraction=0/3=0."
}

Other records

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• VERIFIED_LEDGER.json
• evidence-tranche6/tranche6-results.json