> For the complete documentation index, see [llms.txt](https://docs.wormbrain.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wormbrain.info/explore-wormbrain/04-lab/audit.md). # audit Every loop should leave a row. If it did not, treat the missing row as a bug. ## What a row holds * Time in the world, and time inside the model * The reduced market numbers that hit the nose * Which sensory cells got current, and how much (capped values) * Command-cell readout: forward, reverse, pause * Decoder intent * Cage result: pass, shrink, or block, with a reason * FOMO print id if something actually landed * Hash of the previous row, so a gap is obvious Tied together, those rows are the decision chain. You can export them from the lab view when the export is on. ## What you can do with an export * Confirm a FOMO print has a matching intent * See how often the cage, not the worm, is doing the work * Compare two days without trusting a screenshot * Check that the pinned connectome id did not quietly change ## What an export cannot do It cannot prove the worm "meant" to get rich. It can only show that a published network, given a published nose map, produced a command, and that a published cage did or did not let it through. {% hint style="info" %} If a social post claims a spectacular trade and there is no row, believe the missing row. {% endhint %} ## Hash chain, in one paragraph Each row includes a fingerprint of the row before it. Change an old number and the fingerprints after it stop lining up. That does not make the project sacred. It makes silent edits harder to get away with. --- # 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://docs.wormbrain.info/explore-wormbrain/04-lab/audit.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.