Case Serialization
Definition
The current Case record includes issued case_id and dataset_record_id, creation/update timestamps, canonical content, content_schema_version, derived content_search_text, legacy_metadata and available latest_version output context.
Canonical content uses schema_version: dataset_record.content.v1, an input container and optional case_materials, world_refs and capability_refs.
Canonical and rendered content
The owning schema defines message or structured-object input and material-block alternatives. Do not flatten these into the earlier proposed input.kind: plain_text envelope or invent another public context object.
A saved Case view is a rendered projection. It does not become another editable canonical payload.
Materials and references
Preserve declared material keys, artifact references and issued identities. Display paths and search text are not content authority.
Source World references are separate from an executable world_instance_ref. A serialized field does not establish a World-management endpoint or durable provisioning workflow.
Outputs and history
Latest reference-output context can include an output and normalized trajectory. It is not the response of every candidate Run. Frozen benchmark Case identities and revisions come from the selected Version's manifest, not a current mutable project read.
Field reference
| Field | Meaning |
|---|---|
case_id, dataset_record_id | Required issued identities |
created_at | Required creation timestamp |
updated_at | Update timestamp when returned |
content | Canonical content object or null |
content_schema_version | dataset_record.content.v1 or null |
content_search_text | Derived search representation or null |
legacy_metadata | Compatibility projection |
latest_version | Available reference-output and trajectory context |
See CaseRecord and DatasetRecordContent in the OpenAPI for nested fields. Optional values remain absent or null as returned.
Frozen evaluation membership
GET /case-manifest returns data.manifest beneath the selected Benchmark Version. Members carry case_id, benchmark_version_case_id, dataset_record_version_id and content. Preserve the exact frozen membership when generating results.