MCP · T848 · Audit Evidence

Tie-Out Workbench

Drop a CSV or JSON file, click the value you used, and name the tool input it feeds. The page builds an ocg-document-span@1 sidecar record per mapping: the SHA-256 of the file bytes, the exact cell or RFC 6901 pointer, the extracted string, and the declared normalization rule. Export the batch as a spans file and attach it at verify time on the Artifact Verifier's tie-out block. Everything runs in this page; the file never leaves your browser.

Reliance: 🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only. A span records where a value sat in a file you supplied; the claim it supports is stated on the exported record and nothing more. Deterministic logic · zero PII · runs offline · CC BY 4.0.
CSV + JSON ocg-document-span@1 Zero PII Client-Side
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
1 · The document
Drop a .csv or .json file here, or click to choose one.
Read into memory with the File API; released when the page closes.
No file loaded.
2 · Click the value you used
Load a file first. For CSV the grid shows the parsed records (header row excluded from record numbering); for JSON it shows every string leaf with its RFC 6901 pointer.
Nothing selected.
3 · Map it to a named input
The named input of the target tool, for example /cash_balance. Nested names compose: /counts/n_filed.
decimal-plain: optional sign, digits, optional point and digits, nothing else. Grouping separators, currency symbols, parentheses and exponents are refused, never guessed.
Paste what the target input holds today; the page checks the canonical digest of the normalized extraction against it and the span leaves the bench verified instead of external.
Names the column whose value pins the row (for example account_id = OP-002). If that value appears in more than one record the span is refused as ambiguous, so a reordered file fails loudly. The guard value is taken from the selected row.
4 · The batch
Empty. Added spans are checked here (the four reference checks run on every add) and only a passing mapping enters the batch.
How the binding works, and what it says

Four checks run per span, in order: the SHA-256 of the supplied bytes equals the recorded document digest; the named locator resolves in a parse of the same bytes by the pinned RFC 4180 parser (or an RFC 6901 walk for JSON); the extracted string equals the recorded lexical byte for byte; and the canonical digest of the normalized lexical equals the canonical digest of the value at the input pointer, when that value was supplied. The state marks:

✓ verifiedthe document was in hand and all four checks passed: the value is bound to this document at this location.
◐ externalthe mapping is complete and self-consistent; the input's current value was not supplied, so the fourth check had nothing to bind against.
✗ faileda check refused; the reason code is printed and the mapping never enters the batch.
§A tick mark on this page is a tie-out aid: this does not show the document is accurate.

The extractor is pinned: , checked against the published kernel digest list vendored as-of . Records naming any other digest are refused. Export the batch and attach it at verify time on the Artifact Verifier's tie-out block, which accepts the same records next to a receipt. Primary text: RFC 4180 (CSV) and RFC 6901 (pointers).