Start a brief

Trust

The boundary is part of the build.

A useful system makes authority, access, exceptions and handover visible. It does not hide consequential decisions behind automation language.

Release controls

Six safeguards before public use.

01

Minimum necessary data

Initial enquiries request business context, not credentials, passenger information, maintenance records or confidential operational data.

02

Authoritative sources

Existing regulated and operational systems remain the source of truth unless an explicitly approved migration says otherwise.

03

Named human approval

Consequential external actions require a responsible person and a visible decision record.

04

Least practical access

Access, environments and production changes are bounded to the agreed work and reviewed at handover.

05

Failure and fallback

Representative errors, duplicates, rejected inputs and manual fallbacks are tested before release.

06

No borrowed authority

HMD does not claim certifications, regulatory approvals or aviation expertise that have not been documented.

Private enquiry boundary

No public mailbox and no automatic forwarding.

The staged enquiry service stores only a bounded business brief in a dedicated private inbox. Owner access requires authentication and an explicit allowlist. The review build keeps transmission disabled until that isolated data service and its owner identity are configured.