Skip to content

How it works

Facts. Meaning. Time.
Three things to put back in motion.

Nobody signs off on an ERP migration. Everybody signs off on a read. That is the whole philosophy. lumnik comes in read-only — your system of record stays the sole owner of its data, and it will never know we were there.

  • No migration to start
  • No rewrite of what exists
  • No data leaving your walls

Facts — recover what systems hold

Read ERP databases, files and APIs without writing back, then reconcile the customers, products and orders scattered across them. One usable view, with every disagreement kept visible.

Meaning — declare what values signify

“IP,” “in progress” and “20” may describe the same state. The business declares that knowledge once. lumnik turns unwritten conventions into explicit, traceable lifecycles that people and AI can share.

Time — observe what stopped moving

Each ingestion leaves a dated observation. lumnik can identify work unchanged beyond the threshold your team declared — while staying honest about everything before its first observation.

Dynamics GP

ACME INDUSTRIAL
12 Harbor Rd
(614) 555-0142

Sage 50

Acme Indus.
12 Harbor Rd, Suite C
account on hold

CSV

ACME INDUSTRIAL
purchasing: M. Reyes
email on file

One record served
  • One consolidated customer
  • Address chosen, and traced
  • Purchasing contact enriched
Conflict logged: GP address ≠ Sage 50 address. The single record is served; the disagreement stays visible instead of being silently picked.

Every answer cites its sources.
Or it doesn't exist.

Everyone has an AI now. When it arrives here, it works on data you control — and under watch: deterministic guards check each answer before it ever reaches you.
A confident "there aren't any" that turns out to be wrong is the cardinal sin around here — lumnik would rather admit it doesn't know. That is what makes an answer usable by someone who has to act on it.

 lumnik — scope: inventory
How many 6205 bearings do we have on hand, across all plants?
142 units: 96 in Columbus, 38 in Reno, 8 in Laredo. sources: gp-columbus · nav-reno · csv-laredo — as of this morning's ingestion
And what's the supplier lead time on the 6205-ZZ variant?
I can't establish that from the ingested data — no supplier lead-time field is populated for this part. Rather than invent a number, I'm abstaining.

When time becomes visible

Work that stopped moving becomes impossible to ignore.

An ERP tells you what is. Never since when. Tonight's export overwrites last night's; the status column reads "open" — it read "open" forty days ago too, but nobody wrote that down. This loss of memory is not unique to legacy software.

lumnik rebuilds it, one ingestion at a time.

Each pass leaves a dated observation. Within weeks your hub knows what no report ever showed you: what stopped moving.

A case nobody has touched, an order stuck between two steps, a claim that went quiet on a Friday afternoon. A quote that stopped moving is a decision waiting.

The threshold is declared by you, never guessed: thirty days for an order, forty-eight hours for a claim. lumnik applies what the business said — and shows the exact observation that fired the alert.

When nothing happens, nothing fires. No system warns you about a non-event. This is the one place where lumnik doesn't merely show you your data — it finds something in it.

 lumnik — observation log
Jun 2 quote Q-4471 · sent
Jun 16 observed, unchanged
Jun 30 observed, unchanged
Jul 2 unmoved for 30 days · flagged to sales

On day one, lumnik knows nothing about your past — and it says so instead of guessing. This memory starts at the first ingestion and deepens every night: it's the one part of the thaw you can't catch up on later.