Polaris‑One

Three service crews. Not one vehicle they can drive.

LV 962 is at the workshop again. Nothing is allocated to Team 2 or Team 3, and one tool carrier covers all three. The crews will spend the first hour of the shift ringing the workshop to find out what is spare. The sheet holds every one of those facts, on two halves of the same page.

Open the demonstration Synthetic data. No real person, no real shift plan.

Crews that cannot start 6

Service Crew Team 1 — no light vehicle. LV 962 is under service.

Service Crew Team 2 — no light vehicle, no tool carrier. Nothing is allocated.

Service Crew Team 3 — no light vehicle, no tool carrier. Nothing is allocated.

Free to take right now LV 923 — until end of shift, at DECLINE-1 281 SPL IT 592, IT 593, IT 597 — standing idle

The gap and the answer, from the same shift.

What it works out while you type

A crew with no vehicle it can use, and what is spare: The allocation names LV 962. The fleet table says LV 962 is at the workshop. The same screen lists every unit that no crew holds, so the answer arrives with the problem instead of after a phone call.
Which machine stops, and after how many tasks: A development jumbo earns metres. It reads the status of every face on its own task list and says where the run ends.
A face sent to a jumbo before a nipper set it up: The status reads TSU. The jumbo arrives to mesh and bolts that nobody carried in.
A face inside the stop distance: The sheet holds the advance and the stop line. It never subtracts them.
A heading that needs work with nobody booked: The cycle says what comes next. The task lists say who is going.
A machine with nobody on it, or a person counted twice: Every seat on every unit, read as one list instead of eleven tables.
An active heading with no refuge chamber near it: Tow a mobile chamber on the screen and the answer changes as you watch.

Where the data comes from next

Today Polaris‑One reads two files. That is on purpose: a demonstration must not need a connection to anything. The design keeps the join to a live system small.

The loader is the only seam

Every check and every renderer reads one of two structures. Nothing downstream knows where the data came from. A file fills those structures today. A connector fills the same structures later, and no rule changes.

It reads before it writes

The first connection reads. It writes into nothing. A read needs a far smaller approval than a write, and it cannot damage the system it reads.

The systems it would read

Production and fleet state from Pitram, InMine or LiveMine. Who is on shift from the roster system. Tickets and competencies from INX. Each one replaces a block of the sheet that a person types today.

None of these connections is built. They are the next piece of work, and the order depends on which system a site already runs.

What it will not tell you

It does not grant entry. A barricade controls entry to a heading. This shows the state that a person recorded. It never owns that state.
It cannot measure a walking distance. There are no survey coordinates yet, so refuge coverage asks a question. It never reports that a heading is compliant.
It does not record who changed the plan. The sheet is an authorisation document and it needs a named author. That work is open, and the demonstration runs behind one shared password.
Nobody has confirmed the status codes. TSU and ISU came from a service crew operator. The rest were read off a sheet, and the screen says so wherever it uses them.