> For the complete documentation index, see [llms.txt](https://docs.taptap3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taptap3d.com/testing-and-support/changes.md). # Documentation changes Dated changes to Taptap3D developer documentation, with proposed contract changes distinguished from product releases. This log records documentation changes. It is not a product release log. No production public listing API, embed or SDK has been released. ## 8 October 2026 * Added the developer introduction, record model and current capability status. * Documented a proposed public listing contract, approved revisions, withdrawal behaviour and iframe messages. * Added runnable synthetic examples for a local iframe and server-side rendering. * Organised navigation into getting started, concepts, integration guides, proposed reference, testing/support and project information. * Added local quickstart expectations, access/environment distinctions and troubleshooting. The contract remains a proposal. Hostnames, origin registration, quotas, image withdrawal and compatibility policy require implementation and verification before a live integration. When a public service ships, entries will distinguish documentation-only edits from released behaviour and link to any migration instructions needed for a client change. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.taptap3d.com/testing-and-support/changes.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 `build a script that syncs our docs to a CMS` 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.