> For the complete documentation index, see [llms.txt](https://docs.lumia.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumia.org/tokenize/legal/compliance-overview-for-issuers.md).
# Compliance overview for issuers
**Who this is for:** issuers about to design a token contract who need to know what compliance groundwork is theirs to do first.
{% hint style="warning" %}
This page lists **questions**, not answers. It states no regulatory, licensing, or jurisdictional position, Lumia's or otherwise. Every question below is one your own legal counsel resolves, not this documentation.
{% endhint %}
## The architecture, briefly
Lumia separates a permissionless base layer (the chain itself imposes no identity gate) from a permissioned application layer (the issuer's own contract enforces whatever gate the asset needs). The full explanation lives at [Permissionless base, permissioned app layer](file:///lumia/compliance/Permissionless-base-permissioned-app-layer.md); the four named checks issuers commonly build on top of that split (KYC, KYB, KYT, KYV) are explained together at [Compliance model overview](file:///lumia/compliance/Compliance-model-overview.md). This page doesn't repeat either; it exists to name what an issuer still has to decide once they understand that architecture.
## Questions to resolve with your own counsel
Classification
How is this specific asset, in each jurisdiction where you intend to offer it, legally characterized, and what obligations follow from that characterization? This documentation makes no claim about how any asset class is or should be classified.
Eligibility
What investor category or verification threshold does that classification require, and how will you prove a given holder meets it? See [Eligibility & investor tiers](broken://pages/18dd7868d1562f46add14b80c206289267956403) for the pattern, not the specific thresholds: those are jurisdiction-specific.
Verification provider
Who performs your KYC/KYB checks, what evidence do you retain, and for how long? See [KYC (Know Your Customer)](file:///lumia/compliance/KYC-Know-Your-Customer.md) and [KYB (Know Your Business)](file:///lumia/compliance/KYB-Know-Your-Business.md) for what each check verifies.
Ongoing monitoring
What transaction-monitoring (KYT) obligations apply once the asset is live, and who inside your organization owns that ongoing process? See [KYT (Know Your Transaction)](file:///lumia/compliance/KYT-Know-Your-Transaction.md).
Custody and bailment
If the underlying asset is physical or requires a third-party custodian, what does that bailee agreement need to say? See [Bailee agreements & common law](broken://pages/537d3b8f93e6919c4335fc4eb2641f7c11cfa014).
Accountability
Who at your organization signs off on compliance before each issuance, distribution, and servicing event, and what happens if that sign-off is missed?
Redemption and wind-down
What legal obligations govern winding down the asset or the issuing entity, separate from the on-chain mechanics described in [Stage 5: Redeem](file:///5838283/lifecycle/Stage-5-Redeem.md)?
## What this page does not do
{% hint style="warning" %}
It does not tell you which of these questions apply to your asset, does not state an answer to any of them, and does not describe Lumia's own regulatory or licensing position. **No page in this documentation set makes a jurisdictional, licensing, or regulatory claim, by design. Th**ose questions belong to you and your counsel.
{% endhint %}