File Analysis
Look up one exact packet, dossier, matrix, casebook, report, catalog or operation SHA-256 identifier without fuzzy or semantic matching.
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.
Look up one exact packet, dossier, matrix, casebook, report, catalog or operation SHA-256 identifier without fuzzy or semantic matching.
Processing is browser-local and deterministic. Phase 84 records exact cryptographic review-packet relationships and optional self-declared labels only; it does not establish identity, chronology, semantic relevance, origin, ownership, authenticity, custody, trust or authority.
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 84 accepts 1-32 strictly valid Phase 83 review-packet/trace-diff documents. Each packet is capped at 32 MiB and combined input at 256 MiB. Pair diff catalogs require exactly two distinct packet IDs. Self-declared catalog labels, operator notes and event labels are bounded UTF-8 text, hash-bound, and explicitly unverified.
Input constraints
Choose the exact Phase 84 packet-index/diff-catalog JSON requested by this tool. Source revalidation operations additionally require original Phase 83 packet document(s); exact identifier/diff operations require lowercase 64-character SHA-256 IDs.
Known limitations
Phase 84 creates deterministic local exact-identifier review-packet indexes and packet-difference catalogs only. Self-declared catalog labels, operator notes and event labels are unverified hash-bound text, not trusted identity or chronology. Exact packet co-occurrence and differences do 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 packet index/diff catalogs with SHA-256-bound packet metadata records, exact identifier axes/indexes, exact pairwise packet differences, optional self-declared catalog metadata, deterministic Markdown, source/source-set revalidation, lookup, 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
Provide the required local JSON input, run the browser-local deterministic operation, inspect the machine receipt, and export the canonical catalog/Markdown only when the selected profile produces one. Treat all relationships as exact cryptographic metadata relationships only.
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 83 packet revalidation, index-catalog construction, exact identifier indexing, pair-difference computation, declaration binding, comparison, rebuild and rendering occur in browser memory. Source review packets/dossiers/matrices/casebooks/reports/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 Phase 84 packet-index/diff-catalog check means the strict schema, packet record digest, manifest, identifier axes/index, pair-diff row, declaration digest, deterministic Markdown, canonical order, source-set match or catalog ID did not match. Self-declared labels are not trusted identity or event time, and packet co-occurrence/differences must never be interpreted as semantic relevance, duplicate evidence, common origin, causality, chronology, ownership, authenticity, legal custody, trust or authority.
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 83 packet revalidation, independent SHA-256/canonical-JSON references, deterministic ordering/rebuild vectors, duplicate packet refusal, exactly-two-packet pair negatives, declaration bounds/trust-label checks, altered record/manifest/axes/index/diff/declaration/Markdown/catalog-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.