Onoots Supply
Procurement & vendor-settlement on the Onoots OS. Supply turns purchase
operations — requisitions, sourcing, vendor onboarding, and invoice settlement —
into fail-closed, audit-ready decisions. It does not reimplement the decision
logic: every engine runs the same Compliance Guardian core that Proptech uses
(@onoots/core), and verdicts are meant to be anchored to the Onoots Ledger™.
The four engines
| Engine | What it decides | Fail-closed behavior |
|---|---|---|
| Three-Way Match | PO · Goods Receipt · Vendor Invoice reconciliation | Any tolerance breach or receipt shortfall → hold for dual approval |
| Requisition Intake | Spend-approval routing (manager → director → CFO) | Restricted cost center or over-budget → escalate one step |
| RFQ Sourcing | Ranks vendor quotes, recommends a winner | Below-SLA vendors excluded; engine recommends, human raises the PO |
| Vendor KYS | Know-Your-Supplier standing | Sanctions hit or failed KYS → block; pending / low rating → review |
Where to go next
- Getting Started — what Supply is and how to run it locally.
- Guides — one page per engine, plus the shared Compliance Guardian.
- API Reference — the pure, framework-free engine functions and their types.
Last updated on