Platform · the Judgment Layer
Where your judgment lives.
Every operation runs on two kinds of knowledge. One is in your systems: orders, inventory, lead times, prices. The other is in your people: which supplier's promise dates to discount, which customer will accept a substitute, when the forecast is lying. The second kind decides more than the first — and in most companies it lives nowhere but experienced heads. The Judgment Layer is where the A2go Decision Intelligence Platform (ADIP) keeps it: captured, versioned, and applied by agents on every decision.
What it captures
- Overrides and the reasons for them. When a planner rejects a recommendation, the correction and its rationale are kept — not as a complaint log, but as policy the next recommendation respects.
- Constraints no system records. The dock that can't take a truck after 3pm; the customer whose penalty clause bites harder than the contract implies; the SKU that can't ship with another. Written once, enforced everywhere.
- Preferences with limits. Protect contract customers first, but never let a single account take the whole allocation; favor the cheaper carrier, except when the promise date is already at risk.
- Exceptions that became rules. The workaround your team invented three disruptions ago is often the real process. The Judgment Layer is where it stops being tribal.
How agents use it
When an ADIP agent weighs a decision, it doesn't reason from raw data alone. It reasons from your data through your judgment: the constraints, preferences, and precedents the layer holds. That's why two companies with identical numbers can get different — and correctly different — recommendations. The agent's proposal reads like your best planner's, because the judgment inside it is theirs.
And because every accepted, adjusted, or rejected recommendation flows back in, the layer compounds: each decision makes the next one start smarter. New planners inherit judgment on day one instead of apprenticing for it over years. Nothing leaves when someone retires.
Judgment, governed
Everything in the layer is explicit and reviewable — who added a rule, when, and why. If a piece of judgment stops being true, you change it in one place and every agent decides differently from that moment. That's the difference between tribal knowledge and institutional knowledge: one walks out the door, the other is an asset you govern.
The Judgment Layer is A2go's implementation of the orchestration idea SCOR DS names Orchestrate — the level-0 process that connects strategy to the operating processes. SCOR — the Supply Chain Operations Reference model — is stewarded by ASCM.