Load a fictional product or contact sample, or a JSON file you already hold. Supply explicit field pointers and a bounded schema. The worker reports usable records, missing and invalid fields, ambiguous mappings, and exact source provenance.
This is not identity, legal, or product-truth verification. It does not choose a first entity, follow sameAs, coerce types, fetch a schema, call an LLM, or persist your files. Selecting a new sample or file cancels any in-flight run.
§ 01Local admission
Bounded JSON, mapping, and schema, admitted before projection.
Extraction JSON is limited to 1 MiB; mapping and schema files to 64 KiB each. UTF-8 decoding, JSON parsing, depth/node accounting, and projection run in a replaceable worker away from the interface thread. Duration is capped at eight seconds.
Already-delivered JSON only · maximum 1 MiB.
Explicit JSON Pointers. No first-entity choice. Maximum 64 KiB.
Local JSON Schema 2020-12. No remote $ref. Maximum 64 KiB.
§ 02Records and provenance
Inspect usable rows, then the missing, invalid, and ambiguous remainder.
- Status
- Kind
- Counts
- Input digest
- Disclaimer
Usable records
Missing, invalid, and ambiguous
§ 03Reviewed handoff
Only a short summary may leave this page.
Raw extraction JSON, mappings, schemas, and field values stay in this tab. Review the bounded summary, then explicitly open the existing trial brief. That separate page still requires its own human approval before preparing contact. No new formation offer or hosted SKU is created here.