Arete documentation
From idea to application
For the complete documentation index optimized for AI agents, see llms.txt or llms-full.txt. A markdown version of this page is available by appending.mdto the URL or sendingAccept: text/markdown.
For AI agents: the documentation index is at llms.txt (full corpus: llms-full.txt). A markdown source for this page is /getting-started/from-question-to-app.md.
Start with what people need to do. For a raise, that might be “a creator opens it, wallets contribute before a deadline, and each contributor can act on the outcome.” Use that workflow to decide whether to integrate an existing protocol or build your own.
1. Find the pieces
Section titled “1. Find the pieces”Search callable Arete Protocols with a4 protocol search and inspect a listing
with a4 protocol show <slug>. If a published protocol fits, use its exact
package descriptor and install its client.
For a new composition, discover underlying programs and live data by intent:
a4 explore catalog --query "<product intent>" --jsona4 explore catalog program <slug> --jsona4 explore catalog stack <slug> --jsonInspect supported modes, program interfaces, and SDK targets. MCP can help you look at live data before committing to a model. Curated knowledge is context; exact descriptors and program rules determine what can be built and enforced.
2. Define the protocol
Section titled “2. Define the protocol”Initialize with a4 protocol init. Install programs, import their generated
modules, and describe the protocol’s steps, arguments, guards, and authority.
Model one occurrence as an instance, and per-wallet progress as participants
when needed. Prefer instruction templates; add a handler for construction
that cannot be expressed declaratively.
First protocol · Definition guide
3. Exercise it in a mainnet fork
Section titled “3. Exercise it in a mainnet fork”Run a4 dev up. Test each role, successful actions, expected rejections,
deadlines, and terminal states with dev wallets. Inspect the generated stack
and use checkpointing, replay, and scenarios to reproduce interesting cases.
The protocol and your custom stacks run against the same environment.
4. Build the interface alongside it
Section titled “4. Build the interface alongside it”Use the generated protocol client from the local build. Display current state, show wallet-specific actions and rejection reasons, and implement prepare/inspect/sign/submit with clear pending and failed states.
Add custom live views for data the interface needs beyond the protocol’s own instance and activity views. Standalone Program SDKs and stacks can share the same application session.
Connect the app · React integration
5. Deploy, publish, and verify
Section titled “5. Deploy, publish, and verify”Production deployment is explicit and separate from the dev loop. Choose fees
and resources, obtain review when required, and inspect activation status.
Then verify the installed package points at the intended production deployment.
Use a4 install --check in CI to catch clients still marked as local builds.
An active private deployment, a published package, and a public listing are separate milestones. Request listing only when public access and its other requirements are satisfied.
Keep using the pieces you need
Section titled “Keep using the pieces you need”A data-only application can use live views without authoring a protocol. An integration that needs only account readers or transaction builders can use a Program SDK directly. Follow Programs and Live views for those standalone paths.