x-ray: Order Ingestion Process

Mode: process. Renderer: L0 static HTML/SVG. This example shows how lane handles become selectable visual layers without remote rendering.

surface.summary
Merchant CSV source input Validator process boundary Outcomes accepted or rejected
flow.graph
Upload Required fields Normalize currency Pricing Error report
dependencies.internal + dependencies.external
Validator boundary Merchant Field rules Normalizer Pricing Support
risk.questions
Open questions 1. Who owns validator rules? 2. Where are error reports stored? 3. What happens when pricing queue delivery fails? These questions are inference, not source-backed facts.
Evidence

Source-backed

  • Merchant uploads a CSV.
  • Validator checks fields and normalizes currency.
  • Accepted rows go to pricing; rejected rows go to an error report.
Inference

Explanatory

  • The validator is the branch point.
  • Pricing and support are external process dependencies.
  • Support review may feed future rule changes.
Coverage

Lanes

  • surface, properties, components
  • internal_dependencies, external_dependencies
  • flow, lifecycle, risk_questions, visual_composition
Reader terms

Why It Matters

  • CSV means a spreadsheet-like file of order rows entering the process.
  • Validator means the checkpoint that decides whether rows can continue.
  • Pricing queue means the waiting area for accepted rows; the diagram does not explain pricing itself.
  • Error report means the collected rejected rows that support can review.
Reader outcomes

What To Notice

  • Surface: the whole process is input, checkpoint, outcome.
  • Flow: arrows show what changes as rows move.
  • Dependencies: dashed nodes sit outside the validator boundary.
  • Risk: open questions are separated from source-backed facts.