> 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/nexus_workflow.md).

# nexus\_workflow

Execution engine modules for DAG walks, submissions, verification, settlement, failure handling, and lifecycle events.

The Invocation adapter is generated from the public Nexus Move Packages interface for the selected deployment; exact lock, settlement, timeout, and identity signatures are source evidence. Use released bindings and deployed transaction effects to establish external availability.

### Modules

* [era](/talus-docs-v2.1.0/reference/move/nexus_workflow/era.md) - Package era and protocol-version markers.
* [execution](/talus-docs-v2.1.0/reference/move/nexus_workflow/execution.md) - DAG execution state, walks, requests, committed results, failure records, and advancement helpers.
* [execution\_entries](/talus-docs-v2.1.0/reference/move/nexus_workflow/execution_entries.md) - Execution entry and entry-group request construction.
* [execution\_events](/talus-docs-v2.1.0/reference/move/nexus_workflow/execution_events.md) - Workflow event types emitted during execution lifecycle changes.
* [execution\_failure](/talus-docs-v2.1.0/reference/move/nexus_workflow/execution_failure.md) - Failure classes, evidence, post-failure behavior, and normalized error values.
* [execution\_settlement](/talus-docs-v2.1.0/reference/move/nexus_workflow/execution_settlement.md) - Committed-result settlement, timeout recovery, abort, refund, and payment reconciliation helpers.
* [execution\_submission](/talus-docs-v2.1.0/reference/move/nexus_workflow/execution_submission.md) - Leader and tool result submission paths for off-chain and on-chain tools.
* [execution\_verification](/talus-docs-v2.1.0/reference/move/nexus_workflow/execution_verification.md) - Verifier-aware submission checks, worksheet stamps, proof envelopes, and verdict handling.
* [🔌 invocation\_adapter](/talus-docs-v2.1.0/reference/move/nexus_workflow/invocation_adapter.md) - Adapter from workflow vertices to policy-backed Invocation lock, settlement, expiration, and resolution operations.


---

# 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/nexus_workflow.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.