> For the complete documentation index, see [llms.txt](https://docs.syntetika.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.syntetika.io/protocol-operations/the-end-to-end-operational-workflow.md).

# The End-to-End Operational Workflow

Our financial operations run on a twice-monthly cadence, with NAV struck on the 15th and at month-end. Every step follows one rule: the finalized NAV publishes as soon as it is verified, and nothing is dealt at a price that was already public when it was requested.

<figure><picture><source srcset="https://370893244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfMNy5JyvOjr2XIP52SlC%2Fuploads%2Fi9xYwCM079AuMu8fKb6n%2Ftimeline-dark%403x.png?alt=media&amp;token=3ef6001c-b53d-4bc1-b107-051aafe9fb80" media="(prefers-color-scheme: dark)"><img src="https://370893244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfMNy5JyvOjr2XIP52SlC%2Fuploads%2FG5FsYvqXeyYE0fPTCu28%2Ftimeline-light%403x.png?alt=media&amp;token=9b2da906-3930-4d33-aa2b-1f4dc18ee40d" alt=""></picture><figcaption></figcaption></figure>

***

### 1 — Accumulation

Participants deposit the vault's asset at any time. Deposits accumulate as pending, unminted balances, and redemption requests queue alongside them.&#x20;

Deposit cancellations close at the cutoff and reopen once the cycle has been processed; redemption requests can be cancelled at any time before they are paid.

***

### 2 — Cutoff

Queues close two days before each strike, at 16:00 UTC, shown in your local time in the app; if that day falls on a weekend or holiday the cutoff moves back to the preceding business day. From that moment the deposit side of the cohort is fixed; a redemption may still be withdrawn until it is paid. Strike dates do not move. Exact cutoffs for each cycle are shown in the app.

Every request parked at the cutoff joins the cohort and transacts at the finalized NAV of the strike that follows, once NAVC has delivered it. Later requests roll into the next cohort.&#x20;

The curator nets the cohort at the cutoff. Pending deposit capital is compared against what is owed to the redemption queue, and the balance between the two determines the cycle:&#x20;

<figure><picture><source srcset="https://370893244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfMNy5JyvOjr2XIP52SlC%2Fuploads%2FE0inC3b0rzsPeY9D2OJA%2Fnetting_table_dark%403x.png?alt=media&amp;token=c374da4c-820d-4565-85f3-6f3313f69502" media="(prefers-color-scheme: dark)"><img src="https://370893244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfMNy5JyvOjr2XIP52SlC%2Fuploads%2Fo7gjaqk6oVeIdSVPc9LC%2Fnetting_table_light%403x.png?alt=media&amp;token=da8cac0d-b6f7-45b6-ac3e-820eee8be707" alt=""></picture><figcaption></figcaption></figure>

For participants, the cycle type changes only timing, never price. Deposits mint identically in both cases, and redeemers are paid at the same strike NAV either way.

***

### 3 — Strike

On the 15th and at month-end, the fund takes its NAV snapshot and the cohort's flows become effective as of that date. This is the valuation that prices the cohort itself.

***

### 4 — Finalization, NAV Publish and Mint

Typically within five business days of the strike, and up to fifteen in exceptional cases, NAV Fund Services (Cayman) Ltd, the fund's administrator, and NAV Consulting Inc., its NAV calculation agent (together NAVC), finalizes the official NAV.&#x20;

The attested figure is published on-chain promptly after verification, from a designated publishing address under a joint approval policy in which each operating party must sign.

No single party can publish alone. Only attested, finalized figures are ever published.&#x20;

On the day the finalized NAV is published on-chain, the cohort mints as one lot at that price: deposits mint the vault token at the strike NAV, and the redemptions in the cohort are valued at the same figure. The NAV publish, the mint and the wire all happen that day.

The published figure prices the cohort that closed before its strike, and nothing after. Until the next figure is finalized, it remains the live on-chain price, but nothing later is dealt at it.&#x20;

Two cycles can be in flight at once, since a strike's NAV may finalize after the next cutoff. If a strike's NAV is not final by the next cutoff, the later cohort still closes and waits for its own strike; deposit cancellations may stay closed across both. Each cohort mints at its own price.&#x20;

***

### 5 — Routing, Payout and Settlement

The SPV subscribes only the net, and gives the fund notice of it at the cutoff.

Net subscriptions are wired into the fund on the day the NAV is published and admitted as of the strike date at the strike NAV. NAV and wire move on the same day.&#x20;

Net redemptions are submitted as a withdrawal request at the cutoff, priced at the strike NAV, and paid once the NAV is published and settlement runs. Where a fund offers liquidity less often than the strike cadence, withdrawals from that vault are dealt on the fund's dealing days.&#x20;

Capital is subscribed, not warehoused; the SPV holds nothing beyond a small operational float.

On subscription cycles settlement is immediate, the redemption queue is paid in full the same day as the mint, at the strike NAV.&#x20;

On redemption cycles, the queue is paid in order once settlement with the fund runs, at the strike NAV.&#x20;

Deposits and redemptions are both dealt at the strike NAV. NAVs strike on the 15th and last day of each month and finalize typically within five business days, and up to fifteen in exceptional cases. Nothing transacts until that figure is in, so nobody is dealt at a price that was already public when they queued.
