DialogueDefinitionApplication

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

# Dialogue Definition Application and Clone Modes

The Editor importer applies typed DialogueDefinition documents transactionally. It parses into detached typed values, performs semantic and provider-payload validation, stages a complete candidate, then commits the selected operation. A failed application reports diagnostics and does not leave partial asset mutation.

Current Definition schema

DialogueDefinition interchange schemaVersion 3 contains a single generic Check representation. The Check carries stable ResolutionProfileId, semantic value source, authored base value, optional Skill identity and role, comparison and target/range, ordered scalar inputs, outcome IDs, retry policy, and optional reset-condition identity.

The importer validates the stable profile identifier and generic owner semantics. It does not load a resolution profile, probability rules asset, random stream, or external provider. Schema versions 1 and 2 are unsupported because no production data requires migration.

Application modes

• UpdateExisting preserves the current asset identity and applies authored changes transactionally.
• CreateNewPreservingIdentity creates another asset with the same stable owner identities.
• CreateNewIndependentClone allocates new Dialogue-local identities and remaps Dialogue-owned references, including participant role references and graph routing.

External provider payloads are reconstructed only by a registered typed adapter for the declared provider ID, payload type ID, and schema version. The generic importer does not interpret external owner payloads. It does not mutate another plugin’s state or save packages automatically.

Validation and save behavior

Detached parse and validation failures occur before mutation. Application failures restore the prior semantic state. Successful operations mark the asset package dirty; the caller chooses when to save it. Dialogue Set and LineDelivery retain their corresponding owner-specific typed interchange contracts.

See DataInterchangeTooling.md for the editor workflow and DialogueSkillInterchangeContract.md for the generic Check JSON fields.