The Proof Pack

One real Mendix™ app, authored end-to-end by AI through mxto, and every layer of evidence behind that, downloadable and inspectable. Not stronger claims — the artifacts themselves.

1. The reproducible loop, on Claudius

Claudius is a complete IT asset request tracker (25 entities · 68 microflows · 9 modules · MX 11.6.4) built by an AI agent driving mxto, no Studio Pro in the loop. The whole loop is reproducible from the artifacts below:

Every line above is verbatim captured output (Claudius round-trip, 2026-06-08). The companion “AI adds working logic live” sequence (author → mxbuild 0-CE → behaviour appears, DB-confirmed) is captured on the Comotion app. See the method.

2. Why your AI can read it: the same flow, three ways

This is the core claim, made concrete on one real Claudius flow (ACT_ApproveRequest, all three files in the data pack). Your AI today gets the left column. With mxto it gets the right.

"startNodeId": "2693b9bf-cf9d-…"
"edges": [
 { "originNodeId": "f6167db7-…",
   "destinationNodeId": "11aabc75-…",
   "caseValue": "true" },
 … 8 more edges, each a
   pair of opaque IDs …
]
# no order, no names

flow: ACT_ApproveRequest
params: [Request]
nodes:
  - guard: status in
      (Submitted, InReview)
  - change: Request.Status
      = Approved
  - commit: Request
  - call: CreateAuditEntry
# typed + ordered

flow ApproveRequest(Request):
  if not Request.Status in
      (Submitted, InReview):
    show_warning(…); return
  Request.Status = Approved
  Request.Reviewer = CurrentUser
  commit(Request)
  call(CreateAuditEntry)
  close_page()

Measured with tiktoken o200k_base; resolution counts from the graph's own structure. Reproduce it and the full method: 04-comprehension-benchmark-method.txt. The three files ship in the data pack: ApproveRequest-model-graph.json, ApproveRequest.mir.txt, ApproveRequest.axon.

3. Download & inspect