Skip to content
Game save workbench
Local-first tools No installation Support status shown
SAVEEDITOR.COM
Browse tools
DEVICE-LOCAL Favorites and recent pages stay in this browser.

File Analysis

Evidence Catalog ID Verifier

Recompute the SHA-256-bound deterministic catalog ID from the canonical catalog body.

01 / Tool workbench

Use the runtime only when it is actually ready.

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.

Evidence Catalog ID Verifier
BROWSER LOCAL

Checking whether the declared runtime module is loaded. No input has been processed.

Session change summary

No output has been built in this session.

What this Tool does

Recompute the SHA-256-bound deterministic catalog ID from the canonical catalog body.

Offline query boundary

Phase 78 is a local exact-index/query authority only. A catalog match or absence is not a semantic interpretation, relevance ranking, ownership/authenticity proof, remote-origin proof, trusted timestamp, real-world chronology, legal chain-of-custody proof, compatibility decision, restore authorization, or live-save mutation authority. No remote search, account/cloud lookup, upload, signing/private-key operation or source-evidence embedding is performed.

Input contract

Choose one Phase 78 evidence catalog JSON. Canonical record order, record SHA-256, manifest SHA-256, deterministic inverted indexes, index SHA-256 and catalog ID are recomputed locally.

Safe interpretation

Exact indexed equality can locate cryptographic or literal values already present in a deterministic local catalog. It cannot infer intent, meaning, relevance, authorship, provenance truth, chronology, ownership, origin or trust.

02 / Compatibility

Know the supported input before opening a file.

Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.

Accepted extensions

json

Platforms

No platform assignment is recorded.

Supported versions / editions

Phase 78 catalogs accept 1-64 strictly valid Phase 77 deterministic archive JSON documents. Each selected archive is capped at 12 MiB canonical JSON and combined selected input at 64 MiB. Catalogs store deterministic metadata/index records only; they do not embed source evidence documents or save bytes.

Input constraints

Choose one Phase 78 evidence catalog JSON. Canonical record order, record SHA-256, manifest SHA-256, deterministic inverted indexes, index SHA-256 and catalog ID are recomputed locally.

Known limitations

Phase 78 is a local exact-index/query authority only. A catalog match or absence is not a semantic interpretation, relevance ranking, ownership/authenticity proof, remote-origin proof, trusted timestamp, real-world chronology, legal chain-of-custody proof, compatibility decision, restore authorization, or live-save mutation authority. No remote search, account/cloud lookup, upload, signing/private-key operation or source-evidence embedding is performed.

Output / result

Canonical UTF-8 JSON evidence-catalog indexes and deterministic exact-query/comparison receipts. Records, catalog manifest, inverted indexes and catalog ID are SHA-256-bound.

03 / Instructions

Use a reversible workflow.

File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.

  1. 01Keep the original

    Preserve an untouched copy before creating or transforming binary output.

  2. 02Confirm scope

    Match the file size, format, platform, and version to the support information on this page.

  3. 03Process locally

    Use the runtime only when the page reports that its declared engine is loaded.

  4. 04Validate output

    Compare or test the result before replacing any working source file.

Tool-specific steps

Choose the Phase 78 catalog, verify it locally, and save the generated receipt. PASS proves deterministic catalog consistency only.

04 / Privacy and processing

The processing mode is part of the product contract.

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

Browser local

Runtime state

Operational

Tool-specific privacy notes

All catalog construction, verification, source-archive revalidation and exact querying occur in browser memory. No upload, remote search, account/cloud access, registry lookup, trusted timestamp, certificate lookup, key generation, digital signing, evidence extraction to disk, restore, or live-save write is performed.

05 / Troubleshooting

When a file is rejected, do not force it.

A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.

Wrong file or size

Re-check the documented input type and browser size limit before retrying.

Unsupported format

A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.

Source was modified

Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.

Known Tool issues

A failed catalog check means the strict Phase 78 schema, source Phase 77 archive validation, record digest, canonical order, inverted indexes, catalog manifest, catalog ID, exact query value or supplied source archive set did not match. Do not infer meaning, relevance, chronology, ownership, origin, authenticity or legal custody from a match or miss.

06 / Verification

Support claims should be traceable.

The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.

Last verified2026-08-11
Profileevidence-catalog-id-verifier

Method notes

Verified with independent SHA-256/canonical-JSON reference calculations, exact-query vectors, malformed/tampered catalog negatives, strict Phase 77 source revalidation, UTF-8 byte path ordering, duplicate archive-ID refusal, deterministic rebuild equality, source immutability, no-network/no-semantic-inference guards, and source/installable parity.

07 / FAQ

Questions to answer before editing.

These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.

Is Evidence Catalog ID Verifier ready to use?
The Tool record is verified and declares an operational runtime. The page enables its input controls only when the declared engine module is loaded in the current build.
Does processing stay in the browser?
Yes for this declared mode. The loaded runtime processes the explicit input in the browser; Tool-specific privacy notes describe the exact scope and limits.
Should I keep the original file?
Yes. Keep an untouched source file until any generated output has been validated.
What if my input is rejected?
Use the validation message to correct the base, encoding, width, timezone, byte alignment, or size. The runtime does not guess through invalid input.