What changed in production—and who shipped it?
An audit report for IBM i shops. See recorded object changes, who made them, and whether the same person last committed the source. Coverage first. Conclusions second.
IBM i 7.4 L25+, 7.5 L4+ or 7.6. Runs on your workstation, not on the production system. Verify SHA-256 checksums.
Export your window
Your existing
*AUDIT-authorized security officer reviews the SQL script, sets the window and libraries, and saves one CSV. No new special-authority grants.Describe your shop
Start with the sample configuration. Map production libraries, people, profiles and developer roles. Optionally point at a complete local Git clone.
Read the evidence
Open
report.html: receiver gaps and audit settings, findings, then every recorded change by application. No missing window gets called clean.
An audit handoff, not another platform.
changeward report --extract extract.csv --config changeward.yaml \ --repo /path/to/local/clone --out audit-window
report.html for reading and printing · findings.csv for investigation · manifest.json for input/output hashes · summary.json for counts without names.
Git is optional. Audit settings are current snapshots, not proof they stayed enabled throughout the past. The report is not a compliance certificate; hashes are not digital signatures. Column semantics have been checked against documentation and synthetic fixtures, not a live QAUDJRN. The first real pilot export is the integration test.
Coverage before conclusions.
A generated report from a fictional three-developer shop. The full recorded set stays visible in print; no scripts or remote assets are needed.
Run it on a real audit window.
We need a shop with an active auditor to try the free report. Send summary.json—counts only, no names, profiles, libraries or objects—and tell us where the report helped or failed. Do not send your extract or configuration.