PromenautUse case · Schema transformation
Payment Schema Mapping (SWIFT MT ↔ ISO 20022)
Banks run on decades of undocumented transformation logic that converts legacy SWIFT MT messages into ISO 20022 - the rules are locked inside old systems, and no one holds the full specification any more.
Promenaut reverse-engineers the field-level mapping rules from real message pairs, validates every field against the live output, and produces a documented, reusable package for a human to approve.
From real message pairs to a sealed mapping.
$ promenaut run payment-schem
Single MT202 → pacs.009.001.08 run
Parse the schemas
A deterministic parser reads the block-structured MT message and the target XSD for 100% reliable field extraction, then adds human-readable names, types and formats. No model touches the structural parse.
Infer the mapping
Real source values are correlated against real target values, the transformation rule for each is inferred, and a calibrated confidence score is assigned. A human approval gate follows before validation begins.
Validate every field
Each mapping is replayed against the real output and checked for coverage, schema compliance, type, format and value reproduction. Twenty test cases and a documentation package are generated.
Seal and hand over
A second gate freezes the mapping version and seals it as an immutable snapshot - machine-readable and reusable across every business line that needs the same remap.
What it produced.
Single MT202 → pacs.009.001.08 run
100%
Field coverage across the message.
97.7%
Average mapping confidence, calibrated per field.
~65s
End to end, from brief to sealed package.
Perfect
Pass rate on every validation check.
The pipeline paused at the human approval gate exactly as designed - inferred rules are never auto-shipped.
See it on a workflow you own.
Bring a real process. We'll show what your first agentic workflow looks like on the platform.
