StockLegendTemplate
objects/StockLegendTemplate.mapping.md
Use the issue button on this page or on an individual field to start the auditable mapping discussion.
Notes / open questions
These notes are rendered from the mapping document and remain part of the review record.
Carta has no stock-legend object, legend text field, or legend ID relationship. The entire OCF StockLegendTemplate object and StockIssuance.stock_legend_ids link are therefore no-equivalent.
The pinned Carta v1alpha1 bundle used by this mapping has no standalone legend object, legend text field, or legend ID relationship. The OCF object and StockIssuance.stock_legend_ids therefore remain no-equivalent for this target surface.
Carta's separate Draft Issuer API accepts a certificate-level legend string (the public example uses Default), but its semantics and read-back behavior are not defined by this bundle. Do not treat it as a lossless target for OCF name/text without that contract.
name and text remain unmappable here; id, comments, and object_type are OCF scaffolding. Preserve the template in an extension or sidecar if legend fidelity is required.