cayu.evals.scenario
Public Cayu API. Definitions are grouped by their public source module, and definitions from private implementation modules appear on their package’s page; adding a symbol does not move existing links. The import shown at each entry is a supported public namespace. Read the Python API overview and install the required extra.
compile_eval_scenario
Section titled “compile_eval_scenario”from cayu.evals import compile_eval_scenarioCompile portable stimuli without resolving any execution authority.
compile_eval_scenario(scenario: EvalScenarioDocumentV2) -> CompiledEvalScenarioV2Release source · Runtime guarantees · Capability guides
CompiledEvalScenarioV2
Section titled “CompiledEvalScenarioV2”from cayu.evals import CompiledEvalScenarioV2Validated authority-free template consumed by later launch preflight.
Decorators: @dataclass(frozen=True, slots=True).
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
document |
EvalScenarioDocumentV2 |
required |
initial |
ScenarioInitialInputEventV2 |
required |
steps |
tuple[ScenarioQueuedInputEventV2 | ScenarioResumedInputEventV2 | ScenarioApprovalCheckpointEventV2, ...] |
required |
revision (property)
Section titled “revision (property)”CompiledEvalScenarioV2.revision() -> strtarget_key (property)
Section titled “target_key (property)”CompiledEvalScenarioV2.target_key() -> strartifact_requirement (method)
Section titled “artifact_requirement (method)”CompiledEvalScenarioV2.artifact_requirement(requirement_id: str) -> ScenarioArtifactRequirementV2secret_requirement (method)
Section titled “secret_requirement (method)”CompiledEvalScenarioV2.secret_requirement(requirement_id: str) -> ScenarioSecretRequirementV2Release source · Runtime guarantees · Capability guides
eval_scenario_from_json
Section titled “eval_scenario_from_json”from cayu.evals import eval_scenario_from_jsonLoad one bounded scenario-v2 JSON document from text.
eval_scenario_from_json(source: str) -> EvalScenarioDocumentV2Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_ARTIFACT_REQUIREMENTS
Section titled “EVAL_SCENARIO_MAX_ARTIFACT_REQUIREMENTS”from cayu.evals import EVAL_SCENARIO_MAX_ARTIFACT_REQUIREMENTSEVAL_SCENARIO_MAX_ARTIFACT_REQUIREMENTS = 128Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_BYTES
Section titled “EVAL_SCENARIO_MAX_BYTES”from cayu.evals import EVAL_SCENARIO_MAX_BYTESEVAL_SCENARIO_MAX_BYTES = 8 << 20Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_EVENTS
Section titled “EVAL_SCENARIO_MAX_EVENTS”from cayu.evals import EVAL_SCENARIO_MAX_EVENTSEVAL_SCENARIO_MAX_EVENTS = 1024Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_JSON_PART_BYTES
Section titled “EVAL_SCENARIO_MAX_JSON_PART_BYTES”from cayu.evals import EVAL_SCENARIO_MAX_JSON_PART_BYTESEVAL_SCENARIO_MAX_JSON_PART_BYTES = 256 << 10Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_MESSAGES_PER_EVENT
Section titled “EVAL_SCENARIO_MAX_MESSAGES_PER_EVENT”from cayu.evals import EVAL_SCENARIO_MAX_MESSAGES_PER_EVENTEVAL_SCENARIO_MAX_MESSAGES_PER_EVENT = 32Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_PARTS_PER_MESSAGE
Section titled “EVAL_SCENARIO_MAX_PARTS_PER_MESSAGE”from cayu.evals import EVAL_SCENARIO_MAX_PARTS_PER_MESSAGEEVAL_SCENARIO_MAX_PARTS_PER_MESSAGE = 32Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_SECRET_REQUIREMENTS
Section titled “EVAL_SCENARIO_MAX_SECRET_REQUIREMENTS”from cayu.evals import EVAL_SCENARIO_MAX_SECRET_REQUIREMENTSEVAL_SCENARIO_MAX_SECRET_REQUIREMENTS = 128Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_TEXT_CHARS
Section titled “EVAL_SCENARIO_MAX_TEXT_CHARS”from cayu.evals import EVAL_SCENARIO_MAX_TEXT_CHARSEVAL_SCENARIO_MAX_TEXT_CHARS = 65536Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_TOTAL_ARTIFACT_BYTES
Section titled “EVAL_SCENARIO_MAX_TOTAL_ARTIFACT_BYTES”from cayu.evals import EVAL_SCENARIO_MAX_TOTAL_ARTIFACT_BYTESEVAL_SCENARIO_MAX_TOTAL_ARTIFACT_BYTES = 1 << 30Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_MAX_TOTAL_TEXT_CHARS
Section titled “EVAL_SCENARIO_MAX_TOTAL_TEXT_CHARS”from cayu.evals import EVAL_SCENARIO_MAX_TOTAL_TEXT_CHARSEVAL_SCENARIO_MAX_TOTAL_TEXT_CHARS = 1 << 20Release source · Runtime guarantees · Capability guides
EVAL_SCENARIO_SCHEMA_VERSION
Section titled “EVAL_SCENARIO_SCHEMA_VERSION”from cayu.evals import EVAL_SCENARIO_SCHEMA_VERSIONEVAL_SCENARIO_SCHEMA_VERSION = 2Release source · Runtime guarantees · Capability guides
eval_scenario_to_json
Section titled “eval_scenario_to_json”from cayu.evals import eval_scenario_to_jsonReturn deterministic, human-readable scenario-v2 JSON.
eval_scenario_to_json(scenario: EvalScenarioDocumentV2) -> strRelease source · Runtime guarantees · Capability guides
EvalScenarioDocumentV2
Section titled “EvalScenarioDocumentV2”from cayu.evals import EvalScenarioDocumentV2One canonical external-stimulus sequence with no executable authority.
Bases: _SchemaV2PortableModel.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
schema_version |
Literal[2] |
EVAL_SCENARIO_SCHEMA_VERSION |
revision |
StrictStr |
required |
id |
StrictStr |
required |
target_key |
StrictStr |
required |
name |
StrictStr |
required |
description |
StrictStr | None |
None |
source |
EvaluationSourceIdentityV1 | None |
None |
events |
tuple[ScenarioEventV2, ...] |
Field(min_length=1, max_length=EVAL_SCENARIO_MAX_EVENTS) |
artifact_requirements |
tuple[ScenarioArtifactRequirementV2, ...] |
Field(default_factory=tuple, max_length=EVAL_SCENARIO_MAX_ARTIFACT_REQUIREMENTS) |
secret_requirements |
tuple[ScenarioSecretRequirementV2, ...] |
Field(default_factory=tuple, max_length=EVAL_SCENARIO_MAX_SECRET_REQUIREMENTS) |
validate_schema_version_type (method)
Section titled “validate_schema_version_type (method)”EvalScenarioDocumentV2.validate_schema_version_type(value: object) -> objectvalidate_collections_are_ordered (method)
Section titled “validate_collections_are_ordered (method)”EvalScenarioDocumentV2.validate_collections_are_ordered(value: object, info) -> objectvalidate_revision_shape (method)
Section titled “validate_revision_shape (method)”EvalScenarioDocumentV2.validate_revision_shape(value: str, info) -> strvalidate_ids (method)
Section titled “validate_ids (method)”EvalScenarioDocumentV2.validate_ids(value: str, info) -> strvalidate_name (method)
Section titled “validate_name (method)”EvalScenarioDocumentV2.validate_name(value: str, info) -> strvalidate_description (method)
Section titled “validate_description (method)”EvalScenarioDocumentV2.validate_description(value: str | None, info) -> str | Nonevalidate_contract (method)
Section titled “validate_contract (method)”EvalScenarioDocumentV2.validate_contract() -> EvalScenarioDocumentV2create (method)
Section titled “create (method)”EvalScenarioDocumentV2.create(*, id: str, target_key: str, name: str, events: Sequence[ScenarioEventV2], description: str | None=None, source: EvaluationSourceIdentityV1 | None=None, artifact_requirements: Sequence[ScenarioArtifactRequirementV2]=(), secret_requirements: Sequence[ScenarioSecretRequirementV2]=()) -> EvalScenarioDocumentV2Release source · Runtime guarantees · Capability guides
EvalScenarioInspectionV2
Section titled “EvalScenarioInspectionV2”from cayu.evals import EvalScenarioInspectionV2Bases: _SchemaV2PortableModel.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
schema_version |
Literal[2] |
EVAL_SCENARIO_SCHEMA_VERSION |
revision |
StrictStr |
required |
id |
StrictStr |
required |
target_key |
StrictStr |
required |
event_count |
StrictInt |
Field(ge=1, le=EVAL_SCENARIO_MAX_EVENTS) |
input_event_count |
StrictInt |
Field(ge=1, le=EVAL_SCENARIO_MAX_EVENTS) |
approval_checkpoint_count |
StrictInt |
Field(ge=0, le=EVAL_SCENARIO_MAX_EVENTS) |
message_count |
StrictInt |
Field(ge=1, le=EVAL_SCENARIO_MAX_EVENTS * EVAL_SCENARIO_MAX_MESSAGES_PER_EVENT) |
part_count |
StrictInt |
Field(ge=1, le=EVAL_SCENARIO_MAX_EVENTS * EVAL_SCENARIO_MAX_MESSAGES_PER_EVENT * EVAL_SCENARIO_MAX_PARTS_PER_MESSAGE) |
artifact_requirement_count |
StrictInt |
Field(ge=0, le=EVAL_SCENARIO_MAX_ARTIFACT_REQUIREMENTS) |
secret_requirement_count |
StrictInt |
Field(ge=0, le=EVAL_SCENARIO_MAX_SECRET_REQUIREMENTS) |
validate_schema_version_type (method)
Section titled “validate_schema_version_type (method)”EvalScenarioInspectionV2.validate_schema_version_type(value: object) -> objectvalidate_revision (method)
Section titled “validate_revision (method)”EvalScenarioInspectionV2.validate_revision(value: str, info) -> strvalidate_ids (method)
Section titled “validate_ids (method)”EvalScenarioInspectionV2.validate_ids(value: str, info) -> strvalidate_counts (method)
Section titled “validate_counts (method)”EvalScenarioInspectionV2.validate_counts() -> EvalScenarioInspectionV2Release source · Runtime guarantees · Capability guides
inspect_eval_scenario
Section titled “inspect_eval_scenario”from cayu.evals import inspect_eval_scenarioinspect_eval_scenario(scenario: EvalScenarioDocumentV2) -> EvalScenarioInspectionV2Release source · Runtime guarantees · Capability guides
load_eval_scenario
Section titled “load_eval_scenario”from cayu.evals import load_eval_scenarioRead at most the scenario hard limit before decoding or validating JSON.
load_eval_scenario(path: str | Path) -> EvalScenarioDocumentV2Release source · Runtime guarantees · Capability guides
scenario_from_corpus_case
Section titled “scenario_from_corpus_case”from cayu.evals import scenario_from_corpus_caseLift one runnable corpus-v2 case into the scenario-v2 stimulus contract.
scenario_from_corpus_case(corpus: EvalCorpusDocument, case_id: str, *, scenario_id: str | None=None) -> EvalScenarioDocumentV2Release source · Runtime guarantees · Capability guides
ScenarioApprovalCheckpointEventV2
Section titled “ScenarioApprovalCheckpointEventV2”from cayu.evals import ScenarioApprovalCheckpointEventV2Require a new approval decision for a matching current tool call.
The checkpoint identifies an expected pause but contains no approve/deny choice, approval id, actor, or reusable authorization from the source run.
Bases: _ScenarioEventBaseV2.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
sequence |
StrictInt |
Field(ge=0, le=EVAL_SCENARIO_MAX_EVENTS - 1) |
id |
StrictStr |
required |
kind |
Literal['approval_checkpoint'] |
'approval_checkpoint' |
tool_name |
StrictStr |
required |
occurrence |
StrictInt |
Field(default=1, ge=1, le=EVAL_SCENARIO_MAX_EVENTS) |
resolution |
Literal['fresh_decision'] |
'fresh_decision' |
validate_id (method)
Section titled “validate_id (method)”ScenarioApprovalCheckpointEventV2.validate_id(value: str, info) -> strvalidate_tool_name (method)
Section titled “validate_tool_name (method)”ScenarioApprovalCheckpointEventV2.validate_tool_name(value: str, info) -> strRelease source · Runtime guarantees · Capability guides
ScenarioArtifactRequirementV2
Section titled “ScenarioArtifactRequirementV2”from cayu.evals import ScenarioArtifactRequirementV2An immutable file requirement resolved and authorized only at launch.
Bases: _PortableModel.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
id |
StrictStr |
required |
source |
Literal['fixture_digest', 'artifact_reference'] |
required |
reference |
StrictStr | None |
None |
content_sha256 |
StrictStr |
required |
filename |
StrictStr |
required |
content_type |
StrictStr |
required |
size_bytes |
StrictInt |
Field(ge=1, le=MAX_DURABLE_JSON_INTEGER) |
validate_id (method)
Section titled “validate_id (method)”ScenarioArtifactRequirementV2.validate_id(value: str, info) -> strvalidate_content_sha256 (method)
Section titled “validate_content_sha256 (method)”ScenarioArtifactRequirementV2.validate_content_sha256(value: str, info) -> strvalidate_reference (method)
Section titled “validate_reference (method)”ScenarioArtifactRequirementV2.validate_reference(value: str | None, info) -> str | Nonevalidate_filename (method)
Section titled “validate_filename (method)”ScenarioArtifactRequirementV2.validate_filename(value: str, info) -> strvalidate_content_type (method)
Section titled “validate_content_type (method)”ScenarioArtifactRequirementV2.validate_content_type(value: str, info) -> strvalidate_source_reference (method)
Section titled “validate_source_reference (method)”ScenarioArtifactRequirementV2.validate_source_reference() -> ScenarioArtifactRequirementV2Release source · Runtime guarantees · Capability guides
ScenarioEventV2
Section titled “ScenarioEventV2”from cayu.evals import ScenarioEventV2ScenarioEventV2: TypeAlias = Annotated[ScenarioInitialInputEventV2 | ScenarioQueuedInputEventV2 | ScenarioResumedInputEventV2 | ScenarioApprovalCheckpointEventV2, Field(discriminator='kind')]Release source · Runtime guarantees · Capability guides
ScenarioFilePartV2
Section titled “ScenarioFilePartV2”from cayu.evals import ScenarioFilePartV2A file input by immutable requirement id; it never carries file bytes.
Bases: _PortableModel.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
type |
Literal['file'] |
'file' |
artifact_requirement_id |
StrictStr |
required |
validate_requirement_id (method)
Section titled “validate_requirement_id (method)”ScenarioFilePartV2.validate_requirement_id(value: str, info) -> strRelease source · Runtime guarantees · Capability guides
ScenarioInitialInputEventV2
Section titled “ScenarioInitialInputEventV2”from cayu.evals import ScenarioInitialInputEventV2Input used to create the fresh scenario session.
Bases: _ScenarioEventBaseV2.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
sequence |
StrictInt |
Field(ge=0, le=EVAL_SCENARIO_MAX_EVENTS - 1) |
id |
StrictStr |
required |
kind |
Literal['initial'] |
'initial' |
input |
ScenarioInputV2 |
required |
validate_id (method)
Section titled “validate_id (method)”ScenarioInitialInputEventV2.validate_id(value: str, info) -> strRelease source · Runtime guarantees · Capability guides
ScenarioInputPartV2
Section titled “ScenarioInputPartV2”from cayu.evals import ScenarioInputPartV2ScenarioInputPartV2: TypeAlias = Annotated[ScenarioTextPartV2 | ScenarioJsonPartV2 | ScenarioFilePartV2, Field(discriminator='type')]Release source · Runtime guarantees · Capability guides
ScenarioInputV2
Section titled “ScenarioInputV2”from cayu.evals import ScenarioInputV2One bounded batch of caller messages delivered at an explicit lifecycle point.
Bases: _PortableModel.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
messages |
tuple[ScenarioUserMessageV2, ...] |
Field(min_length=1, max_length=EVAL_SCENARIO_MAX_MESSAGES_PER_EVENT) |
validate_messages_are_ordered (method)
Section titled “validate_messages_are_ordered (method)”ScenarioInputV2.validate_messages_are_ordered(value: object, info) -> objectcreate (method)
Section titled “create (method)”ScenarioInputV2.create(messages: Sequence[ScenarioUserMessageV2]) -> ScenarioInputV2Release source · Runtime guarantees · Capability guides
ScenarioJsonPartV2
Section titled “ScenarioJsonPartV2”from cayu.evals import ScenarioJsonPartV2One structured caller input preserved as durable JSON.
Bases: _PortableModel.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
type |
Literal['json'] |
'json' |
value |
Any |
required |
validate_value (method)
Section titled “validate_value (method)”ScenarioJsonPartV2.validate_value(value: object) -> objectfreeze_value (method)
Section titled “freeze_value (method)”ScenarioJsonPartV2.freeze_value(value: Any) -> Anyserialize_value (method)
Section titled “serialize_value (method)”ScenarioJsonPartV2.serialize_value(value: Any) -> AnyRelease source · Runtime guarantees · Capability guides
ScenarioQueuedInputEventV2
Section titled “ScenarioQueuedInputEventV2”from cayu.evals import ScenarioQueuedInputEventV2Input queued while the scenario session is active.
Bases: _ScenarioEventBaseV2.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
sequence |
StrictInt |
Field(ge=0, le=EVAL_SCENARIO_MAX_EVENTS - 1) |
id |
StrictStr |
required |
kind |
Literal['queued'] |
'queued' |
delivery_mode |
Literal['next_turn', 'on_idle'] |
required |
input |
ScenarioInputV2 |
required |
validate_id (method)
Section titled “validate_id (method)”ScenarioQueuedInputEventV2.validate_id(value: str, info) -> strRelease source · Runtime guarantees · Capability guides
ScenarioResumedInputEventV2
Section titled “ScenarioResumedInputEventV2”from cayu.evals import ScenarioResumedInputEventV2Fresh caller input supplied when a scenario session is paused.
manual_recovery is the scenario-v2 wire name for an ordinary explicit
CayuApp.resume(...) interaction. It does not assert or synthesize the
outcome of a runtime tool call whose external effect is unknown.
Bases: _ScenarioEventBaseV2.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
sequence |
StrictInt |
Field(ge=0, le=EVAL_SCENARIO_MAX_EVENTS - 1) |
id |
StrictStr |
required |
kind |
Literal['resumed'] |
'resumed' |
resume_kind |
Literal['user_input', 'manual_recovery'] |
'user_input' |
input |
ScenarioInputV2 |
required |
validate_id (method)
Section titled “validate_id (method)”ScenarioResumedInputEventV2.validate_id(value: str, info) -> strRelease source · Runtime guarantees · Capability guides
ScenarioSecretRequirementV2
Section titled “ScenarioSecretRequirementV2”from cayu.evals import ScenarioSecretRequirementV2A named server-side dependency; no secret value or vault handle is portable.
Bases: _PortableModel.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
id |
StrictStr |
required |
usage |
Literal['provider', 'tool', 'environment', 'artifact', 'other'] |
required |
purpose |
StrictStr |
required |
validate_id (method)
Section titled “validate_id (method)”ScenarioSecretRequirementV2.validate_id(value: str, info) -> strvalidate_purpose (method)
Section titled “validate_purpose (method)”ScenarioSecretRequirementV2.validate_purpose(value: str, info) -> strRelease source · Runtime guarantees · Capability guides
ScenarioTextPartV2
Section titled “ScenarioTextPartV2”from cayu.evals import ScenarioTextPartV2One literal caller-authored text part.
Bases: _PortableModel.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
type |
Literal['text'] |
'text' |
text |
StrictStr |
required |
validate_text (method)
Section titled “validate_text (method)”ScenarioTextPartV2.validate_text(value: str, info) -> strRelease source · Runtime guarantees · Capability guides
ScenarioUserMessageV2
Section titled “ScenarioUserMessageV2”from cayu.evals import ScenarioUserMessageV2One external user message with ordered text, JSON, or file-reference parts.
Bases: _PortableModel.
Fields and attributes
Section titled “Fields and attributes”Defaults below are source expressions; Field(...) includes schema/validation settings and default_factory creates a fresh value. Inherited declarations are included. Constructor behavior follows the model or dataclass shown in the bases/decorators.
| Name | Type | Default |
|---|---|---|
role |
Literal['user'] |
'user' |
content |
tuple[ScenarioInputPartV2, ...] |
Field(min_length=1, max_length=EVAL_SCENARIO_MAX_PARTS_PER_MESSAGE) |
validate_content_is_ordered (method)
Section titled “validate_content_is_ordered (method)”ScenarioUserMessageV2.validate_content_is_ordered(value: object, info) -> objectcreate (method)
Section titled “create (method)”ScenarioUserMessageV2.create(parts: Sequence[ScenarioInputPartV2]) -> ScenarioUserMessageV2