Air-Gapped Meeting Records: High Defense

Introduction: The Security Demands of Classified Deliberations

In aerospace engineering, defense contracting, government intelligence, and critical infrastructure management, strategic meetings routinely discuss matters of paramount national security and intellectual property. Deliberations in these environments involve classified technical schematics, orbital telemetry algorithms, cryptographic protocols, and sensitive procurement negotiations.

In these high-assurance settings, standard commercial productivity software is not merely discouraged—it is strictly prohibited by law.

Air-Gapped Workstation Isolation Perimeter:
┌────────────────────────────────────────────────────────┐
│ Sensitive Deliberation / Classified Briefing Room      │
└───────────────────────────┬────────────────────────────┘
                            │ Acoustic Waves in Isolated Room
                            ▼
┌────────────────────────────────────────────────────────┐
│ Physically Air-Gapped MacBook Workstation              │
│ (Wi-Fi Disabled, Bluetooth Disabled, Ethernet Severed) │
├────────────────────────────────────────────────────────┤
│ ScreenCaptureKit Local Audio Tap                       │
│ On-Device Core ML Whisper Transformer (Local ANE)      │
│ SQLite FTS5 Embedded Lexical Database                  │
├────────────────────────────────────────────────────────┤
│ Local APFS FileVault 256-Bit Encrypted Storage         │
│ Ed25519 Hardware Token Signature (YubiKey / CAC)       │
└───────────────────────────┬────────────────────────────┘
                            │ 0.00 KB Egress (Physical Proof)
                            ▼
                    [Zero Data Breach]

Under standards established by the National Institute of Standards and Technology (NIST SP 800-53), the Department of Defense (DoD Directive 8140), and Sensitive Compartmented Information Facility (SCIF) operational guidelines:

• No Remote Egress: Audio recordings must never transit external networks.
• No Third-Party Multi-Tenancy: Transcripts must never touch cloud servers or multi-tenant databases.
• Physical Custody: All intellectual property must remain confined to physically controlled, encrypted local hardware.

Yet, technical teams operating in air-gapped SCIF environments still suffer from the same operational friction as commercial software teams: manual note-taking is slow, distraction-prone, and incomplete.

In this systems engineering guide, we walk through the architecture of air-gapped meeting documentation, demonstrating how to deploy sovereign on-device speech recognition on physically isolated Mac workstations.

---

1. Threat Modeling in High-Assurance Meeting Environments

To architect an air-gapped documentation system, we must examine the specific threat vectors present during classified discussions.

1.1 Remote Cloud Interception and Third-Party Subpoenas

When meeting audio transits cloud servers, it is vulnerable to:

• State-sponsored cyber espionage targeting cloud service providers.
• Foreign intelligence signals monitoring (SIGINT) on trans-oceanic fiber optic cables.
• Secret government FISA subpoenas served on cloud SaaS hosting providers without the data owner’s knowledge.

1.2 Acoustic and RF Side-Channel Leakage (TEMPEST)

In high-security environments, wireless transmission protocols (Wi-Fi, Bluetooth, NFC, cellular modems) represent acoustic exfiltration channels. Malware on an infected laptop can modulate high-frequency audio or emit subtle radio frequencies to transmit data across air gaps.

The Mandatory Defense: The documentation workstation must have all wireless radios (Wi-Fi, Bluetooth) physically powered down or disabled at the hardware level, with zero external network connectivity.

---

2. Deploying Oyma in an Air-Gapped Environment

Because Oyma is architected as a self-contained native binary with zero cloud dependencies, it can be deployed into air-gapped environments without compromising isolation protocols.

2.1 Offline Provisioning Protocol

1. Offline Package Assembly: In a secure staging environment, the IT administrator downloads the Oyma macOS DMG package alongside verified, pre-compiled Core ML model weights:
   • WhisperSmall_ANE_INT8.mlpackage (780 MB)
   • WhisperLargeV3Turbo_ANE_INT8.mlpackage (1.6 GB)
2. Cryptographic Verification: Administrators verify the SHA-256 cryptographic hashes of all binaries and model packages against official signed manifests:

# Verify SHA-256 hash of the offline package
shasum -a 256 Oyma-AirGap-Deploy-v1.4.dmg
# Expected: 8f4e2a... (Matches signed cryptographic manifest)

3. Secure Hardware Media Transfer: The verified package is transferred to an encrypted, read-only USB media drive and loaded onto the air-gapped target Mac.
4. Local Installation: The application and models are copied to /Applications/ and ~/Library/Application Support/Oyma/Models/.

2.2 Hardening macOS Network Interfaces via pf

To provide mathematical certainty of zero network egress, system administrators can configure Darwin’s internal packet filter (pf) to block 100% of outbound sockets globally:

# /etc/pf.conf hardening for SCIF workstation
# Block all inbound and outbound traffic across all interfaces
block in all
block out all

# Permit only internal loopback IPC (required for macOS WindowServer)
pass in on lo0 all
pass out on lo0 all

Load and activate the firewall rules:

sudo pfctl -e -f /etc/pf.conf

With pf active, any process attempting to create an external TCP, UDP, or ICMP socket is terminated instantly by the Darwin kernel.

---

3. Cryptographic Chain of Custody: Hardware Token Signing

In defense procurement and legal compliance, meeting records must possess an immutable, provable chain of custody. When notes are stored on disk, how do auditors prove that a transcript has not been tampered with after the conclusion of the meeting?

3.1 Digital Signatures via Ed25519 Hardware Keys

Using local hardware security modules (such as PIV-compatible YubiKeys or Common Access Cards), the author cryptographically signs the generated Markdown meeting note at the conclusion of the session:

# Sign the generated Markdown meeting note using local GPG/Ed25519 token
gpg --default-key "admin@defense.internal" \
    --armor \
    --detach-sign 2026-10-10-Orbital-Propulsion-Review.md

This generates a cryptographic signature file (.sig):

-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEE...
-----END PGP SIGNATURE-----

3.2 Automated Git Ledger with Signed Commits

The meeting vault can be initialized as a local Git repository. Every meeting note creation is committed with a hardware-signed commit:

git add 2026-10-10-Orbital-Propulsion-Review.md
git commit -S -m "docs: finalized orbital propulsion review meeting notes"

The resulting Git commit history forms an immutable, tamper-evident cryptographic ledger that proves:

• Exactly who attended and documented the deliberation.
• The precise millisecond timestamp of the meeting.
• That not a single character of the transcript has been altered since signing.

---

4. Hardware Efficiency in Restricted Environments

In tactical field operations or shipboard installations, workstations often operate on limited generator or battery power without access to external cooling.

Tactical Workstation Resource Profile During 60-Minute Capture:
| Metric | Cloud-Connected Electron App (Otter/Zoom) | Air-Gapped Native Oyma |
| :--- | :--- | :--- |
| **Network Egress (60m)** | 84 MB outbound | **0.00 KB (Zero Outbound Packets)** |
| **Active Internet Required** | Yes (Fails completely offline) | **No (100% Offline Capability)** |
| **Average Power Consumption** | 18.4 Watts | **6.2 Watts (Apple Neural Engine)** |
| **Acoustic Fan Noise** | Active fan spin (Audible) | **Completely Silent (Fanless M2/M3 Air)** |
| **Data Storage Location** | Multi-tenant cloud servers | **Encrypted APFS Local SSD Only** |

Because Oyma executes on the Apple Neural Engine within an ultra-compact power envelope of 6.2 Watts, an Apple Silicon MacBook Air can transcribe six consecutive hours of classified meetings on internal battery power alone—completely silently and without emitting cooling fan noise.

---

5. Summary: High-Assurance Sovereignty

In national defense and high-assurance engineering, convenience can never come at the expense of security. But security does not require returning to manual paper notebooks and lost institutional memory.

By combining Apple Silicon’s on-device neural acceleration, ScreenCaptureKit’s local user-space audio capture, and local cryptographic signing, Oyma delivers high-leverage meeting documentation that satisfies the world’s most stringent air-gapped security mandates.

---

6. Acoustic & Physical Perimeter Protections (TEMPEST Standards)

In ultra-high-security defense installations, security perimeters extend beyond software firewalls into physical and electromagnetic shielding governed by TEMPEST standards (NSTISSAM TEMPEST/1-92):

• RF Attenuation: Meeting rooms are constructed as Faraday cages with copper mesh lining walls, ceilings, and floors to attenuate radio frequency emissions.
• Acoustic Baffles: Soundproofing prevents laser microphone eavesdropping from reflecting off exterior window glass.
• Physical Port Locks: Workstation USB ports are physically locked with tamper-evident resin plugs to prevent unauthorized external drive connections.

In these environments, software must be completely self-sufficient. There can be no “quick check for updates,” no license verification pings, and no telemetry daemons. Oyma’s self-contained architecture ensures that once installed, the binary executes perpetually without ever demanding external network connectivity.

---

7. FIPS 140-2 Level 3 Hardware Security Key Integration

To meet Department of Defense information assurance standards, cryptographic operations must be backed by validated hardware modules.

When signing meeting records in an air-gapped environment:

1. Hardware Token Binding: The author inserts a FIPS 140-2 Level 3 validated security key (such as a YubiKey 5 FIPS or defense CAC card) into the workstation.
2. PKCS#11 Cryptographic Interface: Oyma interfaces with the hardware token via Darwin’s native Security.framework and PKCS#11 cryptographic drivers.
3. On-Chip Private Key Isolation: The private signing key never leaves the secure cryptographic boundary of the hardware chip. The signature is computed on the token itself and returned to the application, providing legal proof of author identity.

---

8. Defending Against Insider Threat in High-Assurance Vaults

In defense organizations, security architecture must protect against insider exfiltration. Because notes are stored as plain text:

• Granular POSIX Access Control Lists (ACLs): File permissions are enforced via Darwin ACLs (chmod +a "group:engineering allow read" note.md), restricting file visibility strictly to authorized clearances.
• Immutable Audit Trails: Changes to meeting notes are recorded via macOS system audit daemons (auditd), logging every file open, edit, and read event with cryptographic timestamps.
• Preventing Covert Channel Exfiltration: Because Oyma operates with zero outbound sockets, malicious insiders cannot utilize the meeting documentation tool as a covert exfiltration vector to transmit classified data outside the facility.