Fingerprint ↔ proxy alignment

What it's for

An exit in New York and a clock set to Europe/London is one of the most trivially-detected anti-detect mistakes there is — and if several Accounts share the same mismatch, it's a fleet-wide tell. Alignment is how Umbra keeps an Account's device signature agreeing with the place its exit comes out. It isn't a setting you switch on; it's something Umbra does for every Account that has an exit, and something you can re-run in one click when it drifts.

What "aligned" means

To align an Account is to copy its exit's tested region — the exact time zone, the latitude and longitude, the country — onto the Account's Fingerprint. The time zone is copied verbatim, which is what makes a later mismatch definitive rather than approximate: if the clocks differ at all, the Account is un-aligned, not merely close.

When alignment happens

Alignment runs at two moments, both automatic, and only when the exit actually carries a region to copy.

Because launch re-aligns, an Account that drifted between sessions is quietly corrected the next time you open it — but drift you haven't opened yet is still there, which is why drop-day readiness checks for it before a sale.

Only a tested exit has a region to copy

There is nothing to align to until the exit has been tested. Testing is where Umbra reads back where an exit comes out and writes that region onto the exit record; a fresh exit knows none of it.

Drift, and the one-click realign

Alignment is a snapshot taken at assign and launch, not a live binding — a manual Fingerprint edit, a synced identity, or an import can leave an Account out of step with its exit. When that happens the fix is exact and one click away.

The realign itself is the PROFILE_ALIGN handler: it runs the same copy the assign and launch paths run, over the Accounts you point it at.

What coherence checks — and what it doesn't

The drift check judges the time zone only. That's a deliberate narrowing, not an oversight.