> For the complete documentation index, see [llms.txt](https://yvechat.gitbook.io/wp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yvechat.gitbook.io/wp/resources/release-readiness.md). # Release Readiness Public distribution of YveChat Engine depends on the items below. Each is Planned, and each is recorded here so the gap between the current state and a public release stays visible. YveChat Engine runs on a user's machine with that user's privileges and holds their conversations, so distribution integrity forms part of the product itself. *** ### Checklist | # | Item | Requirement | Status | | - | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ------- | | 1 | Installer signing | Every build code-signed for its platform, using keys held under documented custody | Planned | | 2 | Notarization | macOS builds notarized so they install without a security override | Planned | | 3 | Checksums | A published hash for every artifact, and documented steps to verify one before installing | Planned | | 4 | Supported platforms | The exact operating system versions tested and supported, stated plainly, with untested combinations named | Planned | | 5 | Browser tests | Pairing verified on Chrome, Edge, Firefox, and Safari, including the local-network permission flow and the behavior when it is declined | Planned | | 6 | Security review | An independent review covering pairing, token storage, origin policy, local session handling, and the local gateway | Planned | | 7 | Privacy verification | Observed confirmation that prompts, conversations, and profiles reach no YveChat-operated server, recorded as reproducible evidence | Planned | | 8 | Rollback | A documented path to reinstall a previous version, with a statement of what happens to stored conversations | Planned | *** ### Dependencies between items Checksums depend on installers existing. Browser tests depend on an installable build. Rollback depends on more than one published version. Signing and notarization gate public distribution entirely, since an unsigned build asks users to override their own operating system's protections. Items 6 and 7 stand independent of the others and can begin against the current source. *** ### What ships before the checklist completes YveChat Engine is buildable from source today. That path suits developers and operators who are comfortable compiling and running their own software, and it carries no signing guarantee. Public installers begin when items 1 through 5 are complete. Items 6, 7, and 8 follow. *** ### Verification of this page The statuses above are reported from the product facts supplied on 2026-08-06. Independent confirmation against the implementation is outstanding, and this page updates as each item is completed and evidenced. {% hint style="warning" %} Until release artifacts exist, no download origin for YveChat Engine is authoritative. Any installer presented as YveChat today comes from somewhere other than this project. Canonical origins are listed on [Verified Links](/wp/resources/verified-links.md). {% endhint %} --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://yvechat.gitbook.io/wp/resources/release-readiness.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.