> 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/releases/changelog.md). # Changelog This changelog covers the public-facing application and controlled pilot, not internal repository/gate history. Entries are derived from the frontend repository's own git history rather than maintained as a separate, hand-written record. ## Unreleased — public commercial layer * Added the public/commercial layer (this documentation's own home application) above the existing protocol/evidence console: product pages for BTC-Secured Credit, Participating Capital, and the RWA Product Series; a controlled-proof page; a partner/product catalogue page. * The application now presents its live functionality (credit, senior-capital, system, risk views) directly, on its own domain, rather than linking out to a separate historical deployment. * Added this documentation site's initial version. ## `external-uat-shell-v1.0-2026-09-12` — public external UAT release The first public, controlled, external-tester release of the current protocol deployment (chain ID `84532`, Base Sepolia), including the institutional visual shell and the full BTC-Secured Credit read/write flow. This tagged release remains preserved as a historical reference point in the frontend repository's own history. ## Earlier history Earlier gate-by-gate engineering history (constitutional design, the accounting core, the credit engine, compliance interfaces, and the initial application layer) is tracked in the protocol repository's own implementation roadmap and is not restated here — this changelog begins at the point the application became externally reachable. --- # 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/releases/changelog.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.