Platform architecture

LumicIQ
Data sources

In-Store Sensors

people counters · shelf and weight sensors · RFID · queue and door sensors

Store Systems

point of sale · workforce management · merchandising and inventory

External Data

weather · nearby events and public holidays · local law-enforcement bulletins and organized retail crime

Video

The store's existing cameras feed one video processing server that turns footage into observations
The footage is kept alongside them, so a decision can be checked against what was actually on camera.

Other Connectors

For systems without a traditional integration method — custom connector code, built in whatever way makes sense for that system
Each feeds the same Intake as every other source.
LumicIQ

Intake

Every source authenticates. Readings are rate limited, validated, de-duplicated and put into one common format, so nothing downstream depends on whose system it came from.

Event spine
readings · detections · recommendations · deliveries · responses
One ordered stream per store, replayable from any point in it

Detection

A rolling baseline for every store, signal and hour of the week. Each reading is scored against its own prior history before it is folded in.

Nobody writes a threshold, and nothing is tuned per customer.

the cost gate — only what clears the bar goes further

Safety Net

A fixed set of critical conditions the platform commits to never missing.

It depends on nothing above it, so the guarantee survives an outage anywhere else in the system.

Intelligence

One agent per store, always on. It is given the live state of the store and reasons over three things it can point to. What comes out is a specific action with the numbers that justify it, not an alert.

the model underneath is swappable, and chosen per task
Judgement — how it reasons is written down and versioned, tuned from what the best store managers actually do.
Knowledge — the company's own procedures, handbooks and runbooks, at company, chain and store level.
Insights — what has been worked out about this store. Evidence is computed, not asserted; a person can confirm, edit or reject it.

Routing

Merges duplicates, then resolves who should see a recommendation from the roster crossed with who is actually on shift, and escalates when nobody is.

Chooses the channel, and if the first does not confirm delivery it moves to the next. A recommendation that never lands is recorded as such.

Audit & Learning

Every reading, decision, delivery and response written once and never altered — any past decision reconstructable exactly.

Outcomes are where the insights come from, and any change to how the system reasons is replayed against this history and compared before it ships.

Outputs

Manager App

Where everything reaches the manager first.
Queue — recommendations as they arrive, each with the numbers and the reasoning behind it. Act, reassign, or hand it back.
Team — who is on the floor, on a break or off shift, and who to give the work to.
Ask — an open conversation about the store, answered from the same context and recorded the same way.

Communication Channels

Slack · Teams · Beekeeper · Theatro · walkie-talkie systems — whatever the store already runs on
The recommendation arrives as a card in chat and spoken on a headset. Questions and replies come back the same way, which makes the channel a data source too.

Disposition

done · can't · reassigned · handed back · dismissed · no answer
The manager can say why, in their own words. What was acted on — and what was not, and why — is what the system learns from.

Gold outline — software LumicIQ ships; everything else is what the store already runs.  ·  Every request resolves to a customer scope before it reaches application code, and fails closed if it cannot.