> For the complete documentation index, see [llms.txt](https://docs.adcpcapital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adcpcapital.com/introduction/controlled-pilot.md). # Controlled Pilot ADCP's current deployment is a **controlled pilot** on Base Sepolia, a public Ethereum test network. > **Test assets only. No real value is at risk anywhere in the current deployment.** ## What this proves The BTC-Secured Credit capability (Series 002) runs live: deterministic capital, collateral, credit, reserve, and accounting rules execute exactly as specified, and every state transition and reconciliation figure is observable — not merely asserted after the fact. ## What this does not prove or claim * Production authorization. * Regulatory approval or legal structuring for any real deployment. * That any parameter used in this controlled pilot is the final production value. * Mainnet or real-value readiness of any kind. ## Structural facts about the current pilot * **Network:** Base Sepolia, chain ID `84532`. See [Base Sepolia](/network/base-sepolia.md). * **Protocol Bitcoin Reserve (PBR):** structurally excluded from this pilot — no PBR contract is deployed, and no PBR functionality is reachable. See [Reserves](/protocol/reserves.md). * **Series 001 (Participating Capital):** architecture / specification only. Not a live product. See [Participating Capital](/products/participating-capital.md). * **Series 003 (RWA Product Series):** future product template. No implementation exists. See [RWA Product Series](/products/rwa-product-series.md). ## Trust ladder ADCP does not ask an institution to trust a startup system on day one. The intended progression: a public controlled pilot (where we are today) → external controlled testing → partner shadow mode alongside an existing process → a paid product-design engagement → legal/regulatory role mapping → a capped, qualified production pilot → scale. Each step requires its own separate evidence and authorization before proceeding to the next. --- # 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.adcpcapital.com/introduction/controlled-pilot.md?ask=&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.