# Belljaw launch plan

Files-only specification. Nothing has been deployed, funded, published, advertised or promised to a participant. The developer is an unnamed role, as are the swarm and reviewers. The dates below are relative gates for a future authorized launch, not instructions to execute one now. Default A has no player payouts. Source and assumption labels refer to RESEARCH.md.

## Day 0: make the claims verifiable before opening the floor

The developer supplies genuine deployment addresses for the developer allocation, swarm allocation and launch-network fee recipient. These are owner-settable deployment inputs; no substitute addresses appear here. The vault is the launching-side recipient and must be a contract. The actual chain, fee routing, immutable custody and code must be verified before liquidity becomes tradable.

| Responsible role | Action | Target or budget | Evidence | If missed |
| --- | --- | --- | --- | --- |
| Developer | Fund the launch capital and reserve | 20 ETH seed; USD 6,000 equivalent ETH expense reserve | Funding transactions and native-asset balances | Do not open trading until funded |
| Developer | Pay for engineering, review, original art, legal review and deployment allowance | USD 24,000 setup budget | Deliverable hashes and review scope | Revise scope or pay the gap; do not remove security gates |
| Swarm | Build plain-transfer token with immutable supply | 1,000,000,000 tokens; 18 decimals; transfer tax 0%; no postlaunch owner mint; no automatic burn | Verified source, bytecode and invariant tests | Stop launch preparation on any mismatch |
| Swarm and developer | Implement and test fee adapter and vault custody | Pool fee 1.25%; 1% to vault; 0.25% to launch network; extra hook fee 0% | Buy/sell, rounding, fee-recipient and fee-collection tests | No substitute token tax or extra fee |
| Independent review role | Review vault, fee adapter, oracle gates, escrow and irreversible LP restrictions | No unresolved critical or high finding | Review tied to exact code hashes | Repair and review changed paths before launch |
| Developer | Execute required launch distribution | 35% pool seed; 10% swarm; 55% developer in one transfer | Transfer events; sum equals entire supply | Abort on any differing allocation; never patch with a fourth recipient |
| Vault integration | Pair launch seed with ETH and hold LP principal irreversibly | BELLJAW / native ETH; full range | Pool key, seed balances, removal and position-transfer rejection checks | Do not describe liquidity as protected merely because an operator says so |
| Swarm | Deliver original character, logo and scene assets from BRAND.md at the later art step | Consistent face in every picture | Art review and authorship record | Correct likeness, caption or copied elements before release |
| IMD | Record release provenance | Matching specification, reviewed code and artwork hashes | Content hashes stored with deployment metadata | No launch-success claim from the existing test counter |

Only the designated pool's fee split is enforced by the proposed integration. A third-party pool may not send fees to the Firm. The launch-network recipient is fixed at deployment and is separate from Base gas. Verify the integration can enforce the specified economic split; if it cannot, do not silently choose a different launch service or alter the required numbers.

## Week 1: earn the first episode

| Responsible role | Action | Target | Evidence | If missed |
| --- | --- | --- | --- | --- |
| Developer | Manually send the required portion of its initial allocation to the specified dead address | 500,000,000 tokens; 50% of original supply; retained allocation 50,000,000 tokens or 5% | Successful transfer from developer wallet to 0x000000000000000000000000000000000000dEaD | Display pending or failed; postpone promotional launch-complete claims; no vault or token automation substitutes |
| Holders | Optionally register founding-season escrow | Entry during first 7 days; minimum 100,000 tokens | Timestamped deposit lots and active balance | Later buyers use normal tenure path; do not extend the window selectively |
| Swarm | Provide direct contract reporting views and reproducible read procedure | Fee credits, cash buckets, principal, token output, pending executions and manual-transfer status | Same result from independent reads at one block | Mark unavailable fields and fix reads; do not type treasury totals by hand |
| Permissionless executor | Attempt first buyback only after all guards pass | Accrued budget at least USD 25 equivalent; reference coverage seasoned 7 days | Execution receipt or guard-failure reason | Keep budget queued; post the deferred episode instead of a burn claim |
| Holders | Open first eligible weekly ballot | Complete prior epoch stake history; quorum 10% | Checkpoints, votes and eligibility proofs | Retain prior allocation; do not use a server tally |
| Rex narrator role | Prepare the first weekly Open Mouth chapter | 1 chapter based on actual settled report | Report hash and matching copy | Quiet chapter or correction, not fabricated activity |

The manual transfer is a developer action that must be verified, not a guaranteed event. The starting supply remains the ERC-20 totalSupply even after dead-address transfers. Separate the developer transfer, vault acquisitions and unsolicited transfers in every report.

## Month 1: open a useful quote lane

| Responsible role | Action | Target | Evidence | If missed |
| --- | --- | --- | --- | --- |
| Developer | Propose verified USDC pool entry to the whitelist | Notice period 7 days | Exact native asset address, pool key, code and issuer-risk disclosure | Leave the lane budget in ETH; no clone asset |
| Holders and vault | Select and fund the first expansion | At most 1 new pool per 30 days; minimum USD 2,000 equivalent funded position | Successful ballot, enforced limits and funded LP position | Accrue and report budget until the threshold and coverage pass |
| Vault | Use target liquidity shares with conditional lanes | ETH 60%; USDC 25%; cbBTC 10%; gold 5% | Budget allocations, explicit inactive-lane fallback to ETH | Do not seed a thin lane just to satisfy a calendar |
| Swarm | Reconcile first monthly report | Every fee receipt allocated exactly once | Launch fees separate from Portfolio fees and recycled self-fees | Freeze disputed reporting claims; repair accounting and replay reads |
| Developer | Continue external maintenance and observe vault expense cap | USD 1,000 external maintenance per month; USD 300 vault operating cap per month | External work records; contract reimbursements within cap | Reduce paid services or contribute externally; never withdraw LP principal |
| Community | Review the first holding-tenure promotion | Broker after 4 complete weeks | Escrow age and badge status | Follow actual deposit dates; no retroactive age awards |

The financial model's Portfolio volume after the first month is a conditional scenario. A late pool launch means that income must be set to zero until real outside trades occur. A gold asset remains unselected; do not announce an operational gold pool or use a stock wrapper without proving it meets the stricter rule.

## Month 3: prove the story can handle a quiet floor

| Responsible role | Action | Target | Evidence | If missed |
| --- | --- | --- | --- | --- |
| Developer and holders | Evaluate cbBTC lane against code, custody, oracle and depth gates | Within maximum 20% of new liquidity budget after vote | Verified whitelist record and active market coverage | Keep cbBTC budget in ETH; do not bridge to another chain |
| Developer and review role | Revisit the conditional gold lane | Maximum 5%; actual allocation 0% until authentic Base representation qualifies | Verified deployment and risks, not a ticker match | Keep explicit ETH fallback and list gold as unopened |
| Vault and swarm | Settle season-end report from contract state | 12 weekly chapters; monthly reconciliation complete | Accrued versus spent budgets, actual token transfers, LP inventory and fees | Report backlog and settle when safe; never infer purchases from a schedule |
| Community | Review the external-volume milestone | USD 5,000,000 cumulative outside volume | Pool event totals excluding vault self-swaps; ownership uncertainty disclosed | Run Quiet Floor Test episode; no paid volume campaign or deadline extension |
| Holders | Reach Partner eligibility through continuity | 12 complete weeks | Per-lot escrow age and current stake | Publish actual cohort sizes; wallet count is not person count |
| IMD and swarm | Package lessons for later company launches | Reconciled design and implementation review | Artifact and release provenance | Keep launch experimental status if evidence is incomplete |

## Operating policy and reasons

| Decision | Rule | Why |
| --- | --- | --- |
| Selected design | A; player payouts 0% | Ritual and governance must stand without income marketing |
| Optional B | Separate prelaunch configuration only, subject to jurisdiction-specific review | No surprise diversion of A buckets and no implied holder entitlement |
| Pair choice | Holder vote over delayed developer contract whitelist | Community direction within explicit asset-risk bounds |
| Launch liquidity custody | No principal withdrawal, position transfer or emergency sweep | Avoids a withdrawable launch position; immutability increases the need for review |
| Tokenized stocks | Allocation 0% | No issuer-freeze-free representation has been verified |
| Gold lane | Conditional; never a guessed asset or contract | Files-only design can define a gate without inventing deployment facts |
| Missed fee targets | Budgets scale with real receipts; queues can grow | No obligation to buy activity, emit rewards or sell treasury principal |
| Low-volume mode | Aggregate executions; respect minimum budget and expense cap | Limits fixed cash drain; preserves readable books |
| No-volume mode | Stop new funded activity after accrued budgets run out | A contract does not manufacture external demand |
| Communications | No price, monetary-outcome or guaranteed-execution claims | Report events and choices, not expectations |
| Public identity | Only invented narrator and unnamed operational roles | No person is advertised as founder, team or owner |

Predeployment checks must cover supply conservation, one developer allocation transfer, ordinary transfers, absence of mint/burn authority, fixed fee math in both directions, every path for collecting fees, immutable LP custody, stale-oracle deferral, rounding dust, snapshot integrity, sybil-neutral token-time arithmetic and the full cash reconciliation. These are future implementation requirements. This deliverable's own checks validate documents and arithmetic only; they are not a contract audit.