> 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/verification/observable-state.md). # Observable State **Do not trust ADCP first. Verify it beside your existing system.** ADCP does not eliminate audit. It turns more of the underlying economic evidence into continuously verifiable state: collateral, reserves, deployable capital, liabilities, losses, and governance actions become observable inputs to reconciliation, rather than facts that depend on a later human assertion. ## What is directly observable in the current controlled pilot * **Balance-sheet state** — accounted protocol USDC, liquidity reserve, risk reserve, and derived solvency figures, read live from the deployed contracts. * **Credit-position state** — a specific loan's collateral, outstanding debt, health, and eligibility for further action. * **Risk state** — oracle health, credit risk indicators, and treasury risk indicators. * **Custody-vs-accounting reconciliation** — the accounted USDC balance compared against what the treasury contract actually, verifiably holds. ## Where to observe it The live application at [adcpcapital.com](https://adcpcapital.com) exposes all of the above directly — no separate tool or export is required to inspect current state. See [Frontend Integration](/developers/frontend-integration.md) if you want to read the same state independently, from your own tooling. ## What is not yet part of automated observable evidence A dedicated evidence-capture and chain-verification layer for recording human-tester assertions against independently-verified on-chain transaction outcomes exists in the codebase and is being extended for the current pilot's own domain. See [Evidence API](/developers/evidence-api.md) for its current status. --- # 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/verification/observable-state.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.