> For the complete documentation index, see [llms.txt](https://venzofinance.gitbook.io/venzofinance-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://venzofinance.gitbook.io/venzofinance-docs/venzo-app/architecture/issuance-and-operation-layer.md).

# Issuance & Operation Layer

The Issuance & Operation Layer is the core product engine inside the Venzo capital stack. It composes tokenized assets and vault operations into unified products that feature a single methodology, a product-level Net Asset Value (NAV), and a streamlined subscription and redemption experience.

The architecture is built on ten core modules:

<table><thead><tr><th width="187.38671875">Module</th><th>Function</th></tr></thead><tbody><tr><td>Product Registry</td><td>The canonical registry of live products, product IDs, component lists, methodology versions, fees, capacity limits, eligibility policies, and lifecycle status.</td></tr><tr><td>Issuance Engine</td><td>Creates the product token, share, receipt, or position record and links it to the registry, eligibility logic, NAV source, and redemption path.</td></tr><tr><td>Composition Engine</td><td>Defines components, target weights, allocation bands, sleeves, wrappers, and approved component sources across internal vaults and external whitelists.</td></tr><tr><td>Methodology and Rules Engine</td><td>Stores product methodology, rebalance cadence, trigger rules, concentration limits, drawdown controls, liquidity requirements, and allowed actions.</td></tr><tr><td>Unified NAV Module</td><td>Aggregates component NAV, pricing feeds, idle assets, liabilities, accrued fees, and settlement records into a unified product-level NAV.</td></tr><tr><td>Rebalancing Controller</td><td>Executes rebalance instructions strictly inside approved allocation bands, component whitelists, venue rules, and governance limits.</td></tr><tr><td>Primary Market Module</td><td>Handles subscription, creation, redemption, epoch closure, price locks, liquidity checks, and claim execution.</td></tr><tr><td>Eligibility and Transfer Policy</td><td>Applies KYC/AML requirements, jurisdictional rules, allowlists, investor limits, transfer restrictions, and product-specific access rules.</td></tr><tr><td>Disclosure and Reporting Layer</td><td>Publishes methodology, component exposure, NAV history, fee schedules, risk disclosures, verification records, product events, and wind-down notices.</td></tr><tr><td>Lifecycle Manager</td><td>Supports launch phases, component changes, methodology updates, fee adjustments, pauses, migrations, product maturity, and final wind-down procedures.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://venzofinance.gitbook.io/venzofinance-docs/venzo-app/architecture/issuance-and-operation-layer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
