StockAcceptance

Join-dependent (downstream). A stock acceptance carries only security_id and no discriminator; the security family is fixed at issuance, not on the acceptance record. An importer must resolve issuance_type from the joined StockIssuance first (the two-pass requirement, §2.2) before it can decide where the acceptance lands. StockIssuanceType has exactly two values — RSA and FOUNDERS_STOCK — which the two variants partition exhaustively.

date is the only acceptance-specific field. For an RSA issuance the accepted security is a Carta RestrictedStockAward, which exposes stakeholderAcceptanceDate ($ref Iso8601CompleteCalendarDate); the OCF acceptance date is folded onto that security via the per-variant target map.

Default (FOUNDERS_STOCK) has only an identity home. Non-RSA stock maps to a Carta Certificate, and Certificate has no stakeholderAcceptanceDate (its only date fields are issueDate / canceledDate / lastModifiedDatetime). The acceptance date and standalone event therefore remain unmappable (primary_targets: null, date → null), but security_id is still preserved on CertificateTransactionItem.securityId and Certificate.securityId so the referenced stock is not lost.

security_id is the join key (route_by_property.lookup_by.key) and is also copied to the resolved Carta identity: RsaTransactionItem.securityId plus RestrictedStockAward.securityId for RSA, or CertificateTransactionItem.securityId plus Certificate.securityId for founders' stock.

id, comments, object_type → unmappable. Standard OCF object scaffolding: id is OCF's own object identifier (Carta assigns server-side ids) and object_type is OCF's discriminator constant (TX_STOCK_ACCEPTANCE), both ocf-internal; comments is free-text with no Carta slot (no-equivalent).