swarm-sie-agent

You can audit SIE4 files for encoding and data integrity by running a read-only analysis that checks record coverage across #VER, #TRANS, #IB, and #UB, while detecting CP437, Latin-1, and UTF-8 encoding issues to ensure text integrity.

A read-only SIE4 audit verifies multi-year migration continuity by checking original voucher numbers and record coverage across primary and secondary SIE files without writing data, creating tickets, or committing any code changes.

Checking SIE4 export correctness requires validating the presence and structure of mandatory record types including #VER, #TRANS, #IB, #UB, #SRU, #FNAMN, #ORGNR, and #DIM to ensure complete and accurate file generation.

Yes, the SIE4 audit process detects mojibake by analyzing text integrity across CP437, Latin-1, and UTF-8 encodings, ensuring character data remains robust and correctly mapped during file imports and exports.

You can run a safe SIE4 file analysis using a non-destructive audit approach that preserves original data by strictly avoiding writes, ticket creation, and code commits throughout the entire verification process.

The limitation of a read-only SIE4 audit is that it can identify encoding errors, missing records, and migration gaps but cannot automatically fix them, requiring manual intervention to correct any detected data integrity issues.