Mary · Sample report

What you see
every morning.

A static rendering of Mary's daily compliance-data reconciliation report. Section-for-section the same shape your live report takes — vendor identifiers, license, per-row values, and category labels are redacted in this public sample.

List Your Products — Free →Back to Mary for Compliance

Sample data. No live operator's information is shown on this page. Identifiers and categories appear as bracketed placeholders.

What the sample shows

Same shape as the live reportsection-for-section, status-for-status
Identifiers tokenizedvendor, license, tags, manifests
Categories redactedfull set in your live report
Knox-anchor strip includedsequence + truncated hash

TL;DR

Mary's daily report covers the sweep window, what reconciled cleanly, what diverged, recommended vendor actions, confidence notes, the vendor's review determination block, and a Knox anchor strip. This sample renders every section field-for-field the same way the live report does. The bits a public surface cannot honestly carry — your operator name, your license number, per-row tags and manifests, and the closed category labels — show up as bracketed placeholders. The sample renders the vendor-facing sections of the live report the same way the live report does; the audit-trail raw-text block is omitted on the public sample. The structure is the structure.

Sample · 2026-05-27 sweep

Mary's daily report.

Static render. No live operator data. Identifiers and category labels appear as bracketed placeholders.

Sweep

2026-05-27

Operator [Vendor] · License [License]

DRAFT

State count: 287
TerraVault count: 287
Matched: 284
Divergences: 3

Summary

The reconciler compared 287 packages against the state-system record for the sweep window of 2026-05-27. 284 packages reconciled cleanly. Three packages diverged.

What matched

284 of 287 packages reconciled cleanly on the tag join key. The matched bulk of the population indicates day-to-day scan-in discipline is holding for routine receiving and movement.

What diverges

Three packages diverged in this sweep. Two are flagged in one category; one is flagged in another. Per-row details are shown in the live report; identifiers and category labels are redacted in this public sample.

Divergence categories

[Category A]Two packages flagged in this category. Per-row tag, manifest, and recommended action shown in the live report.
2
[Category B]One package flagged in this category. Per-row tag, weight delta, and recommended action shown in the live report.
1

Recommended vendor actions

Confirm the two packages flagged under [Category A] either belong to a transfer manifest the operator has not yet receipted in TerraVault, or are not the operator's inventory; reconcile in the state system.
Confirm the package flagged under [Category B] reflects a real-world weight measurement; reconcile in whichever system is stale.
Submit a review determination once both reconciliations are complete; Mary anchors the determination to the Knox chain on submit.

Confidence and flags

Reconciliation ran against the full sweep window. No data-quality warnings from the parser. All three flagged rows are above the reconciler's confidence floor.

Vendor review determination

In the live report, the vendor picks a decision and writes the corrective action taken in each system. Mary anchors the determination on submit; the row locks. The controls below are static for this sample.

RESOLVED

Every divergence acted on in both systems.

DEFERRED

Acknowledged; vendor will act later.

DISPUTED

Vendor believes the reconciliation is wrong.

Action taken in the state system

Action taken in TerraVault

Knox anchor strip

Sequence: [sequence — populated at anchor]
Anchor hash: [sha256 — truncated, populated at anchor]
Anchored at: [ISO-8601 — populated at anchor]

Live values are populated when the sweep event is anchored to the Bonis Knox chain. See the proof model for how a third party verifies any anchored receipt.

What this sample redacts

Tokenized in this sample.

A public surface cannot honestly carry the operator-specific bits. Those appear as bracketed placeholders here.

Vendor and license: The live report carries the operator's legal name and state license number. The sample shows them as [Vendor] and [License].
Per-row identifiers: The live report carries per-row state-system tags, transfer manifest references, and the specific weight or batch values for each divergence. The sample shows category counts only.
Category labels: The closed category set the reconciler buckets divergences into is shown in your live report. This sample uses [Category A] and [Category B] tokens to signal there are two distinct categories flagged in this sweep without naming them.
Knox anchor values: The live report carries the actual Knox sequence number and the SHA-256 anchor hash for the sweep event. The sample shows them as bracketed placeholders to make the strip layout visible.

What the live report adds

The live report carries the rest.

The vendor, license, and per-row identifiers are real, not tokenized.
The full closed category set is shown, with the count Mary observed in each.
The recommended-actions block is row-specific and names tags, manifests, weights, and the system to reconcile in.
The decision-state controls accept input, anchor the determination to the Knox chain on submit, and lock the row.
The Knox anchor strip carries the real sequence number and SHA-256 hash; chain-index lookup is operator-mediated today and becomes public when activation conditions clear (see /for-vendors/compliance/proof).

See your own report tomorrow.

List your products on TerraVault for free. Connect your state-system credentials. Mary's first scheduled sweep lands the next morning; you can also run one on demand from the dashboard.