DialogueSkillInterchangeContract
Review draft. This source page has not completed website editorial and release-specific verification.
# Dialogue Skill and Check Interchange Contract (2.1.0)
DialogueDefinition typed interchange uses schemaVersion 3. Checks use one generic owner schema. Dialogue owns semantic intent, participant-role identity, routing, retry state, and history; Skill Director owns Skill values and progression; the external resolution provider owns mechanics.
Generic Check representation
Section titled “Generic Check representation”A generic Check node serializes a stable checkId, resolutionProfileId, valueSourceKey, baseValue, skillId, skillParticipantRoleId, comparison, target, rangeEnd, ordered scalarInputs, successOutcome, failureOutcome, retryPolicy, and retryResetConditionId.
The Skill fields are populated only when valueSourceKey is Skill. Dialogue validates the stable profile ID shape and does not query a provider registry. The profile ID is independent of graph position and does not encode mechanics.
Check authoring contains no D20, D100, NdM, dice, advantage, probability percentage, Probability rules asset, stream policy, decision policy, bias, or Probability status.
Skill and participant semantics
Section titled “Skill and participant semantics”A Skill-sourced Check uses exact Skill identity and a stable participant role ID in the active Dialogue frame. SubDialogue role mapping projects the explicit immediate-caller binding. Dialogue acquires the effective Skill value through the optional Skill query service; Skill Director remains authoritative.
Copy/paste and UpdateExisting preserve semantic identities. Independent clone remaps Definition-local participant references and graph identities according to their owner policies. Runtime results, provider internals, and Preview state are not authored interchange data.
Strict typed schema
Section titled “Strict typed schema”The canonical codec requires exact field sets, strict tokens, typed numeric values, valid stable identities, and valid ordered scalar inputs. Schema 1 and schema 2 are unsupported and rejected; no migration parser is provided for unreleased data. Application remains transactional and reports validation diagnostics before commit.
CSV boundary
Section titled “CSV boundary”CSV is a constrained projection. Check semantics, Skill fields, retry settings, Conditions, Actions, connections, and external provider payloads remain in immutable canonical document.json. Supported CSV edits are applied to a copy only after the canonical base digest matches; stale or malformed bundles fail without partial application.
Provider boundary
Section titled “Provider boundary”At runtime Dialogue acquires any Skill value it owns the right to query, then dispatches a neutral request through IDialogueResolutionProvider. Optional DirectorBridge Dialogue.Probability ContractVersion 3 may provide Probability mechanics. Dialogue interchange does not encode the Bridge implementation, Probability strategy, provider object, or integration settings.