> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/id/memulai.md).

# Memulai

- [Apa itu Rome?](https://docs.rome.builders/id/memulai/what-is-rome.md): Rome adalah lingkungan eksekusi EVM di dalam Solana. Apa pun yang Anda bangun terbuka untuk pengguna EVM, pengguna Solana, dan pengguna di chain lain. Empat cara untuk membangun.
- [Mengapa Rome?](https://docs.rome.builders/id/memulai/why-rome.md): Bagaimana Rome berbeda dari pendekatan EVM-on-Solana lainnya — komposabilitas CPI atomik, satu state bersama, dan sovereign app chain dengan token gas kustom.
- [Arsitektur](https://docs.rome.builders/id/memulai/architecture.md): Bagaimana komponen Rome saling terhubung — eksekusi EVM di dalam program Solana.
- [Ekosistem & repos](https://docs.rome.builders/id/memulai/ecosystem.md): Setiap repo Rome publik, apa fungsinya, dan bagaimana semuanya tersusun — peta untuk menavigasi permukaannya.
- [Quickstart](https://docs.rome.builders/id/memulai/quickstart.md): Deploy kontrak Solidity pertama Anda di Rome dalam waktu kurang dari 5 menit.
- [Konsep Utama](https://docs.rome.builders/id/memulai/key-concepts.md): Istilah penting Solana dan Rome EVM untuk pengembang — program, akun, PDA, CPI, token SPL, serta eksekusi atomik vs. iteratif.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rome.builders/id/memulai.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
