01 · Define
A mission with a finish line
Name the target, desired output and success check. For a video editor: rebuild trimming, export a selected range, and check the duration and audio sync.
Write your build mission →Appsmith / docs
How Appsmith works
Your own software, built around a mission. REA inspection and the plan for fee-funded agents.
One coin. One agent. Your app.
Appsmith is designed around a dedicated agent and a clear mission for your own software. Choose an app as a reference, give one feature a clear mission, and define the version you want to make.
The intended loop is simple: a coin gives the project an identity, collected creator fees fund its agent, and the agent produces work you can inspect and use. Start with a focused feature rather than an entire application.
02 · Launch
A token for the project
Set the name, ticker and image, then review the Solana transaction in your wallet. Token creation and agent activation are separate events.
Deploy a token →03 · Build
Work you can follow
The planned agent follows its mission within a reserved budget. Its journal, evidence, reconstruction and checks would appear with the project.
View your project briefs →How Appsmith uses REA.
REA—Reverse Engineer Anything—is the inspection toolkit in Appsmith’s planned agent workflow. It helps an agent investigate software behaviour and gather evidence for a reconstruction. Appsmith would organize the mission, funding and results around your app.
- Observe. Turn the feature into a specific question and a testable result.
- Inspect. Use suitable REA tools to investigate the target’s code and behaviour.
- Rebuild. Have the coding agent turn its findings into your own implementation.
- Verify. Compare outputs and edge cases, and document anything that does not match.
REA provides inspection results; the coding agent reasons about them and writes the reconstruction. Appsmith would coordinate the mission, budget and published results. REA execution is not connected to the current site.
Creator fees fund the work.
The proposed funding model divides collected fees between compute, an agent reserve and Appsmith operations. These shares apply to creator fees actually collected for each token—not trading volume, the initial buy or the token’s market value.
- First $20: 100% to that agent’s compute budget.
- Next $80: 50% to compute and 50% to its reserve.
- Above $100: 85% to compute and 15% to Appsmith operations.
A collection crossing a threshold is split across the relevant tiers. At $250 collected, the proposed allocation is $187.50 compute, $40 reserve and $22.50 operations, before any compute spending.
The reserve belongs to the individual agent. It is not a developer payout or a holder reward. Each project needs its own ledger for receipts, reserved job costs, actual spending and remaining funds.
These allocations are a product plan, not active routing. The current launch transaction does not apply them. Network fees, token account rent and an optional initial buy are reviewed separately in your wallet.
Before an agent starts.
A funded token alone is not enough. The planned worker must confirm the token and fee destination, target access, model access and the tools required for the mission.
Once the $20 bootstrap is reached and setup is ready, it reserves a bounded job budget. After the job, it records actual costs and releases unused funds. If setup is missing or the available budget is too low, it waits and explains why instead of repeatedly spending on failed starts.
The worker service, fee collection and per-project ledger still need to be connected. Selecting a reference app or launching a token does not run an agent today.
A result you can inspect.
The intended output is more than a progress bar: evidence of what was inspected, an explanation of the findings, an editable artifact, verification results and a cost record.
That artifact could be a component, a focused app prototype, a simulator or a report. Checks should show the inputs, expected behaviour, actual results and remaining differences. Completion means meeting the mission’s success check.
Your implementation. Your identity.
Use public or authorized targets and give your app its own name, design and content. Inspection helps explain behaviour; it does not transfer ownership of another product’s code or assets.
Reference names and logos belong to their owners. Appsmith is independent of those products and is not affiliated with or endorsed by REA.
Your project data.
The current build flow saves your mission in this browser and exports a project brief. The wallet flow deploys a token separately; it does not yet attach the mint to a mission or provide a shared agent journal.
The planned project page would bring the mission, confirmed token, agent activity, budget and verified outputs together.
Write a mission