# Mugi V1 synthetic allocation recommendation

Retain the advisory baseline: crew 0 receives zero and each living crew, indices 1–9, receives a cumulative target of 1000 synthetic accounting units. This is a discretionary equal allocation under missing market evidence. It does not imply equal market quality or expected returns.

This is research for a consumer testing production MugiBuybacks allocation approval and MugiIMDVerifier proof validation. It is not a signed oracle approval, proof of successful validation, transaction, deployment, or financial-return prediction. No ETH budget is funded, no crew tokens or pools are deployed, and no swaps are possible. The inherited names `totalWei` and `currentTargetsWei` denote synthetic test units here, not funded ETH.

## Evidence and snapshot boundary

The source for all allocation inputs is the requester's supplied confirmed typed snapshot, identified by chainId **1**, blockNumber **26228656**, blockHash **0xdb7e68ce15c393e52f617ae14119b54050375c24ad946e2c6032bf7c4bbc3a07**, timestamp **1792437383**, and snapshotHash **0xf5c0ddadb7ee119e5235c91eb6c6f1109b6fa4f7463ebebb8b9397a9cfcd9e42**. Its hook is **0x161DB86AdFfb56Af0926fEee4C2d6AEb86b278a2**. These identifiers are supplied provenance, not independently authenticated by this report. No chain state was fetched and no substitute block was used.

The snapshot states `aliveMask = 1022`, `totalWei = 9000`, and `spentWei = 0`. Bits 1–9 are set, so there are nine living crews; crew 0 is dead. All ten `crewSpentWei` values are zero. The current cumulative targets are zero for crew 0 and 1000 for each other crew. Every observation has `eligibleSupply = "0"`, a zero token address, `pool = null`, and `twap = null`. The zero addresses are supplied undeployed-token markers, not proposed recipients or usable contracts.

## Methodology and judgment

For general methodology, the primary [Uniswap v2 oracle documentation](https://developers.uniswap.org/docs/protocols/v2/concepts/oracles) explains constructing a TWAP from cumulative-price observations across a time interval and relates manipulation cost to liquidity and averaging duration. This supports considering observed depth and spot/TWAP divergence when such evidence exists. It supplies no Mugi observation or price and does not establish which pool design Mugi would use.

Here native ETH depth, spot prices, and spot/TWAP deviations are unknown: null pools and TWAPs cannot be scored as zero depth, zero price, or zero deviation. The supplied eligible-supply zeros are recorded facts of this synthetic fixture; they do not provide an eligible-holder count or evidence of relative demand. There is consequently no supplied comparative signal that justifies favoring one living crew. Equal targets preserve symmetry and the existing baseline, avoiding an unsupported ranking. That choice is a policy judgment under uncertainty, not a statistically estimated optimum.

## Exact integer feasibility

With T = 9000 and N = 9, each living crew's lower bound is floor(3 × 9000 / (4 × 9)) = 750; its upper bound is ceil(5 × 9000 / (4 × 9)) = 1250. These divisions are exact. Every proposed living target is 1000, inside [750, 1250] and at least its already-spent amount of zero.

| Crew indices | Status | Cumulative target per crew | Already spent per crew |
| --- | --- | ---: | ---: |
| 0 | Dead | 0 | 0 |
| 1–9 | Living | 1000 | 0 |

All ten targets sum to 0 + 9 × 1000 = 9000 exactly. Targets include spending already incurred; they are not additional allowances on top of prior spending. Since spending is zero here, each living crew's remaining synthetic allowance is also 1000. RoundId **1**, nonce **1**, and deadline **1792458983** remain exactly as supplied. The deadline is 21600 seconds after the snapshot timestamp; this arithmetic does not certify acceptance at any later execution time.

## Uncertainty and unanswered questions

The snapshot cannot answer which living crew would have deeper native ETH liquidity, more eligible holders, or a smaller spot/TWAP deviation in an actual market. No relative market preference or return forecast is supported. Such questions would require observations absent from this fixed snapshot; they are left unanswered rather than filled with newer data. The recommendation is feasible under the stated arithmetic constraints, but this report does not independently establish snapshot authenticity, contract authorization, signature validity, nonce availability, or verifier acceptance.

## Proposed cumulative allocation

```json
{"roundId":"1","nonce":"1","deadline":"1792458983","allocations":["0","1000","1000","1000","1000","1000","1000","1000","1000","1000"]}
```