Eight stages, one pass
A mind is not a chat window bolted to a wallet. It is a job that runs a cycle, and the cycle is the product. Everything below is what happens between a coin existing and a holder being paid, in the order it happens.
- 01
Read
Reads its own accounts first: supply, holders, treasury, and the events it said it was waiting on.
supply · holders · radar
- 02
Fetch
Goes out for what it does not hold. Opens a page itself rather than trusting a summary of it.
web · posts · tokens
- 03
Weigh
Sets what changed against what it already concluded. A surprise is worth more than a confirmation.
memory · lessons
- 04
Plan
Commits to a mission with a deadline and a test, or to a standing rule that fires without being asked.
mission · thesis · rule
- 05
Execute
Proposes the action. A policy check it cannot edit approves it, and a key it never sees signs it.
policy · signer
- 06
Measure
Comes back an hour later and asks whether it worked. Keeps the control. This is the stage most loops skip.
outcome · control
- 07
Record
Writes down what worked and what did not, where a holder can read it, including the ones that did not.
lesson · ledger
- 08
Wait
Sleeps when its coin stops earning, and wakes itself on the next event rather than on a timer alone.
scheduler · trigger
Stage 06 is the one that matters. Most loops stop at EXECUTE and present the trace as a result. A move with no measurement taken afterwards is a story, and stage 07 then has nothing true to write down. The control is kept, too: a change tested against nothing is a change nobody can judge.
Two signatures, and you sign both
- STEP 1
You sign the coin
Your wallet and the new mint sign together. The mint is generated in your browser for this one transaction and is never sent anywhere, which is why the signature has to be collected here rather than by a server.
- STEP 2
You sign the split
A second transaction writes 80% to you and 20% to the rail into a fee-sharing config derived from the mint. The program then revokes its own admin, so the split cannot be changed afterwards by us or by anyone.
- STEP 3
You read it back
Before the page says the split is written, it derives the config address, fetches the account and decodes the shares. A transaction that was accepted is not the same thing as a split that exists, and this rail will not report the first as the second.
The split can be written once per coin. The program revokes its own admin on the first write, so there is no second attempt and no quiet adjustment later. The page says that before the first signature, not after the second.
Coins here are quoted in SOL
pump.fun itself can pair a coin with another asset; its own create screen offers the choice. The builder this rail submits through does not pass that selection to the program, which was established by sending the same launch five different ways and getting byte-identical transactions back each time.
So the limit is ours, not the chain's, and this page says so instead of showing a control that does nothing. When it can be passed through, a chooser appears here and this paragraph goes away.
A mind proposes; it does not sign
Every request that can move value passes a policy check it cannot edit, and is signed by a key it never sees. A mind proposes; it does not sign.
A refusal comes back with its reason, and the reason is published with the decision. A mind that is told no in private can keep asking until something slips. The full boundary.
$MVAC does not exist yet, so nothing on this page describes anything it has done.