SAIL Rules
The way you run your business is intellectual property built over decades. Write it as rules in sentences, tables or code, and SAIL runs them on every transaction across your connected network. Tested, replayed on your own history and approved before they go live. Every decision recorded.
How a rule works
One rule is callable from anywhere: a map, a flow, a form, a business object, an agent. Rules gather at decision points, so publishing one changes what that point decides on the very next transaction.
01 Sentence
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 operationsThe sentence is generated from the rule, so it always says what will run.
02 Table
| Trading partner | Quantity change | Hours to ship | Outcome |
|---|---|---|---|
| Harbor Home Stores | > 5% | < 48 | Hold for account owner |
| Harbor Home Stores | ≤ 5% | any | Accept |
| any | > 10% | any | Flag for planner |
| any | any | any | Accept |
Hit policy: First match. No overlaps, no gaps.
03 Decision point
order.changedOutcomeHold for account owner
Recorded with what it read: quantity, ship date, partner. Rule versions v7, v12, v3.
Illustrative example · sample data
Write “when … then …” with your own business names. SAIL reads the sentence back to you exactly as it will run.
For business ownersPaste a decision table from a spreadsheet. Overlaps and gaps are marked before you save, with an example of each.
For many cases at onceWhen a rule needs it, write it in JTScript. It runs sandboxed, needs a test and its owner’s approval to publish.
For the rare exceptionScope and precedence
A rule applies as broadly or as narrowly as you scope it. Set one rule for the whole account, a tighter one for a program, and the tightest for one trading partner’s inbound invoices.
Pay invoices that match the order and receipt within 2%
DefaultWithin 1% for every retailer in the program
More specificWithin 0.5%, and never above contract price
Most specific · winsIllustrative example · sample data
A rule for one trading partner and one document type sets aside the broader rule it narrows. A scope you don’t set matches everything.
A rule you lock for the network cannot be set aside by a narrower one beneath it. A narrower rule can only add to it.
If two rules could disagree and neither is more specific, publishing stops and shows a transaction where they disagree, so you settle it before it goes live.
Every change
No rule reaches a live transaction until it has passed its tests, run on your own history and been approved by the person who owns it.
01
Test cases made in one click from real transactions and failed checks. Every test must pass and every check be clean.
02
The draft runs on your own history, 30 days by default and up to a year. See exactly which decisions would change, each one click from its transaction.
03
Approved by the rule’s owner, never by its author and never by AI. Locked and authority rules need two approvers.
04
A new version, effective-dated. Live on the very next transaction, or on the date you set, with no change to the flow.
05
One click puts the previous version back, as a new recorded version. No replay needed.
Each decision keeps exactly what it read and the version of every rule, table and object it used. Open any decision and see why.
Permanent, with the transactionRerun chosen transactions as a simulation. Every send, write and call is replaced by a recorder, and no credential is available, so nothing leaves.
See what would have happenedRun a draft over months of transactions in the background, inside your own account’s capacity. Live traffic doesn’t slow down, yours or anyone else’s.
Report only, pause any timeYour authority
For each kind of resolution, you set how far the agents may go on their own, what share of cases they take, and the limits and budgets they work within. Change it any time; the next case runs on it.
The agents watch and report. Nothing is proposed.
The agents prepare the fix. Your team decides.
The agents act once a person approves.
The agents act inside your limits. You can undo within the window.
The agents act inside your limits and report what they did.
Even at L4, the agents act only inside the limits a person set.
Resolution Short-pay invoice overcharges
Agents 70%Freight audit 30%
The level is the ceiling. The share is how much of it is used; the rest goes to your team with the fix prepared.
Emergency stopEvery agent back to Suggest, at once
Illustrative example · sample data
At the act levels you set the share of cases the agents handle alone, in steps of 10%. Raise it from 70% to 80% and cases only move to the agents, never back.
An agent or JT Assist can only propose a change. A wider level, share, amount or budget needs a person, and never the one who proposed it.
One action sets every agent, for one resolution or all of them, back to Suggest at once. It is recorded, and only a person reverses it.
Rules about time
Some of the most valuable rules are about time: a document that is late, a silence that lasts too long, things out of order. The clock keeps time for them, because an absence is exactly when nothing arrives.
No ship notice within 12 hours of the order acknowledgment: escalate to the supplier manager.
Something must happen in timeNo status update on a load for 3 hours: ask the carrier, then raise it to the lane owner.
Silence is a signalAn invoice may not arrive before its ship notice: hold it until the ship notice does.
Things happen in orderInvoiced quantity no more than shipped, shipped no more than ordered, within your tolerance.
Documents agreeA document that arrives after its window closes is recorded against the breach, so the history shows both.
Describe it in words
Describe a rule, or hand over a document or a spreadsheet. JT Assist drafts it, with the source it read. Every draft passes the same tests, replay and approval as any other rule, and JT Assist can never approve. Switch AI off and every rule, screen and approval works the same.
No ship notice within 12 hours of the PO acknowledgment escalates to the supplier manager. Start with our top 40 suppliers.
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 days | Orders | The rule would have |
|---|---|---|
| Ship notice within 12 hours | 18,204 | Done nothing |
| Ship notice late, arrived after | 41 | Recorded the breach |
| No ship notice at all | 312 | Escalated to supplier managers |
A draft only. Supplier compliance approves it; JT Assist never can.
Your IP
Your rules stay yours. Bring them in from the spreadsheets and decision tables you already keep, and take every one of them out again whenever you want.
In Import
Every import arrives as drafts, with a report of what was read exactly and what needs review. Nothing inside a file, such as a macro, is ever run.
Out Export
Export it all and import it into an empty account, and you get the same decisions. Your rules are never used to train anything.
Business Expansion Agents
Your network. Your rules. Your IP. The agents connect your network on day one, run every transaction on your rules and resolve what you authorize them to. See your rules at work in logistics →