Each organisation chooses which instrument templates it offers
Instrument templates, the reusable product shapes an asset is issued from, are offered for issuance only when an organisation publishes them.
An organisation now decides which instrument templates it offers for issuance. Equity, Bond, and Stablecoin start published, every other DALP Library template starts unpublished, and one switch changes that in either direction. Publish the templates you issue from before your next issuance after the upgrade.
What changed
An instrument templateAn Instrument Template lets an issuer configure a new instrument from an approved shape, instead of re-deciding what it records, does, and permits each time.Read the concept is the reusable product shape an asset is issued from. Until now every organisation saw all thirty-three DALP Library templates in Issue new asset, and most organisations issue two or three instrument types.
Each template now has one of three states in an organisation: draft, published, or unpublished. Issue new asset lists the templates the organisation has published and not hidden. The state belongs to the organisation, so publishing a DALP Library template in one organisation changes nothing in another.
Publishing and unpublishing are reversible without limit. An administrator, system manager, or asset designer uses the "Published" switch on the template's detail page, or the "Publish" and "Unpublish" buttons in the instrument templates table. An organisation's own draft still passes the readiness check once, for its first publish. Unpublishing never returns a template to draft.
What an existing organisation sees after the upgrade
The starting state applies to every organisation, existing and new. We chose one rule for all organisations over a per-organisation backfill, so the same three templates are the starting point everywhere.
- Issue new asset lists Equity, Bond, and Stablecoin until someone publishes more.
- Both DALP Library structures, the dual-class share and the convertible note, start unpublished, also in an organisation that published their templates. Issue new asset does not list them until someone publishes each structure.
- A token creation or an issuance run that names an unpublished template is rejected, through the API, the SDK, and the CLI. The answer is a
409that is not retryable:TOKEN_CREATE_TEMPLATE_UNPUBLISHEDfor a token creation andTOKEN_ISSUANCE_RUN_TEMPLATE_UNPUBLISHEDfor an issuance run. The frozen v1 token creation route rejects the same request with its existing422INPUT_VALIDATION_FAILED(DALP-0316). Publish the template, then send the request again. - An issuance run the platform accepted while its template was published still completes.
Assets already issued are unaffected. An asset issued from a template that is now unpublished keeps its page, its asset class, its sidebar entry, and its operations.
The remedy is one action per template: publish it in the Console or call the publish endpoint.
curl -X PUT "https://your-instance.example.com/api/v2/settings/asset-type-templates/system-real-estate/publish" \
-H "X-Api-Key: sm_dalp_..."Issue new asset says what to do when the list is short
When an organisation offers no template, the first step shows "No instrument templates are published" in place of a list. An account that can manage templates gets a link to the instrument templates overview. Any other account is told to ask an asset designer or administrator. When templates are listed, an account that can manage templates also sees a line under the list that links to the overview, where more can be published.
Structures have their own published state
An instrument structure groups two or more templates into one multi-class instrument. Each organisation now publishes or unpublishes a structure as it does a template, and Issue new asset offers a structure only when the structure and every template in it are published and none of them is hidden. A structure an organisation creates starts published; a DALP Library structure starts unpublished.
A single publish makes a structure issuable. Publishing it also publishes its unpublished templates, after the Console lists them and the user confirms. Unpublishing it leaves its templates published. A template that a published structure uses cannot be unpublished until the structure is, so nobody can take a structure out of issuance by accident through one of its templates. The disabled control names the structures, and the API answers 409 ASSET_TYPE_TEMPLATE_USED_BY_PUBLISHED_STRUCTURE with their ids and names in data.structures.
The "Structures" tab of Instrument templates is now a table like the templates table, with a "Status" column, a filter on it, and rows that expand to each class and its template's state. Issue new asset lists a structure only once it and every template in it are published and none of those templates is hidden; publishing happens on that tab. An issuance run on an unpublished structure answers the non-retryable 409 TOKEN_ISSUANCE_RUN_STRUCTURE_UNPUBLISHED; a run accepted before the structure was unpublished still completes.
The designer filters policy templates by jurisdiction
The compliance step of the instrument template designer now opens filtered to the template's jurisdiction. Pick the country in the "Jurisdiction" field at the top of the step. The platform stores it as the default value of the template's jurisdiction metadata field when that field is a country field, and otherwise of issuerJurisdiction, adding that field as a country field when it does not exist and jurisdiction when the template has neither. With a default of Germany, the step lists policy templates that name Germany, policy templates that name a group containing it such as the EU, and global policy templates. An "Applies to Germany" chip turns the filter off and on again, and stays visible either way. The filter never changes a policy template that is already selected. A template with no default opens the step unfiltered.
Both template overviews are tables
Instrument templates and policy templates were lists of cards. Both are now tables with search, sorting, filters, and pagination, and each row expands to show what the card showed: the description and required features for an instrument template, the description and the configured and required controls for a policy template. The instrument table shows each template's state and filters on it. The policy table adds a "Jurisdictions" column that reads "Global" for a template with none.
The card lists' query parameters q, domain, source, status, version, sort, and page no longer apply, and a bookmark that uses them is not redirected.
Compatibility
The v2 changes are additive. PUT /api/v2/settings/asset-type-templates/{id}/publish now also accepts a DALP Library template and an unpublished template. PUT /api/v2/settings/asset-type-templates/{id}/unpublish is new, and answers 409 ASSET_TYPE_TEMPLATE_NOT_UNPUBLISHABLE for a template that is a draft or already unpublished. Template responses gain an isPublished boolean for the calling organisation, and the list accepts isPublished as a filter and a sort field. The frozen v1 surface has no instrument template routes, and its request and response shapes do not change.
PUT /api/v2/settings/asset-type-template-structures/{id}/publish and PUT /api/v2/settings/asset-type-template-structures/{id}/unpublish are new. Structure responses gain an isPublished boolean, each member gains isPublished and isHidden, and the structure list accepts isPublished as a filter and a sort field. Template responses with a publication state gain publishedStructures, the published structures that use the template.
Three existing operations gain a new rejection instead of a new shape. POST /api/v2/tokens answers TOKEN_CREATE_TEMPLATE_UNPUBLISHED for any create that names an unpublished template, POST /api/v2/token-issuance-runs answers TOKEN_ISSUANCE_RUN_TEMPLATE_UNPUBLISHED for an unpublished template and TOKEN_ISSUANCE_RUN_STRUCTURE_UNPUBLISHED for an unpublished structure, and PUT /api/v2/settings/asset-type-templates/{id}/unpublish answers ASSET_TYPE_TEMPLATE_USED_BY_PUBLISHED_STRUCTURE for a template a published structure uses. All are non-retryable 409 codes listed in the error reference. The frozen v1 route POST /api/v1/token/create gains no new code: a create that names an unpublished template answers the 422 INPUT_VALIDATION_FAILED (DALP-0316) it already publishes, with a message that names the template. A client that wants to avoid the round trip reads isPublished on the template before it creates.
Policy template publishing does not change. It stays permanent, and a policy template cannot be unpublished.
Publish a template in the Console → · Issue a new asset → · Understand instrument templates →
Instrument catalog
The catalog of instrument shapes grew from twenty-four to thirty-three, adding two sukuk structures, a digital asset class, a spot commodity, and more.
Compliance controls
Six controls close gaps found in a two-class share structure: expiring claims, a sanctions rule the subject cannot undo, a minimum holding, and a supermajority.