Home The Problem

Files Are Not Data

An airline's most critical knowledge lives in documents — OM-A, OM-B, MEL, QRH, ADs, STCs, training syllabi, SOPs. Today these are PDFs in folders. Word docs attached to emails. Revisions tracked in spreadsheets.

Which version is current?

Multiple copies across desktops, iPads, shared drives, and inboxes. No single source of truth.

Who has read it?

No acknowledgment tracking. No way to prove crew received and understood a revision.

What changed?

No diff between revisions. Crews compare PDFs manually to find what's new.

What did it say on that date?

After an incident, reconstructing what was current is manual forensics across file servers.

Who can see what?

Access control by folder permissions. No row-level governance. No attribute-based policies.

Is it truly gone?

Deleted files leave no trace. No retention policy. No legal hold. No chain of custody.

Files have no lineage, no governance, no relationships, no memory. WingLayer turns documents into governed data assets.

The Data Layer

Documents Become Data

WingLayer stores, versions, governs, and exposes documents as structured, queryable, trustworthy data. Everything that consumes airline documents reads from WingLayer.

Document Object

A document in WingLayer is not a file. It is a governed data object with identity, lineage, relationships, and rules.

Identity

  • Unique ID (immutable)
  • Document type (OM-A, MEL, AD, ...)
  • Title & owner

Content

  • Encrypted file (AES-256-GCM)
  • Content hash (SHA-256)
  • Per-document encryption key

Metadata

  • Aircraft types & ATA chapters
  • Regulatory references
  • Effective & expiry dates
  • Custom tags (airline-defined)

Lineage

  • Full revision chain
  • Supersedes / superseded-by
  • Parent & related documents

Governance

  • Access policy & approval chain
  • Acknowledgment requirements
  • Retention & legal hold

State

  • Draft → Review → Approved → Active
  • Superseded / Archived / Held
  • Current revision number
01

Complete Version History

Every revision is permanent. Nothing is overwritten. Full diff, approval chain, and effective date on every revision.

02

Point-in-Time Access

"What did the MEL say on March 3rd?" Resolve by walking the revision chain and effective dates.

03

Zero-Copy Branching

Only changed pages are stored. Branches share unchanged content with trunk. Storage cost: 3 pages, not 412.

04

Sharing Without Copies

Never distribute copies. Grant access. Training, Ops, Safety, and the regulator all see the same live data.

05

Flexible Metadata

Minimal core schema. Airlines extend with their own tags, fields, and taxonomies. No rigid predefined dropdowns.

06

Governance at the Data Layer

Security is a property of the data itself. Any system that reads from WingLayer inherits its governance automatically.

What WingLayer Is Not

WingLayer is a data layer. It deliberately does not include:

×AI / LLM / RAG — that's a compute layer that reads from WingLayer
×Chunking / embedding — that's a processing layer that transforms WingLayer data
×Search — that's a service built on top of WingLayer's data and metadata
×Training management — that's an application that references WingLayer documents
×Reporting dashboards — those are views, not data

WingLayer stores the truth. Other systems interpret it.

Security

Bank-Grade Security

Every document treated like a financial instrument. Aviation operational data is safety-critical, legally discoverable, and regulator-auditable.

Four-Layer Encryption

No WingLayer employee can read customer documents. Tenant keys are managed such that platform operators have no access to decrypted content.

1

Storage Encryption AES-256

All data encrypted at rest. Documents, metadata, audit logs — everything.

2

Transport Encryption TLS 1.3

All data encrypted in transit. Every connection, internal and external.

3

Field-Level Encryption

Sensitive metadata encrypted with independent keys. Crew PII, medical data, incident details.

4

Content Encryption PER-TENANT

Document content encrypted with tenant-specific keys. HSM-backed. BYOK supported. Auto-rotation.

Zero-Trust Access Model

RBAC + ABAC hybrid. Role-based defaults with attribute-based overrides per fleet, base, clearance, and time window.

RoleDefault Access
Accountable ManagerAll documents, all revisions
Chief Pilot / VP OpsOM-A, OM-B, MEL, QRH, performance data
Head of TrainingOM-D, syllabi, training records, competency frameworks
Line PilotOM-B (relevant fleet), QRH, MEL, airport briefs
Safety OfficerSafety reports, occurrence data, investigation files
DispatcherOM-B, MEL, NOTAMs, performance data, weather
RegulatorAs per regulatory access agreement
Fleet E175 pilot sees only E175 docs
Base Station-specific procedures scoped by home base
Clearance Investigation docs restricted to named individuals
Temporal Auditor access valid only during audit window

Immutable Audit Trail

  • APPEND-ONLYNo entries can be modified or deleted
  • TAMPER-EVIDENTCryptographic hash chain — each entry hashes the previous
  • QUERYABLE"Show every access to the MEL between Jan 1 and March 15"
  • EXPORTABLECompliance reports for regulatory submissions
14:32:07doc.viewOM-D Rev 6 sec:4.3.2m.khan
14:33:15doc.downloadOM-D Rev 6 format:pdfm.khan
15:01:44doc.viewOM-D Rev 6 sec:2.1j.smith
15:10:02doc.viewOM-D Rev 6 full_docbcaa.audit

Governance & Retention

  • ACK TRACKINGAcknowledgments are data, not emails. Live with the document
  • RETENTIONPer-type policies. Safety reports: 10 years. Superseded OMs: 5 years
  • LEGAL HOLDFreeze documents. Overrides retention. Cannot be archived or deleted
  • REG HOLDAutomatic hold triggered by linked safety events or regulatory findings
TENANT ISOLATIONSEPARATE KEYSDATA RESIDENCYFULL EXPORTNO LOCK-IN
Architecture

Data Model

The complete structure that governs every document from ingestion to retirement.

data_model.txt
TENANT
 ├─ LIBRARY
      ├─ DOCUMENT
           ├─ REVISION (1..n)
           │    ├─ Content (encrypted file + hash)
           │    ├─ Metadata (core + extended)
           │    ├─ Diff (against previous revision)
           │    └─ Approvals (chain of sign-offs)
           │
           ├─ BRANCH (0..n)
           │    └─ Draft Revision (1..n)
           │
           ├─ RELATIONSHIPS
           │    ├─ supersedes / superseded_by
           │    ├─ references / referenced_by
           │    └─ derived_from
           │
           ├─ ACCESS POLICY
           │    ├─ Role grants
           │    ├─ Attribute rules
           │    └─ Temporal windows
           │
           ├─ ACKNOWLEDGMENTS
           │    └─ (user, timestamp, revision)
           │
           └─ AUDIT LOG
                └─ (action, user, timestamp, details)

Documents become data. Data becomes truth. Truth becomes trust.

Your Documents.
Versioned. Encrypted. Governed. Ready.

The single, governed, versioned, secure data layer for every document an airline operates on.