From Business Requirement to Working Software

Build merchant onboarding.

Each merchant belongs to a platform.
Track tax number, address, external ID,
creation time, and last update time.

Developer or Coding Agent

Clarifies objects, representative values, relationships, constants, ownership, and provider choice, then saves the result as XML/KSML.

The model path—not a chat transcript—is the artifact used for evaluation, review, and regeneration.

<root name="crm-erp-service"
      org="doublechaintech"
      data_service="postgres">

  <platform
      name="CRPERPPlatform"
      create_time="createTime()"
      last_update_time="updateTime()" />

  <merchant
      name="Global Logistics Corporation"
      tax_number="91XXXXXXXXXXXXX"
      platform="platform()"
      create_time="createTime()"
      update_time="updateTime()" />

</root>

Types, relationships, and generation intent

Representative values allow the evaluator and generator to infer supported field types. References such as platform() connect business objects. Metadata can add display names, modules, constants, identifiers, and ownership boundaries.

Evaluation Report
├── Errors       must be fixed
├── Warnings     require a decision
├── Suggestions  optional improvements
└── Solid Areas  preserve these sections

Generation is blocked when the submitted model contains evaluation Errors. Repair the model, evaluate again, and keep the report as evidence.

cargo teaql \
  --input model/main.xml \
  rust-assist-query/merchant

The same pattern supports create, update, delete, expression, list-page, debug, tool API, ensure-schema, and runtime-customization guidance.

Generated AGENTS.md
       ↓
Select language + action + object
       ↓
Call TeaQL assist API with the model
       ↓
Use exact generated methods
       ↓
Compile, test, and request more help