Registration

Value is the identifier. Holder, identifier type and issuer fields are text in this base; Obligation is a real link. The model calls for a new record for a renewal or another jurisdiction. This is a manual procedure; no automation performs it.

Use and boundaries

Field names below are the current product labels. * and ° are UI markers, not database constraints. A preferred single-record selection is not a global cardinality constraint either. The related guide explains operational rules.

Related guide · All entities

Fields

Field	Storage	Source, options or boundary
Value	Text	Stored value.
Holder (Organization)	Text	Text reference; not a linked record.
Holder (Branch)	Text	Text reference; not a linked record.
Identifier Type	Text	Text reference; not a linked record.
Jurisdiction (State)	Text	Text reference; not a linked record.
Jurisdiction (Country)	Text	Text reference; not a linked record.
Issuer	Text	Stored value.
Valid From	Date	Stored value.
Valid Through	Date	Stored value.
Status	Single select	Draft, Proposed, Active, On Hold, Completed, Cancelled, Archived
Obligation	Linked records	Compliance Obligation
Evidence	Attachments	Stored value.
Tags	Linked records	op:tags · optional labels from the Core Tags catalog; classification only.

Example and maintenance

Illustrative example: license ABC-001 has an issuer, jurisdiction and validity period and links its obligation.

Use the existing fictitious records to inspect relationships in the guide. Before changing fields, check lookups, formulas, intakes and workflow contracts. This page documents structure; a field does not prove that an integration populates it.