# Business Journeys — Reference Pilot

## A. Downstream-demand scenario (illustrative)
Retail demand forecast/order → manufacturer demand → flour requirement → wheat sourcing/import → customs/silo receipt → flour production → pasta production → transfers to retail warehouse/stores → POS sale → receivable accrual → settlement instructions/reconciliation.
**Open:** Which actor legally initiates purchase orders and under what contract? Do not assume this ordering is final.

## B. Upstream-supply scenario (illustrative)
Wheat lot available → supplier proposes volume/specifications → manufacturing availability/reservations → purchase and production orders → distribution allocations → retail sell-through → financed/insured positions as configured.

## C. Lot and processing evidence
Import lot must track source shipment, documentation, actual received quantity and quality. Flour batch consumes recorded actual lots/quantities (blend possible), creates output and registered losses. Pasta batch consumes flour and other ingredient lots and records yield. Product sold links to batch only with valid receipt/transfer and sale/lot association; FIFO/FEFO is inference with confidence, not direct proof.

## D. Finance
Contracts define parties, legal ownership, custody, responsibility, invoice basis, percentages, settlement event triggers, accrual and risk coverage. Journal remains balanced. Banking payment may take place outside VNOS and must be reconciled rather than represented as guaranteed movement.

## E. Failures and exceptions
Partial delivery, refusal, returns, recall, damaged shipment, customs delay, incorrect quantity, disputed invoice, missing POS batch, invoice correction and failed external settlement need workflows with explicit status, evidence, reversals and audit.

## F. Multi-industry invariant
The same platform must model e.g. steel → component maker → automaker → dealer, or pharma ingredients → manufacturer → distributor → pharmacy, without changing core entities per named partner.