Trade Wars · Captain's operating doctrine
Capacity before opinion. Evidence before fire.
Trade Wars is a self-custodied command system. It calculates, organizes, and displays campaigns. It never turns a local plan into transaction authority.
Fleet roles
Manual fleet Check-In and PWA restart
- Install or open Trinity on the secure trade origin. The fleet roster merges public addresses saved in Check-In and local War Room vessels on that device.
- Use Open to view one remembered wallet. Public address and public-chain reads do not create signing authority.
- Use Check In on one vessel, or Check In Next Wallet to work through the fleet. Switch the wallet provider to the address shown before approving the readable, device-bound Check-In message.
- If the provider returns a different account, Trinity stops that step. It never substitutes one fleet wallet for another.
- After the PWA or browser closes, the device may restore the public fleet roster and unexpired, revocable Check-In sessions. It does not restore a private key, provider connection, background monitor, or transaction approval.
- A wallet can remain remembered without being checked in. Reconnect the exact wallet whenever its Check-In session expires or a transaction needs review.
Verifying every fleet wallet is optional. A captain may keep the whole public roster on one device, verify selected wallets, or use one wallet at a time. Nothing scans or trades until the captain acts.
Captain's launch sequence
- Open the War Room and connect a compatible self-custodied Solana wallet. Connection reveals only the public address; it does not move capital.
- Register that public address as one vessel on the current device.
- Create a campaign using the exact token mint, verified entry anchor, current observed price, verified wallet value, and maximum commitment.
- Keep maximum campaign commitment at or below 10% of verified wallet value.
- For a Scout, supply rank 101–1,000, at least $1,000,000 of 24-hour volume, and four positive hourly volume observations.
- Activate the campaign. Hold Fire and Pit states block local PIT review.
- Wait for the next sequential 2%–4%–8%–2%–4%–8%–10% trigger and at least one hour after the prior confirmed fill.
- Open PIT only when local gates clear. A fresh backend card must independently match live wallet, market, capacity, route, and accounting evidence.
- Review the exact transaction in the connected wallet. Reject it if the mint, amount, program, accounts, or economic bounds differ.
- After confirmation, wait for reconciliation. Never treat a submission, deposit, transfer, projected yield, or local campaign entry as realized profit.
Ladder and exit doctrine
The eight-order campaign uses increasing order weights across a sequential 2%–4%–8% cycle and a final 10% step. Ten percent of the campaign ceiling remains reserved for friction. The displayed exit target is the higher of one-third recovery from the lowest filled level or a 10% profit over weighted basket basis.
This is a finite, capital-bounded ladder—not a promise of infinite capital, accuracy, or recovery. No asset is guaranteed to survive, retain liquidity, or avoid absolute loss.
Fail-closed rules
- No private key, seed phrase, pooled custody, leverage, or automatic public-wallet signing.
- No fresh engine card, no transaction.
- No verified wallet value, no 10% capacity claim.
- No one-hour spacing, no next add.
- No exact mint, route, liquidity, and volume evidence, no Scout deployment.
- No verified settlement and accounting proof, no profit claim.
- The Founding Fleet route is a separate paid public Solana Mainnet mint. Connecting requests no signature and moves no funds. Minting occurs only after the captain selects a ship and separately approves the paid wallet transaction. The NFT is an eligibility record only; Mission activation, delegation, automated execution, and trading authority remain disabled.
- The immutable ship-policy field
nft_launch_enabled:falserecords the reviewed pre-launch state when those policy bytes were sealed. It remains unchanged as history. The later R60 approval made only the five paid R60 issuance paths canonical; it did not activate Missions, automation, or wallet authority.
Trading can lose all deployed capital. Trade Wars is operational discipline and transaction control, not a guarantee of results.