Round-Trip Check

OIM Fact-Table Viewer

Paste or drop an ocg-xbrl-json@1 export (OCG SPEC.md §13.13) to see its facts, dimensions, and units as a table, check canonicalValues + JCS conformance, and verify the execution_hash metadata against the original artifact. Built for the CbCR, Pillar Two, and Call Report personas re-checking an export before it leaves their hands.

🔒 All inputs are processed locally in your browser. Nothing is uploaded, cached, or stored. Reload the page and every field is gone. Do not enter real personal data; use synthetic or anonymised inputs only.
Scope: read before relying on this
This is a round-trip check against our own export, not an XBRL conformance authority. It confirms the export is internally well-formed (canonical JSON, JCS key order) and that its cited execution_hash matches the artifact it claims to come from. It does not perform DTS discovery, XDT dimensional validation, or formula-linkbase execution, and it is not a submittable wire format for any regime (FFIEC submission is XBRL 2.1 XML; EBA is xBRL-CSV; SEC/ESEF is iXBRL; see SPEC.md §13.13.3). For full taxonomy-aware OIM/XBRL conformance, use a certified processor such as Arelle (Apache-2.0). The execution_hash check below verifies a binding, not a re-execution of the underlying kernel; see SPEC.md §17.2: an advisory published claim, not a cryptographic proof of execution.
1 · ocg-xbrl-json export

Paste the export JSON, or drop a .json file. Read locally, never transmitted.

2 · Original artifact (optional)

Paste the source OCG §4 artifact this export was generated from (the one with policy_parameters / output_payload / execution_hash) to verify the export's cited hash actually matches it. Leave empty to check the export's hash metadata for well-formedness only, a weaker, format-only check.

Facts, dimensions, units
canonicalValues + JCS conformance
execution_hash metadata verify