On-chain transferability does not remove the need for limited-partnership governance. It changes where that governance lives and who can verify it. The question every institutional allocator asks, early in diligence, is: what protects the LP in a structure where the GP controls the vehicle and the token is transferable? The answer, in our case, is a layered governance architecture — partnership agreement, LP advisory board, AIFMD-compliant GP, depositary, and token transfer agent — that provides independent check points at each layer.

Layer one: the partnership agreement

The foundational governance instrument is the Luxembourg SCSp partnership agreement. It specifies LP voting rights on defined matters, the scope of GP authority, the procedures for amending the agreement, the frequency of LP meetings, and the circumstances under which the GP may be removed. It is negotiated at the outset between GP, LP cornerstone investors, and Luxembourg counsel, and is governed by Luxembourg partnership law.

Layer two: the LP advisory board

The LP advisory board — composed of cornerstone LP representatives — exists as the standing institutional governance body between formal LP meetings. The advisory board's scope covers: advice on conflicts of interest, advice on valuation methodology for NAV reporting, advice on material changes to investment policy, and consultation on extraordinary distributions. The advisory board does not run the fund; the GP runs the fund. The advisory board provides an independent LP perspective on matters where GP discretion is meaningful.

Layer three: the AIFMD-compliant GP

Alkemya Partners GP S.à.r.l. is AIFMD-compliant. It operates under the AIFMD organisational requirements, conflict-of-interest rules, risk-management framework, and reporting obligations. This is where the regulatory discipline on fund-level activities sits — not at the LP level, but at the GP level where the fund-management activity takes place.

Layer four: the depositary

A Luxembourg depositary sits independent of the GP and is responsible for: safeguarding the assets of the SCSp, verifying the flow of cash into and out of the vehicle, and — critically for a physical-reserve vehicle — verifying the existence, custody, and valuation of the underlying physical asset. The depositary function is the single most important independent check on GP conduct in the Luxembourg alternative-investments architecture.

Layer five: the token transfer agent

On-chain transferability does not remove the need for limited-partnership governance. It changes where that governance lives and who can verify it.

The digital-security layer adds one governance function that has no direct analogue in conventional LPs: the token transfer agent. The transfer agent is the entity that maintains the on-chain registry of LP interests, enforces the Reg-S transfer restrictions at the smart-contract level, and reconciles the on-chain registry with the off-chain partnership-register records. This function is critical because it prevents an on-chain transfer to a restricted person (a US person under Reg S, for example) from creating a legal but unenforceable transfer of LP interest.

In ALKN's architecture, the transfer agent is bound by the partnership agreement and supervised in coordination with the depositary. The on-chain permissioned-transfer logic is the technical enforcement of the partnership agreement's transfer restrictions, not a separate rule set.

Reporting cadence

LPs receive: quarterly NAV statements, annual audited financial statements, periodic reports on the physical reserve audit, and notifications of any material events under the partnership agreement. Advisory board members receive additional ad-hoc communications on matters within the advisory board's scope. The reporting cadence meets or exceeds the market standard for institutional private-markets vehicles.

What changes in a down scenario

A serious governance architecture is tested in a down scenario. If the vehicle's physical reserves were, hypothetically, to become impaired — through custodial failure, specification dispute, or secondary-market dislocation — the LP protections would activate in the following order: the depositary would verify the discrepancy and notify the GP, the GP would notify the LP advisory board, the advisory board would consult on appropriate response, a material event notice would be issued to all LPs, and an LP meeting could be convened under the partnership agreement's extraordinary-meeting provisions. The on-chain layer would not affect this process; it would simply track whatever LP interests existed under the off-chain register.

This is governance as architecture, not as a compliance narrative. It is designed to work in the scenarios where governance actually matters, and it is designed to be independently verifiable by allocators before they commit capital. If an institutional allocator cannot read a tokenised LP's governance stack in fifteen minutes and underwrite it in an hour, the governance stack is inadequate. Ours is designed to pass that test.