Live control room
REMOTE MESSAGE FEED Connected — no public messages
Remote dispatch log

When mobile signal ends,
the journey can still speak.

Short field messages can keep HAVIKWAY connected during remote stages where ordinary mobile coverage is weak or unavailable.

Satellite updates are intentionally concise. Their role is not to replace the journal, but to provide a simple public signal from places where normal communication may not work.

SAT 0 PUBLIC MESSAGES
GARMIN Disabled
MAPSHARE Not configured
PUBLIC DELAY 60 min
LATEST MESSAGE No public satellite message yet
Public dispatches

Short messages from the field.

Only messages explicitly marked public should appear in this log.

...
REMOTE DISPATCH STATUS

No public satellite messages are available yet.

HAVIKWAY will publish short remote updates here once a satellite message source is connected and messages are explicitly marked public.

MESSAGE TABLE Connected
Why satellite updates matter

A small message can carry a lot of context.

01 Presence

A short dispatch can confirm that the expedition is still progressing when normal connectivity is unavailable.

02 Context

A simple field note can explain a delay, route change or remote stage better than a silent map point.

03 Continuity

The public journey remains connected even when high-bandwidth publishing is temporarily impossible.

04 Archive

Remote dispatches can later become part of the permanent expedition record.

Public communication boundary

This page is a public feed, not an emergency response system.

Public satellite updates are communication, not a substitute for dedicated emergency procedures.

Emergency communication, SOS functionality and private safety contacts should remain separate from what appears publicly on HAVIKWAY.

A missing public update also does not automatically mean something is wrong. There may simply be no publishable message at that moment.

Dispatch structure

What a useful remote message can contain.

STATUS Short condition

A concise statement about the current stage or situation.

LOCATION Safe public context

Country, region or route label rather than sensitive coordinates.

TIME When it was sent

The dispatch should keep its original field timestamp.

SOURCE Communication channel

Garmin, satellite messenger or another verified remote source.

Data integrity

A GPS point is not a message.

HAVIKWAY keeps location records and written field dispatches conceptually separate.

The current live_locations table contains coordinates and telemetry, but no message body. This page therefore does not reinterpret public_label as a satellite message.

live_locations GPS + telemetry
satellite_updates Written field messages
public_label Location context
message_text Dispatch content
Recommended message record

Ready for the next database step.

The public page is already prepared to read a dedicated satellite_updates table.

id BIGINT
message_text TEXT
public_label VARCHAR
source VARCHAR
message_type VARCHAR
is_public TINYINT
sent_at DATETIME
published_at DATETIME
HAVIKWAY / SATELLITE

Sometimes the whole update is simply: still moving.