> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soterislabs.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Input records

> The shape of a controlled submission bound to an engagement.

An input record is a controlled submission bound to a single engagement. It carries the material a client, partner, or operator provides so preparation can proceed. Inputs are structured and attributable, not loose files in an inbox.

## Shape

An input record identifies its engagement, its source, when it was submitted, and the documents and context it carries. A minimal, synthetic example:

```json title="input-record.json" theme={null}
{
  "schemaVersion": "0",
  "engagementId": "eng_9f2c",
  "source": "partner",
  "submittedAt": "2026-01-15T18:04:00Z",
  "documents": [
    { "documentId": "doc_a1", "kind": "statement", "label": "Q4 balances" }
  ],
  "notes": "Provided under the agreed mapping.",
  "metadata": { "partnerRef": "PN-4821" }
}
```

## Field notes

* `source` names the submitting actor category: client, partner, or operator.
* `documents` references controlled inputs. File contents are never embedded in the record.
* `metadata` is an open bag for mapping references agreed with the partner.

<Info>
  This shape is conceptual. No public submission endpoint exists in v0. Inputs reach Soteris through the portal or an agreed mapping, per [Integration surfaces](/start/integration-surfaces). Common fields are defined once in the [Field dictionary](/reference/field-dictionary).
</Info>