The explicit identity transition: end-dates the current record and mints a successor with the supplied facts, linked through previousId/nextId. The target must be the chain's current record; advancing a superseded record returns 409 ResourceConflict. The successor inherits the chain's owner and subject, starts every verification lane at NotStarted, and becomes the source for refreshed downstream projections such as Auto W-9s. The successor type must equal the predecessor's immutable chain type. effectiveDate defaults to now, or to the predecessor's startDate plus 1 ms when needed for a subject-scoped chain. It cannot precede the predecessor's startDate; a client-supplied date cannot be in the future and, for a subject-scoped chain, must be strictly later than the predecessor's startDate. The id is resolved with the same authorized-lane and primary-wins semantics as GET, and the resolved owner kind is retained through the transition. Idempotent via Idempotency-Key. Fires ComplianceEntity.Inactivated on the predecessor and ComplianceEntity.Evolved on the successor.

Requires a session with recent MFA step-up for HighRiskWriteAction. If step-up is missing or expired, this operation returns 403 StepUpMfaRequired; create and verify an MFA challenge at /v3/platform/mfa-challenges with requiredFor: "HighRiskWriteAction", then retry.