Stress-test payroll rules drawn from collective agreements

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

   Scope checkYes or no, with a probability

   Before work starts on a unit

   Does this collective agreement's scope clause cover the site and employee group the pay rule is written for?

   Sees only: One pay rule's stated scope and the agreement's scope clause

   Why: Avoids testing a rule against an agreement that never governed it.

   00.30 and 0.601

   • Yes: 0.60 or higher→thenAccept
   • Unsure: 0.30 up to 0.60→thenEscalate to a strong model
   • No: below 0.30→thenSkip this unit
2. 2

   After workers, the judge checks

   Evidence checkYes or no, with a probability

   After a worker answers

   Does the quoted agreement clause set the same rate, trigger and conditions as the written pay rule, with nothing added or left out?

   Sees only: One written pay rule and the clause the builders quoted

   Why: The builders' case must rest on the clause text, not on how payroll has always done it.

   00.50 and 0.851

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

   Evidence checkYes or no, with a probability

   After a worker answers

   Does the clause the breakers quoted create an exception or condition that the written pay rule fails to apply?

   Sees only: One written pay rule and the exception clause the breakers quoted

   Why: An objection only counts if the agreement text really says it; weak objections are retried, not kept.

   00.50 and 0.851

   • Yes: 0.85 or higher→thenAccept
   • Unsure: 0.50 up to 0.85→thenMark unresolved
   • No: below 0.50→thenReject and retry
4. 4

   Reconciler, while merging

   Conflict checkYes or no, with a probability

   While reconciling

   Does this side letter or later amendment change the clause that the rule was built from?

   Sees only: The quoted clause and one dated side letter or amendment

   Why: Later documents quietly override earlier ones; this catches rules built on superseded text.

   00.30 and 0.701

   • Yes: 0.70 or higher→thenMark unresolved
   • Unsure: 0.30 up to 0.70→thenEscalate to a strong model
   • No: below 0.30→thenAccept
5. 5

   Run control, between rounds

   Another round?Yes or no, with a probability

   Between rounds

   Did the last round of objections raise any clause that earlier rounds had not already quoted?

   Sees only: The list of clauses quoted in each round for one rule

   Why: Ends the attack when it starts repeating itself.

   00.30 and 0.601

   • Yes: 0.60 or higher→thenContinue
   • Unsure: 0.30 up to 0.60→thenStop
   • No: below 0.30→thenStop
6. 6

   Accountable person, before anything is settled

   Person decidesYes or no, with a probability

   Before anything is reported as settled

   Would correcting this pay rule change what any group of employees is paid?

   Sees only: One rule's verdict with both sides' quoted clauses

   Why: Pay changes and disputed readings belong to the payroll manager, labour relations and union consultation.

   Accountable: The payroll manager and labour relations lead decide rule changes; disputed readings go through union consultation.

   00.05 and 0.201

   • Yes: 0.20 or higher→thenAsk a person
   • Unsure: 0.05 up to 0.20→thenAsk a person
   • No: below 0.05→thenAccept