Trace component origin and declarations down the bill of materials

The decision tree

6 typed decisions, each with an action for every answer

At fixed moments in a run, the engine puts one narrow question to a decision model. The decision model never writes text: it answers yes or no with a probability, picks from listed options, or gives a score, about a small slice of the material. The engine then does exactly what this tree says, which is what makes the run auditable. The thresholds are the template's design values, not measured results.

1. 1

   Planner, while planning

   Split or keep serialYes or no, with a probability

   While planning

   Does this assembly contain components from more than one supplier, so that its origin cannot be answered from a single declaration?

   Sees only: One assembly's bill of materials lines with supplier names

   Why: Splits only where the tree really branches.

   00.40 and 0.601

   • Yes: 0.60 or higher→thenSplit the work
   • Unsure: 0.40 up to 0.60→thenKeep serial
   • No: below 0.40→thenKeep serial
2. 2

   Split or keep serialYes or no, with a probability

   While planning

   Does this supplier's declaration name sub-tier sources or sites that need their own check?

   Sees only: One declaration's source and site section

   Why: Goes a level deeper only where the declaration itself points there.

   00.40 and 0.601

   • Yes: 0.60 or higher→thenSplit the work
   • Unsure: 0.40 up to 0.60→thenKeep serial
   • No: below 0.40→thenKeep serial
3. 3

   Scope checkYes or no, with a probability

   Before work starts on a unit

   Is this component in scope of the rule being answered, given its material and customs classification?

   Sees only: One component line with material and classification, and the rule's scope sentence

   Why: Out-of-scope parts are most of a bill of materials and need no check.

   00.30 and 0.601

   • Yes: 0.60 or higher→thenAccept
   • Unsure: 0.30 up to 0.60→thenAccept
   • No: below 0.30→thenSkip this unit
4. 4

   After workers, the judge checks

   Evidence checkYes or no, with a probability

   After a worker answers

   Does the declaration list this part number, cover the shipment period and carry a signatory from the supplying entity?

   Sees only: The component line and the declaration's part list, validity dates and signature block

   Why: A declaration for a neighbouring part number proves nothing about this one.

   00.50 and 0.901

   • Yes: 0.90 or higher→thenAccept
   • Unsure: 0.50 up to 0.90→thenEscalate to a strong model
   • No: below 0.50→thenReject and retry
5. 5

   Reconciler, while merging

   Conflict checkA choice among options

   While reconciling

   Do the direct supplier's declaration and the sub-tier questionnaire name the same country and site of origin for this part?

   Sees only: The two origin statements for one part number

   Why: A branch with an origin conflict must not roll up as clean.

   • Same country and site→thenAccept
   • Different country or site→thenMark unresolved
   • They cover different parts or periods→thenReject and retry
6. 6

   Accountable person, before anything is settled

   Person decidesYes or no, with a probability

   Before anything is reported as settled

   Would this roll-up be used in a statement of origin or due diligence sent to a customer or an authority?

   Sees only: The product-level roll-up with its open gaps and conflicts

   Why: The compliance manager signs external statements.

   Accountable: The compliance manager signs any origin or due diligence statement sent to a customer or authority.

   00.15 and 0.401

   • Yes: 0.40 or higher→thenAsk a person
   • Unsure: 0.15 up to 0.40→thenAsk a person
   • No: below 0.15→thenAccept