Specification reference: summaries, with sources.

Historical source, current applicability

These source ranges preserve the provenance of the uploaded specification, not proof that every described feature is implemented, admitted or enabled today. The precedence rule above resolves disagreements inside that historical document; it does not override current release boundaries, custody capabilities or exact transaction review.

• Four historical launch paths are not four open routes. Native reward issuance is gate-dependent; standard is existing recovery only, and new Pump/adoption admission is deferred.
• Historical reserve-acquisition instructions do not apply to new reward issuance. No compulsory purchase of the newly issued reward token is required; the separate COMPUTER holding prerequisite remains.
• Turnkey policies and independent governance describe historical design, not universal native custody. Native wallets are server-managed; no no-drain assurance follows from this document.
• Index, routed dividends, hosted leverage and vault mechanics are design references, not operational payout or trading promises. Existing legacy financial obligations retain their original recovery terms.

Live configuration is display-only, never permission.

§6 Launch layer

Lines 303–356 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Four entry paths (StonkFun reward, StonkFun standard, pump.fun new, adoption) all end in a coin record, an allocation record and destination wallets.
• Thesis launches buy the reserve share with buy_exact_out against total supply; only the share actually held after confirmation is ever displayed.
• Adoption is a hard gate: a reward-mode mint that fails the launchpad, mode or tax check is marked defective and hidden from funding surfaces. Refund detail in this section is older shorthand; §28 F7/F8 governs.
• Every command carries an intent id; a retry returns the original result and no second transaction is built after submission.

§7 Inflows and the reserve

Lines 357–378 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Every amount a coin earns is first recorded as an inflow row (tax dividend, creator fee, trade fee, meme fee, top-up).
• The thesis reserve policy denies any transfer of the coin's own mint; it may move inflow assets to treasury token accounts only.
• The platform inflow fee is taken once, before the router, on tax-dividend and creator-fee inflows; trade-fee and meme-fee streams are exempt from it (§7 table, §27 item 14).

§8 Allocation router

Lines 379–414 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Five destinations: DESK, INDEX, EMBER, VAULT, DIVIDEND, with named presets.
• Splits sum to 100 with a minimum share on every selected destination; DIVIDEND is unavailable on StonkFun reward coins.
• A creator may re-cut once per window; changes apply only to later inflows and every change is public history.
• No creator control withdraws funds, adds leverage, opens a position or touches a key.

§9 Desk engine

Lines 415–516 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• A mandate holds one to three perp legs whose shares sum to 100; aggregate notional is capped per mandate including resting orders (§27 item 15).
• Legs fund in share order once the opening minimum clears; a leg arms in the same database transaction as its funding row and shows LIVE only after an actual fill.
• Kill drawdown, take-profit milestones and liquidation step-down are pure rules. Thesis perp realized profit is 100% own-coin buyback; the house keeps a 50% exception (§27 item 28).
• PAPER fills use the live book with real fees and estimated slippage and are labelled PAPER.

§10 Index engine

Lines 517–528 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• The roster is the StonkFun flywheel active set in rank order, never a hardcoded count; a fallback count is labelled ESTIMATED.
• Deduction order: gas reserve first, then the treasury cut, then an equal split (§27 item 16). Unquotable roster coins are skipped, never substituted.
• Airdrop rounds snapshot holders excluding pools, the burn address and platform wallets; small entitlements roll forward.

§11 Dividend engine

Lines 529–539 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• For coins without a native transfer tax. Pays holders in the inflow asset on a fixed cycle.
• One hidden snapshot per round, committed at round start and revealed at payout, with the holder list signed by an out-of-runtime verifier key.
• Disabled on StonkFun reward coins, where StonkFun pays the tax to holders natively.

§12 Ember

Lines 540–545 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• The EMBER share buys the coin through its own pool and sends it to the burn address.
• Purchases wait when price impact exceeds the configured ceiling or no route exists.
• Ember is separate from perp-profit buybacks.

§13 Meme leverage engine

Lines 546–657 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Markets resolve to Phoenix, Arqen or an isolated Percolator market; hosted Percolator markets stay disabled until audit and adversarial analysis gates pass.
• Effective leverage is the minimum of user tier, side cap, venue cap, mode cap and risk ceiling (§27 item 7).
• Bootstrap and seeded vault modes; caps, oracle clamp and liquidity halt are the primary defense (§27 item 18).
• Settlement is SOL for Percolator markets and USDC on Phoenix and Arqen.

§13.6 Meme engine fees

Lines 639–651 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• No fee to open, no fee to close at a loss, no funding on hosted markets. The only hosted fee is an asymmetric impact haircut on realized profit.
• Haircut split: platform burn queue, vault equity and vault insurance. External venues keep their own fees.

§17 Revenue model and the $COMPUTER burn

Lines 678–724 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Platform cash streams are split by integer floor-third with remainder conservation: one third burns $COMPUTER.
• Standard creator fee vaults split creator 60 / platform 40 (§27 item 27).
• Perp realized profit never touches $COMPUTER on thesis coins. Scenario tables in this section are sizing, not forecasts.

§20 Security

Lines 806–858 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Historical Turnkey design: separate deny-by-default policies, reserve own-mint bans, no lookup tables or durable nonces. This is not a description of all current native wallets.
• Historical governance design: immediate risk-reducing guardian actions and a 24 hour public timelock with majority multisig for risk increases. Current enforcement needs independently scoped evidence.
• S1–S4 are specified proof contracts, not proof that a current environment satisfies them. Native wallets are server-managed; no compromise-proof custody is claimed.

§21.4.9 Learn

Lines 1033–1036 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Keep the existing guide. Add one page per engine with eyebrow LEARN / <ENGINE>, one paragraph, one diagram, governing config values and a link to the spec section.

§22 Copy that must ship

Lines 1302–1307 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• The risk disclosure paragraph that must appear verbatim; it is published in full on the Risk page.

§25 Open items and risks

Lines 1557–1610 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Lists day-zero and per-slice blockers that remain open until proven, and a risk table covering custody exposure, launchpad rule changes, bridge failure, meme market drain, oracle manipulation, key compromise and scam launches.

§27 Decision Ledger (v6.6.1)

Lines 1645–1681 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Rules that override older body text: refund boundary (item 11), fee waterfall (item 14), index and dividend order (item 16), own-coin buyback (item 28), kill vs timelock (item 8).
• Historical item 11 refunds the launch fee only on defective or reserve_short and never the reserve buy or top-ups. Superseded where it overlaps by §28 F7/F8: the service fee is also refunded on reserve_failed, and unspent reserve budget returns to the original payer in the original asset.

§28 Financial Invariants Addendum (v6.6.2)

Lines 1682–1721 · COMPUTER.EXE + STONKED Platform Spec v6.6.4 FINAL (2026-10-01)

Historical summary — not spec text or current enforcement evidence

• Authoritative over §27 where they overlap.
• F2.1 share epochs: rollover happens only on an attempted mint, never on price alone. A triggering deposit first pays the FIFO queue; the epoch closes only if equity for shares is still zero or negative at that mint. A positive surplus after the queue does not close the epoch. Closed shares are non-redeemable.
• F3/F4 with F3.1: queue payment is strict FIFO, head-first, no skipping; while the queue is non-empty every outflow except returned margin, liquidation bounty and the haircut attached to the payment being made waits.
• F6: the maximum gross profit before any haircut is fixed when the position opens, in SOL or USDC depending on its collateral.
• Current reward issuance has no compulsory reserve purchase or minimum holding of the newly issued reward token. This does not remove the separate COMPUTER launch holding prerequisite. Service fees, network/rent and optional personal buys are itemized separately. Existing funded F7/F8 reserve obligations retain their original recovery and refund terms.