Documentation
Documentation
FACE by Runink: Fulfilment Autonomous Claims Engine. Logistics and fulfilment teams lose money and hours to shortages, damaged loads, missed claim windows and carrier invoices that don’t match the contract. Finding each case means reading across the warehouse system, the telematics feed and the paperwork by hand. FACE does that reading: it connects to the systems you already run, finds the cases, and drafts the claim, the evidence and the next step for a person to approve.
These docs are organised by what you are trying to do.
What FACE is, how it is built, and the vocabulary.
One page per page in the app: Ask, Briefs, Options, Why, Actionable Twins, Settings.
Connections, runners, and every supported connector.
How findings, decisions and evidence documents are produced.
Each agent’s job, inputs, model and human oversight.
The controls, how they work, and the scope of each.
Deploying, configuring and troubleshooting an instance.
Every service and method, for integrators.
Conventions in these docs
- Names of settings, environment variables, RPCs and error messages are copied from the product exactly. If a page and the product disagree, the product is right. Please tell us.
- Every analysis page ends with a Reading the results note, and every security page with the scope of its controls. Read those notes as carefully as the rest.