> For the complete documentation index, see [llms.txt](https://docs.urbit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.urbit.org/hoon/zuse.md).

# Zuse

Documentation for the %base desk's /sys/zuse.hoon library, which contains helper functions for the kernel.

Documentation for the `%base` desk's `/sys/zuse.hoon` library, which contains helper functions for the kernel.

Zuse is the farthest downstream component of the kernel in terms of dependency, so its version number is used to represent the version of the kernel as a whole. For example, a new kernel release might be referred to as "408k" to refer to Zuse kelvin version 408.

## 2d: Formatting functions <a href="#id-2d-formatting-functions" id="id-2d-formatting-functions"></a>

* [2d(1-5): To JSON, Wains](/hoon/zuse/2d_1-5.md) - Functions for encoding/decoding line-lists and various JSON encoding functions.
* [2d(6): From JSON](/hoon/zuse/2d_6.md) - Functions for decoding `$json`.
* [2d(7): From JSON (unit)](/hoon/zuse/2d_7.md) - Functions for decoding `$json` to `$unit`s.

## 2e: Web Text Functions <a href="#id-2e-web-text-functions" id="id-2e-web-text-functions"></a>

* [2e(2-3): Print & Parse JSON](/hoon/zuse/2e_2-3.md) - Print `$json` and parse JSON.

## 2m: Ordered Maps <a href="#id-2m-ordered-maps" id="id-2m-ordered-maps"></a>

[2m: Ordered Maps](/hoon/zuse/2m.md) - Functions for creating and working with ordered maps.


---

# 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://docs.urbit.org/hoon/zuse.md?ask=<question>&goal=<user_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.