About the Campaign Desk

Campaign Desk is a planning desk for Solana volume campaigns. It covers one layer: the decisions taken between owning a tool and getting a result out of it that anyone can defend afterwards. The objective, the parameters that express it, the pacing that carries the budget across the window, the stages the run is cut into, and the report the campaign will be marked against.

What the desk does

Every note here answers a planning question. What is this run for, and how would anyone know afterwards whether it happened. How many funded accounts does the flow need to spread across, and what does the answer cost at either end. How large should each trade be relative to the pool it hits. What shape does the spend take across the window, including the final hour. Where does the run pause so that continuing becomes a decision. What does the closing report have to contain, and when is it written.

The format is consistent because the method is. Each parameter is stated as a trade-off with a named failure at the bottom of its range and a different named failure at the top, because there is no value that is correct independently of the objective. Every worked example is arithmetic chosen to show the shape of a calculation, labelled illustrative in the block that carries it, and describing no real pair, run or result.

What the desk leaves alone

Four adjacent subjects are deliberately out of scope, and mixing them into a plan is how plans stop being readable.

• Comparing tools or ranking vendors. That is a purchasing decision and it is answered elsewhere.
• Interface walkthroughs. Which button does what is a property of a product, not of a campaign.
• Key handling, funding routes and incident response. Serious topics with their own literature.
• Building versus buying. A useful argument that has nothing to do with what a run is for.

The desk also does not publish anything that would help conceal activity. The notes here are about designing a campaign you can account for, and a plan whose value depends on nobody being able to read it is not a plan this desk knows how to write.

The rules everything here is written under

These are fixed and they constrain what can appear on any page.

• No promised outcomes. Nothing here says a configuration will produce a result.
• No invented benchmarks, statistics, review counts, ratings or testimonials.
• No named token, wallet, team or venue used as an example of a real campaign.
• No backdated publication dates and no fabricated case studies.
• Every parameter recommendation carries the failure it causes at both ends of its range.
• Every figure in a worked example is labelled illustrative in the block that contains it.

How numbers are handled

Three kinds of number appear on this site and nothing else does. Protocol facts, which are properties of Solana and its programs and are linked to primary documentation rather than asserted. Illustrative arithmetic, which exists to show how a calculation chains together and is marked as illustrative every time. And figures a reader supplies themselves, in a template where the desk provides the structure and the reader provides the values.

What never appears is a measured result presented as typical, a cost figure presented as a market rate, or a threshold presented as an industry standard. This desk has not measured those things, and a number without a method behind it is a claim wearing a number's clothes.

Who writes this

Notes are published under The Campaign Desk, which is the editorial identity of the site rather than a person. There are no invented author biographies here, no photographs, and no credentials attached to anything. The reasoning on each page has to carry itself, and where a claim rests on something external, the page links to the source so a reader can check it directly rather than taking the desk's word for it.

Corrections

If something here is wrong, it gets corrected on the page rather than quietly removed, and the underlying reasoning gets revisited rather than patched. Errors in a planning note usually mean the trade-off was stated in only one direction, which is the specific mistake the format exists to prevent. Corrections and questions go through the contact page.