DataInterchangeTooling

Review draft. This source page has not completed website editorial and release-specific verification.

# Data and Interchange Tooling (Dialogue 2.1.0)

The Data and Interchange surface provides typed authoring data, validation, JSON import/export, and constrained CSV bundles. The graph remains the primary Dialogue authoring surface.

Canonical Definition JSON

DialogueDirector.DialogueDefinition schemaVersion 3 is the current typed Definition schema. It contains one generic Check node representation. A Check carries stable profile identity, semantic value source, authored base value, optional Skill identity and participant role, comparison and target/range, ordered scalar inputs, outcomes, retry policy, and optional retry reset condition.

ResolutionProfileId is a stable identifier. Dialogue structural validation checks its form and does not require an Editor provider. If one is installed, separate provider validation may add diagnostics; none of its descriptors or diagnostics are serialized. Check interchange does not contain provider implementation settings. Schema versions 1 and 2 are rejected as unsupported; this unshipped data has no migration reader.

Import and application use detached parsing, typed semantic validation, and transactional application. A failed application does not partially mutate the asset. The importer does not create Gameplay Tags or external owner state.

CSV bundles

CSV is a constrained projection over immutable canonical document.json and its SHA-256 base. Check payloads, participant references, routing, retry data, Conditions, Actions, and external provider payloads remain canonical JSON. A stale base is rejected and malformed projection edits do not return a partial document.

Owner and provider boundaries

Dialogue owns its Definition, localized FText identities, graph flow, generic Check semantics, and Dialogue-local stable identities. Typed provider payloads are interpreted only by registered owner adapters identified by stable provider ID, payload type ID, and schema version.

Optional owner integrations provide their own typed payload codecs. An optional Editor resolution provider may supply profile display data, but Dialogue interchange does not encode provider configuration. The base Dialogue Editor remains useful with no provider installed.