Elysia Tools
Navigation
Workflow Playbook
Compare two candidate artifacts, choose the right diff path for the format, review structural or semantic changes, and finish with integrity checks when approval needs byte-level certainty.
Hubs
This workflow is for situations where two candidate artifacts need an approval-ready comparison. The honest first step is to classify what the artifacts are. A markdown revision, a CSV export, an OpenAPI contract, a screenshot pair, and an AGEX bundle all need different evidence, even though they are all 'diff' problems.
For text-heavy files, start with text-diff; for spreadsheets and exports, use csv-excel-diff-tool; for JSON payloads, start with json-diff-visualizer; for document or media outputs, use pdf-diff, image-difference, or audio-diff. This first pass should answer where the meaningful deltas actually live.
Raw diffs are often too noisy for a real decision. Use diff-formatter to clean up textual patches, pretty-json-diff for field-level JSON changes, difference-arrays for membership changes, and environment-config-diff-visualizer when the question is whether deployment settings drifted. If compatibility matters more than literal file edits, escalate to database-schema-diff, openapi-diff-breach-detector, or api-response-diff-semantic-analyzer.
Before approval, decide whether you need perceptual review or byte-level proof. responsive-breakpoint-diff is for layout regressions across breakpoints. checksum-comparator and hash-algorithm-comparator confirm exactness at the digest level. agex-bundle-diff is for encrypted bundle packaging changes, not ordinary content review. A good final report names the artifact type, the comparator branch used, the important changes found, and whether the result is readable review evidence, compatibility evidence, or integrity evidence.
Workflow playbook
Start with the closest content-level comparison for the actual format so the reviewer sees real edits instead of a generic binary mismatch.
When raw diff output is noisy, reformat or narrow the comparison so key line edits, JSON field moves, array differences, or config value changes become readable and attributable.
If the question is compatibility rather than raw content, compare database schemas, OpenAPI contracts, or real API responses to identify breaking changes and semantic drift.
Finish with responsive layout review or byte-level checks when the release gate depends on visual regressions, exact hashes, or observable AGEX bundle changes.
Choose text or tabular content for documents, logs, markdown, CSV, or spreadsheets; choose structured payloads for JSON, arrays, or environment configs; choose contract review for database schemas, OpenAPI files, or paired API responses; choose media review for PDF pages, images, audio, or responsive layouts; choose integrity review when the key question is whether bytes, hashes, or AGEX bundles match expected changes.
Use formatter, schema, semantic, and media branches when a reviewer must understand what changed. Use checksum, hash, or AGEX bundle diff when the acceptance gate depends on exact bytes or packaging state.