> For the complete documentation index, see [llms.txt](https://b3-flowmesh.gitbook.io/b3-flowmesh-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://b3-flowmesh.gitbook.io/b3-flowmesh-docs/readme.md). # README Follow B3 and FlowMesh development through milestone updates, short videos and reproducible evidence. I explain what changed, what I tested and what still needs work. Videos are hosted on [B3 Flow Mesh on YouTube](https://www.youtube.com/@B3FlowMesh). This GitBook is the written companion, separate from the B3 node repository. No wallet files, private keys, signer journals or large video files belong here. ## First milestone **FlowMesh V2 accounting and restart recovery** covers shared balances, order reservations, agreement under faults and recovery after process interruption. The recorded reproduction passed 332 isolated model tests. These results are not production approval or a latency benchmark. [Watch development diary 01](https://youtu.be/h8OF2ygjLiE). ## Reading the results Each update identifies its evidence and limitations. A model result is not a live-node guarantee; an accepted order is not necessarily a matched trade; a historical demonstration is not current production footage. The goal is to make the progress understandable without hiding the remaining work. --- # 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://b3-flowmesh.gitbook.io/b3-flowmesh-docs/readme.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.