Coordination Field Engine
A logistics coordination runtime that tracks agreements, evidence, loops, and divergences across the full lifecycle — from booking to payment, from insurance to dispute resolution.
What this demo shows
A single shipment — 500 bags of green arabica coffee from Santos, Brazil to Rotterdam, Netherlands — tracked across four coordination layers: operational, documentary, financial, and insurance.
Every data point on this surface was validated against the hermes schema running on a live PostgreSQL 16 instance. The data is synthetic but the schema, the constraints, the triggers, and the evidence logic are real.
What is validated vs designed
Core schema
3 migrations, 11 tables, 7 views, 9 triggers, 12 enums. All runtime-tested.
NF-e parser
Brazilian fiscal document parser. Zero dependencies. 17 tests passing.
API routes
Context timeline and summary endpoints. Runtime-verified against live database.
Financial layer
Invoice, payment, cost mismatch, payment delay — all modeled through existing primitives.
Insurance layer
Policy, averbação, reefer incident, claim, partial denial — existing schema, no new tables.
Multiplayer surface
Shared interaction over sovereign core. Architecture documented. Not yet built.
Marketplace logic
Offer, demand, negotiation, conversion. Vocabulary defined on existing primitives.
Federation
Seeds, structural templates, consent-governed sharing. Vision documented. No runtime.