File Analysis
Compare exact matrix/casebook/report/catalog/operation identifier-set differences between two valid Phase 82 dossiers.
01 / Tool workbench
The application shell fails closed. An input interface is not enabled merely because a WordPress Tool record exists; the declared engine must be registered in the current build.
No output has been built in this session.
Compare exact matrix/casebook/report/catalog/operation identifier-set differences between two valid Phase 82 dossiers.
Processing is browser-local and deterministic. Phase 82 traceability records exact cryptographic relationships only; ledger order is not chronology and does not establish identity, ownership, authenticity, legal custody or trust.
02 / Compatibility
Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.
Accepted extensions
Platforms
No platform assignment is recorded.
Supported versions / editions
Phase 82 accepts 1-16 strictly valid Phase 81 offline review matrices. Each matrix is capped at 32 MiB and combined input at 128 MiB. Pair dossiers require exactly two distinct matrices. Single-catalog dossiers require every matrix to contain exactly one identical Phase 78 source-catalog ID.
Input constraints
Choose two valid Phase 82 dossiers. Comparison reports exact identifier-set differences only and creates no chronology, trust, provenance-authority or semantic ranking.
Known limitations
Phase 82 creates deterministic local exact-identifier dossiers and traceability ledgers only. Ledger sequence is canonical matrix-ID order, not chronology. It does not establish semantic relevance, duplicate evidence, common origin, causality, authorship, ownership, authenticity, legal custody, authoritative-copy status, trusted time, remote trust, collaboration/account authority, signature validity, restore priority or production acceptance.
Output / result
Deterministic canonical UTF-8 JSON dossiers with SHA-256-bound matrix metadata records, exact identifier axes, trace indexes, canonical non-chronological ledger entries, deterministic Markdown, source/source-set revalidation, lookup, trace, comparison, rebuild and export receipts.
03 / Instructions
File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.
Preserve an untouched copy before creating or transforming binary output.
Match the file size, format, platform, and version to the support information on this page.
Use the runtime only when the page reports that its declared engine is loaded.
Compare or test the result before replacing any working source file.
Tool-specific steps
Select the required local JSON document(s), run Offline Matrix Dossier Comparison Receipt, review the deterministic receipt, and save any exported evidence if needed. Keep the original Phase 81 matrices when later exact source revalidation is required.
04 / Privacy and processing
SaveEditor.com should state local processing only when the implementation truly keeps file contents in the browser. Server or hybrid processing must be disclosed just as clearly.
Declared mode
Runtime state
Tool-specific privacy notes
All Phase 81 matrix revalidation, dossier construction, exact trace indexing, ledger binding, lookup, comparison, rebuild and rendering occur in browser memory. Source matrix/casebook/report/save documents are not embedded, and no upload, remote collaboration, account/cloud access, remote lookup, signing/private-key operation, trusted timestamp, restore, source mutation or live-save write is performed.
05 / Troubleshooting
A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.
Re-check the documented input type and browser size limit before retrying.
A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.
Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.
Known Tool issues
A failed dossier/ledger check means the strict Phase 82 schema, stored record digest, manifest, axes, trace index, ledger link, deterministic Markdown, canonical order, source-set match or dossier ID did not match. Ledger sequence is matrix-ID order only and must never be interpreted as chronology, provenance authority, authorship, ownership, authenticity, legal custody, duplicate evidence or semantic relevance.
06 / Verification
The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.
Method notes
Verified with strict Phase 81 matrix revalidation, independent SHA-256/canonical-JSON references, deterministic ordering/rebuild vectors, duplicate matrix refusal, pair/single-catalog constraint negatives, altered record/manifest/axes/trace/ledger/Markdown/dossier-ID negatives, exact source-set revalidation, source immutability, no-network/no-signing/no-authority guards and source/installable parity.
07 / FAQ
These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.