SAIL Rules

Your rules. Your IP. Live on the very next transaction.

Sentences · tables · code · tested · replayed · approved · recorded

How a rule works

Write it as a sentence. Read it as a table. Decide it everywhere.

01 Sentence

Late order change

WhenA purchase order from Harbor Home Stores changes quantity by more than 5% within 48 hours of the ship date

ThenHold it for the account owner, with the change and the stock position attached

Owner: Customer operations

Generated from the rule

02 Table

The same rule, every case

Trading partnerQuantity changeHours to shipOutcome
Harbor Home Stores> 5%< 48Hold for account owner
Harbor Home Stores≤ 5%anyAccept
any> 10%anyFlag for planner
anyanyanyAccept

Hit policy: First match. No overlaps, no gaps.

03 Decision point

order.changed

  • Late order change v7Harbor Home Stores · 850 / 860 · inboundfired
  • Credit hold v12Whole account · lockedpassed
  • Retail order tolerance v3Retail programset aside, more specific rule applies

OutcomeHold for account owner

Recorded with what it read: quantity, ship date, partner. Rule versions v7, v12, v3.

Illustrative example · sample data

Plain sentences

“When … then …” · your business names

For business owners

Tables

Pasted from a spreadsheet · overlaps and gaps marked

For many cases at once

Code

JTScript · sandboxed · tested · approved

For the rare exception

Scope and precedence

The most specific rule wins. Conflicts are caught before you publish.

Scope by
Whole accountProgramTrading partnerDocument typeDirectionConnection or lane
  1. Whole account

    Pay invoices that match the order and receipt within 2%

    Default
  2. Retail program

    Within 1% for every retailer in the program

    More specific
  3. Harbor Home Stores · 810 · inbound

    Within 0.5%, and never above contract price

    Most specific · wins

Illustrative example · sample data

Most specific wins

One partner · one document type · sets aside the broader rule

Locked rules stay

Locked for the network · narrower rules only add

Conflicts caught first

Publishing stops · the disagreeing transaction shown

Every change

Tested, replayed and approved. Then live. Rolled back in one click.

  1. 01

    Test

    From real transactions · every test passes

  2. 02

    Replay

    Your history · 30 days to a year · every changed decision

  3. 03

    Approve

    The owner · never the author · never AI

  4. 04

    Publish

    New version · effective-dated · next transaction

  5. 05

    Roll back

    One click · recorded

Every decision recorded

What it read · every version it used

Permanent, with the transaction

Reruns that cannot act

Simulation · nothing sent · no credentials

See what would have happened

Runs over months of history

In the background · live traffic untouched

Report only, pause any time

Your authority

You decide what the agents decide. Level by level, limit by limit.

  1. L0
    Observe

    The agents watch and report. Nothing is proposed.

  2. L1
    Suggest

    The agents prepare the fix. Your team decides.

  3. L2
    Act with approval

    The agents act once a person approves.

  4. L3
    Act within limits, with undo

    The agents act inside your limits. You can undo within the window.

  5. L4
    Act within limits, report after

    The agents act inside your limits and report what they did.

  6. ·
    No level above

    Limits set by a person

Resolution Short-pay invoice overcharges

L3 · Act within limits, with undo

Agents 70%Freight audit 30%

Up to $500 per invoiceAt most 200 a day$40,000 a month budgetApproved carriers onlyWeekdays 06:00 to 20:0024-hour undo windowApprover: Freight audit lead

Emergency stopEvery agent back to Suggest, at once

Illustrative example · sample data

The share is yours

Steps of 10% · set by you

Agents never widen their own limits

Proposed by an agent · approved by a person

One emergency stop

Every agent back to Suggest · at once

Rules about time

What should happen, and when. Including what never arrives.

Within

No ship notice within 12 hours of the order acknowledgment: escalate to the supplier manager.

Something must happen in time

Absence

No status update on a load for 3 hours: ask the carrier, then raise it to the lane owner.

Silence is a signal

Sequence

An invoice may not arrive before its ship notice: hold it until the ship notice does.

Things happen in order

Reconciliation

Invoiced quantity no more than shipped, shipped no more than ordered, within your tolerance.

Documents agree

Describe it in words

JT Assist drafts the rule. People approve it.

You

No ship notice within 12 hours of the PO acknowledgment escalates to the supplier manager. Start with our top 40 suppliers.

SAIL · JT Assist · draft

Draft rule · ship notice expected · replayed on 30 days

Illustrative example · sample data

Drafted as a rule about time for your top 40 suppliers, owner Supplier compliance. Replayed on the last 30 days of acknowledgments before anything goes live.

On the last 30 daysOrdersThe rule would have
Ship notice within 12 hours18,204Done nothing
Ship notice late, arrived after41Recorded the breach
No ship notice at all312Escalated to supplier managers

A draft only. Supplier compliance approves it; JT Assist never can.

Submit for approvalReplay on 90 days

Your IP

Your rules are your IP. Bring them in. Take them out.

In Import

Bring the rules you already have

  • Spreadsheet tables (.xlsx, .csv)
  • Standard decision-table files (DMN)
  • JSON rule definitions and JSON Schema
  • A SAIL solution file
  • Words and documents, drafted by JT Assist

Imported as drafts · macros never run

Out Export

Take everything, any time

  • SAIL rule files
  • Standard decision tables (DMN)
  • Spreadsheets
  • The original files you imported
  • Every decision’s history, as CSV

Same decisions in an empty account · never used for training

Business Expansion Agents

Bring us your rules. They stay yours.

Your network. Your rules. Your IP. See your rules at work in logistics →