About the Program Notes Desk

Program Notes is a small English-language desk writing about launchpad automation on Solana at the level the chain records it: which instruction was sent, which accounts it named, what changed as a result, and what the transaction says afterwards. It is published by The Program Notes Desk, which is an editorial identity rather than a person, and it is independent of every launchpad and every tool it writes about.

What the desk covers

Six notes and a glossary, organised into two sections. Instructions deals with what a program is asked to do: discriminators, argument layouts, ordered account lists, the preamble instructions that travel with a trade, and the errors a program returns when a request does not match its expectations. Behaviour deals with what the ledger shows once the request has been processed: detection sources and their blind spots, the structural patterns that separate classes of automation, and the write sequence a curve completion produces.

The two sections are two views of one transaction. That is deliberate, because most confusion about launchpad bots comes from mixing the views: reading a log line and calling it a balance, or reading a dashboard summary and calling it a trade. Keeping them apart is most of the method.

How a note gets written

1. Start from something checkable: a public documentation page, a program interface, or a confirmed transaction that can be opened by anyone.
2. Describe the mechanism before drawing any conclusion, and state which deployed version the description belongs to.
3. Mark every number as a protocol constant, an illustrative calculation with stated inputs, or a figure from a named public source. If it is none of those, it does not go in.
4. Separate observation from inference in the writing itself, so a reader can see where the evidence stops.
5. Publish with the build date, and amend in the open when something turns out to be wrong or to have aged out.

What this desk will not publish

• Results. No profit figures, no win rates, no returns, no backtests, no case studies. Mechanism notes that end in a performance claim are a different genre and a worse one.
• Fabricated evidence. No invented statistics, no review counts, no testimonials, no ratings, no wallet figures presented as observations when they are examples.
• Runnable automation. The notes describe what an instruction contains and how to read a trace. They deliberately stop short of assembling anything that could be pointed at a market.
• Permanent specifications. Launchpad programs sit behind upgrade authorities. Any account list, discriminator or constant here is a description of a version, and it says so.
• Named attribution. A trace can show that wallets were funded together and traded together. It cannot show who operated them, and this desk does not pretend otherwise.

On independence

Program Notes is not affiliated with, endorsed by or operated by any launchpad, exchange or automation vendor. It does not display third-party logos or branding. Where a commercial tool is mentioned, it is mentioned because the paragraph is genuinely about the job that class of tool performs, and the mention is a link a reader can ignore without losing the argument.

The site links outward to primary documentation where a claim depends on it, and those links go to stable documentation roots rather than to deep paths that break. When something on this site disagrees with the runtime documentation or with a confirmed transaction, the runtime and the transaction win.

Corrections

Corrections are the part of an editorial policy that matters, because everything else is a promise about the future. If a note here is wrong, the fastest way to fix it is to send the signature that shows it. A confirmed transaction settles a disagreement about program behaviour in a way that no amount of argument does, and the desk would rather amend a page than defend it.

Send corrections through the contact page. Amendments are made to the page itself rather than appended as a note at the bottom, and the modified date on every page reflects the current version. Nothing here is backdated, and no publication date is ever moved forward to make a page look fresher than it is.

Scope, honestly stated

This desk is narrow on purpose. It does not cover trading strategy, token selection, market analysis, or whether any particular launch is worth participating in. It does not rank tools and does not review them. It covers the mechanical layer, which is the part that can be checked, and leaves the rest to people who are willing to be judged on predictions.

If you arrived looking for an argument about whether launchpad automation is a good idea, this is the wrong site. If you arrived wanting to know what a curve buy actually contains, or why a transaction started failing the moment a token migrated, start with the instruction layer and work outwards.