Manufacturing & supply chain

Work orders, inventory movements, and supplier payments — with the provenance boundary stated honestly

Cost truth and movement truth, months later

A work order's cost buildup, an inventory transfer, a supplier payment cleared against several invoices — each is easy to record and hard to prove later, when the question becomes whether today's record matches what the MES or ERP held at the time. Supply chains add a second problem: claims about origin and handling made by many parties over months, where the dispute is rarely "what does the record say" and usually "is this the record, and who said so." FORAY answers the record-integrity half completely — every anchored record is tamper-evident, and any later edit breaks the match against the public chain — and states its boundary on the other half plainly rather than overclaiming it.

Roll-ups, transfers, and supplier settlement

A purchase order or supply agreement is an Arrangement. Materials, labor, and overhead recognitions are Accruals — computed judgments with declared methods and inputs. An expected completion or expected payment is an Anticipation; the transfer or disbursement is an Action. The worked examples:

  • Work Order: Materials, Labor, and Overhead Roll-Up — three cost Accruals rolled into one expected finished-goods transfer and the inventory-movement Action that completes it: the sector's central evidence shape, end to end.
  • Combined Payment: One Action, Two Allocations — a supplier payment cleared against two expected invoice payments with exact decimal attribution: allocation amounts must sum to the settled amount exactly, no tolerance.
  • Cash Sale: Action-Only Record — the degenerate case that proves the grammar flexes: settlement with no contract and no receivable is one Action and nothing else.
  • The proofs page's finance demonstration record is itself an accounts-payable settlement against a purchase order — the sector's daily transaction, anchored on mainnet with complete published custody material.

Provenance, stated exactly. Provenance claims — origin, handling, certification — are declarations by identified parties. FORAY proves what was claimed and that it has been unaltered since; the trust model is the precise statement of the claim ladder, including the attestation posture. Digest-identified external artifacts (certificates, inspection documents) travel with the record as references whose bytes the holder retains.

What a holder keeps

The anchor is permanent; the holder's ability to use it is exactly as durable as their custody. For every anchored record the holder keeps the exact record bytes, the full anchoring response (salt and window material), any formula packages behind declared computations, the referenced external artifacts themselves — a digest reference proves nothing if the artifact is gone — and the anchor reference. The Evidence Custody Model states the package and the retention discipline; the custody sheet is the completeness instrument.

What verification looks like

Verification is holder-side and requires no access to DUNIN7. The proofs page demonstrates the full check against live mainnet anchors, and the Verifier Specification defines it for any independent implementation. A validation PASS attests conformance to the ruled shape; the trust model is the precise statement of what every FORAY proof covers.