TRUST & SECURITY
The A2go Decision Intelligence Platform (ADIP) runs above the ERP, WMS, and TMS your team already governs. This page states plainly what the platform stores, what write-back can change, and how deployment works, written so a lean IT team can evaluate it in one sitting. Where documentation is still being confirmed, the section says so instead of claiming.
DATA HANDLING
ADIP's Judgment Layer accumulates your company's decision memory: the approvals, the rejections, and the reasoning behind them. That memory lives in a tenant that belongs to your company, and it is never shared across customers, in either direction. What your planners teach the platform compounds for you; no other customer's logic appears in yours.
For what the Judgment Layer captures and how it compounds, see how we capture tribal knowledge.
WRITE-BACK SCOPE
Write-back is the step where an approved recommendation becomes a change in your system of record. It is a specific, bounded change, proposed with its reasoning attached, and it targets fields and documents your team already governs. Which decision types an agent may touch, and the bounds it may act within, are reviewable policy your administrators configure, not convention.
Proposed
An agent surfaces a recommendation with the signal that triggered it and the options it considered. Nothing changes at this step.
Approved
Recommendations are approval-ready by default. A call becomes automatic only when you decide it has proven out, and that grant is itself reversible.
Logged
Every change lands in an audit trail with its rationale and who, or what policy, approved it. "Why did this happen?" always has an answer.
Reversible
A write-back touches fields and documents your team already governs. Undoing one is an ordinary transaction, not an archaeology project.
The full definition, including bounded autonomy and the system categories agents write to, is at how agents take action.
DEPLOYMENT PATH
ADIP does not replace your ERP, WMS, or TMS, and there is no prerequisite data program. Nothing is replaced and nothing is ripped out; the platform runs above the systems you already own, and the first decision domain goes live in weeks, measured against the baseline you bring. Expansion happens one decision at a time, on your roadmap.
AGREEMENTS
We work from a standard subscription agreement, available on request. Ask for it through the contact page and we will send the current version for your review.
DOCUMENTATION STATUS
This page follows one rule: nothing appears here unless it is true and current. The sections below stay open until their owners confirm the content.
The fastest way to test these claims is on a decision your team runs today. Start with the one that hurts most; the survey maps it in a few minutes, and the conversation that follows stays scoped to that decision.
Map your highest-pain decision