> 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/reference/move/nexus_scheduler/era.md).

# nexus\_scheduler::era

* [Struct `RuntimeV1`](#struct-runtimev1)
* [Struct `WorkAdmissionV1`](#struct-workadmissionv1)
* [Struct `V1`](#struct-v1)

### Struct `RuntimeV1`

Runtime identity introduced by the first Scheduler facade release.

This type is distinct from \[[`V1`](#nexus_scheduler_era_V1)]: it selects system effect authority, while \[[`V1`](#nexus_scheduler_era_V1)] controls mutation of durable Scheduler objects.

```move
public struct RuntimeV1 has drop
```

<details>

<summary>Fields</summary>

</details>

#### Struct `WorkAdmissionV1`

Validation contract selected by Tasks created through the first proposal API.

This type identifies admission semantics. It is not evidence that a particular package or function constructed a Task.

```move
public struct WorkAdmissionV1 has copy, drop, store
```

<details>

<summary>Fields</summary>

</details>

#### Struct `V1`

Version one Scheduler package witness.

```move
public struct V1 has copy, drop, store
```

<details>

<summary>Fields</summary>

</details>


---

# 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/reference/move/nexus_scheduler/era.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.