EquityCompensationExercise

Join-dependent. Resolve compensation_type by joining security_id to the related EquityCompensationIssuance; route options to OptionExerciseTransaction. RSU and SAR exercise targets are absent from the June 22 bundle.

RSUs route through a different source object. An RSU settlement is modeled by EquityCompensationRelease, which maps to Carta's RSU settlement objects; the Rsu variant is null only in this exercise mapping because Carta has no RSU exercise target.

Mapped fields. date, quantity, and resulting_security_ids map to the resolved exercise family; security_id anchors the parent transaction/grant. resulting_security_ids is computed onto certificate lineage because Carta's transaction-level result pointer is scalar.

Unmapped fields. id, comments, object_type, and consideration_text have no equivalent Carta field; Carta-only exercise metadata remains unpopulated.

Carta OptionExercise needs clarification. The pinned Carta bundle defines OptionExercise as a top-level object with request/workflow-oriented fields such as state (PENDING, COMPLETE, CANCELED), tax withholding, and money movement. This mapping instead routes the realized OCF exercise to the nested OptionExerciseTransaction (and related Exercise, grant, and certificate structures), which is why the inverse explorer currently labels OptionExercise as having no standalone OCF record. That may be correct if OptionExercise is a request/workflow object distinct from a completed exercise transaction, but the target schema and routing documentation also describe an option exercise as producing an OptionExercise record. Carta should clarify the lifecycle and intended data/API role of OptionExercise versus OptionExerciseTransaction/Exercise, and whether a completed OCF EquityCompensationExercise should populate OptionExercise in addition to the realized transaction structures.