Lumen
The decision layer.
Sources. Objects. Decisions. Surfaces. One loop, one audit trail. The platform every Inflect solution sits on.
Four layers.
The same shape every time. Sources feed Objects. Objects ground Decisions. Decisions surface where operators already work.
- L01
Sources
INBOUND
- Mailbox, ERP, CRM, telematics, SCADA.
- File drops, PDFs, spreadsheets.
- OAuth per source. No shared service accounts.
- Replay-safe ingestion.
- L02
Objects
TYPED MODEL
- Customer, asset, transaction, route, vendor.
- Row-level access. Tenant boundary in the database.
- Versioned history per object.
- Audit trail per write.
- L03
Decisions
GROUNDED AI
- Agents read the Objects layer, not the public internet.
- Actions write back. Journals. Dispatches. Approvals.
- Confidence scored. Citations attached.
- Reversible by default.
- L04
Surfaces
OPERATOR APPS
- LedgerAI. Operations apps. Reports.
- Each surface reads from Objects.
- New surfaces in weeks.
- Same audit trail underneath.
One loop. Any domain.
An invoice arrives. The Source ingests it. The Objects layer recognises the Vendor against past journals. An Agent proposes a balanced Action. Debit Expenses 6200, credit Bank. Confidence 94%. Cited back to the email. The treasurer accepts. The Action commits. The Surface refreshes.
The same loop runs unchanged when the Source is a fleet GPS stream, the Object is a Route, and the Action is a re-dispatch. The same loop again when the Source is a sensor feed, the Object is an Asset, and the Action is a maintenance call.
The vertical changes. The shape does not.
Built on Lumen.
Each surface reads from Objects, never from raw Sources. New surfaces ship in weeks, not quarters.
LedgerAI
Mailbox to ledger to audit-ready statements. The reference surface. Sources, Objects, Decisions, Surfaces all visible in one workflow.
ExploreOperations
Dispatch and routing surface for fleet and field teams. Objects: Vehicle, Route, Leg, Driver. Actions: re-dispatch, re-route, hold.
Design phaseReliability
Process and asset surface for industrial operators. Objects: Asset, Sensor, Process Step, Batch. Actions: schedule maintenance, halt batch.
Design phasePosture.
- E01
Database-enforced tenancy
Postgres row-level security. Tenant boundary is not a query filter. It is a constraint at the DB layer.
- E02
Encrypted per-tenant secrets
OAuth tokens, API keys, and source credentials wrapped under a server-side KEK. No flat-file secrets, no shared keys.
- E03
Auditable Actions
Every write carries actor, source, confidence, and citation. Reversal is a first-class operation, not a workaround.
- E04
Single deploy, multi-tenant
One shared FastAPI process behind Caddy. Linear scaling into the hundreds of tenants. No microservice circus.
A problem that fits the shape?
We onboard a small number of partners at a time. Bring the data, bring the objects, bring the decision you want made.
Start a conversation