LeadRefinery — How the Platform Works

Caller-ID pool and reputation

Traced at commit ffe4e48 · libs/contracts/src/lib/did-pool.ts · libs/temporal/src/activities/{did-pool,dial-gate}.ts · libs/contracts/src/lib/breakers.ts

Summary

  1. A caller ID has five states: WARMING, ACTIVE, THROTTLED, QUARANTINED, RETIRED.
  2. A new number starts in WARMING. It dials a small, rising volume.
  3. The warm-up ramp is 10 business days. Nobody can shorten it.
  4. A number becomes ACTIVE only after the carrier confirms its registration.
  5. The platform throttles a number with degraded health. The platform quarantines a number that continues to degrade.
  6. A quarantined number returns to WARMING, never straight to ACTIVE.
  7. The platform checks reputation once each business day. The platform does not check reputation on each dial.
  8. This check refuses more dials than any other check in the gate.
A caller ID moves between five states. A new number starts in warming and dials a small rising volume over a ten-business-day ramp that cannot be shortened. It may only become active after the carrier confirms its registration. An active number with degraded health is throttled to reduced volume. A throttled number that keeps degrading is quarantined, because throttling did not save it. A quarantined number whose label is cleared returns to warming, not to active. Any number can be retired. Reputation is swept once each business day, not on each dial, and too many quarantines in 24 hours opens a platform breaker.
Workflow 1 of 2 — the states. Two transitions matter most: escalate when reduced volume fails, and re-warm instead of restore.

Workflow 1 — the states

The five states

  1. WARMING — the number dials a small daily volume. The volume rises across the ramp.
  2. ACTIVE — the number dials at the full daily cap.
  3. THROTTLED — the number dials a reduced volume. Its health has degraded.
  4. QUARANTINED — the number does not dial. The number rests.
  5. RETIRED — the number leaves the pool. It does not return.

The transitions

  1. WARMING to ACTIVE — the ramp is complete and the carrier has confirmed the registration.
  2. ACTIVE to THROTTLED — health degrades. The platform reduces volume before it stops the number.
  3. THROTTLED to QUARANTINED — health continues to degrade. Reduced volume did not save the number.
  4. QUARANTINED to WARMING — the carrier clears the label. The number restarts the ramp.
  5. Any state to RETIRED — the number leaves the pool.

Read the two asymmetries. Escalation says that reduced volume did not work. The platform therefore stops the number. A number that stays throttled loses reputation slowly. The platform stops it instead. A cleared label does not restore trust. A number returned to full volume earns the same label again within days. A second label is harder to clear than the first.

Registration

  1. Registration with the carrier is a precondition for ACTIVE.
  2. It is not an administrative formality.
  3. An unregistered number that dials at volume matches the profile the carrier models detect.
  4. Registration afterwards does not remove that label.

Workflow 2 — the daily reputation sweep

Once each business day the platform asks the carrier for the reputation of every number in the pool, records a risk band and sub-scores, and those readings drive the state changes. The platform does not check reputation when it places a call, because a vendor lookup on the dial path would add a network call to every call. A number therefore carries yesterday's reading into today, and if the vendor entitlement is absent the platform skips the sweep rather than guessing. Two pool-level alarms watch the results: too many quarantines in twenty-four hours, and too large a share of the pool quarantined across seven days.
Workflow 2 of 2 — the sweep. Once a day for the whole pool, and never on the dial path.

What the sweep does

  1. The platform sweeps reputation once each business day.
  2. The platform does not check reputation on each dial.
  3. A per-dial check would add a vendor network call to every call the platform makes.
  4. A number therefore carries the label of yesterday into today.
  5. If the vendor entitlement is absent, the platform skips the sweep. The platform does not estimate the value.

Pool-level alarms

  1. The platform counts quarantines in a 24-hour window.
  2. Too many quarantines in that window opens a breaker.
  3. That pattern is the signature of a reputation collapse across the pool.
  4. The breaker stops the platform. It does not stop one number.
  5. The platform also watches the share of the pool quarantined across 7 days.

The dial gate — check 11 asks this pool for a number, and refuses 354,514 dials when none is free.