# What ToggleX Uses and What It Doesn’t ToggleX works from the activity you generate across your tools. It uses the signals of what you open, what you touch and how your attention moves; and these signals form the basis of the Work Mesh. From there, the system uses structure and timing. It relies on the Work Graph to understand which items connect and on the Temporal Lattice Memory to see how work persists, pauses or changes across different moments. TDN works only with structural patterns. It does not store content. It operates on the shapes formed by the fabric to improve how the system handles similar cases over time. The system also does not reorganize your tools or make decisions about your work. It records what happens, forms the structure around it and steps forward only when that structure is useful to see. The work remains in your hands. Chat gives you a way to work inside a project or item without leaving its structure. It can draft material, outline a step or help you continue a thread, and it stays within the boundaries the system has already established. ToggleX uses your activity and the relationships it forms. It does not rely on anything outside these elements, and everything the system shows comes from that foundation. --- # Agent Instructions: 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: ``` GET https://toggle.gitbook.io/togglex/oldgitbook-below/what-togglex-uses-and-what-it-doesnt.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.