> For the complete documentation index, see [llms.txt](https://docs.talus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talus.network/talus-docs-v2.1.0/reference/move.md).

# Move reference

{% hint style="info" %}
**Audience:** Nexus Move and transaction integrators.
{% endhint %}

**Generated from:** the public Nexus Move Packages interface for the selected deployment (generated — do not hand-edit module signatures). Exact command and binding execution still requires a client and network whose package graph matches this source.

For consumer TAP and on-chain Tool installation or dependency work, complete [Prepare for On-Chain Development](/talus-docs-v2.1.0/guides/getting-started/prepare-onchain-development.md). It records the six public Move Registry dependencies, source/provenance links, `Move.lock` requirement, and selected-network package-ID check. This generated reference records executable Nexus package behavior and may include runtime implementation details; it is not a substitute for the public native interface packages and must not turn generated reference paths into consumer dependencies.

Many public signatures accept `nexus_kernel` runtime authority or permit values. This Reference does not publish a kernel module family and the public Move Registry has no `@talus/nexus-kernel` or `@talus/nexus-policy` record: obtain those authority values only through matching SDK/CLI transaction flows and the selected network’s RuntimeAuthority root. A signature is source evidence, not evidence that an application can construct or substitute its authority argument.

* [`nexus_primitives`](/talus-docs-v2.1.0/reference/move/nexus_primitives.md) — Protocol, data, proofs, ownership, and shared primitives.
* [`nexus_interface`](/talus-docs-v2.1.0/reference/move/nexus_interface.md) — Agent, DAG, authorization, payment, and verifier interfaces.
* [`nexus_tool`](/talus-docs-v2.1.0/reference/move/nexus_tool.md) — Tool registry, Tool objects, cashiers, and package-pointer migration.
* [`nexus_registry`](/talus-docs-v2.1.0/reference/move/nexus_registry.md) — Agent/leader/network registries and the priority-fee vault.
* [`nexus_workflow`](/talus-docs-v2.1.0/reference/move/nexus_workflow.md) — Execution, submission, verification, settlement, and recovery.
* [`nexus_scheduler`](/talus-docs-v2.1.0/reference/move/nexus_scheduler.md) — durable Task, occurrence, and schedule lifecycle.
* [`nexus_policy`](/talus-docs-v2.1.0/reference/move/nexus_policy.md) — standalone policy DFA extension.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talus.network/talus-docs-v2.1.0/reference/move.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 `build a script that syncs our docs to a CMS` 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.