Skip to content

One DSL Contract

XML is the customer-facing DATAMIMIC model format. It is the descriptor that people edit, review, store in a project, validate, and execute.

XML and DM JSON

DM JSON is a temporary, typed representation used by Agent Authoring while it assembles a model from requirements. It is not a second project format and users do not need to create or maintain it. Agent Authoring compiles the draft to XML; that XML is the final review and execution artifact.

Both representations describe the same model semantics. Conversion succeeds completely or the model is rejected with a diagnostic. DATAMIMIC does not silently drop unsupported elements, attributes, or relationships.

What one contract means

  • The XML editor, element reference, validation, and Agent Authoring use the same allowed elements, attributes, values, and parent-child relationships.
  • The Agent returns XML that can be reviewed and executed in the same way as a manually authored descriptor.
  • Issue and Contract IDs identify the same rule in validation, documentation, and Agent feedback.
  • An element capability is documented once in the generated model reference, not copied into separate hand-maintained catalogs.

Typical workflows

For manual authoring:

  1. Create or edit the XML descriptor.
  2. Validate the XML model.
  3. Review and execute the validated descriptor.

For Agent Authoring:

  1. Describe the intended products, sources, targets, and constraints.
  2. The Agent validates its temporary DM JSON draft and compiles it to XML.
  3. Review the exact XML and its diagnostics before execution.

In both workflows, XML remains the durable, user-facing source of truth.