profile.json
$ cat profile.json
{
  "focus": ["embedded", "cellular", "networking", "macOS"],
  "stack": ["C", "Swift", "Objective-C", "Shell", "Python", "Go"],
  "creed": "code is law — protocol before permission",
  "status": "online"
}

CAPABILITY MAP

What I build

Cellular systems

QDC507, DJI 4G / EG25-G, Quectel EC25, USB identity, ECM, UAC, SMS, voice, and module-side Linux.

radio → userspace

Embedded firmware

ESP32 tools, OpenWrt derivatives, firmware images, recovery flows, and hardware-first diagnostics.

flash → boot → observe

macOS systems

Swift and Objective-C utilities, Apple Silicon packaging, USB inspection, permissions, helpers, and Continuity repair.

Darwin / arm64

Reproducible automation

GitHub Actions, image builders, artifact pipelines, safe upstream merges, signed applications, and release packaging.

commit → verify → ship

OPERATING PRINCIPLES

How I approach systems

  1. 01

    Evidence before assumptions

    Probe the real interface, capture the response, then write the parser.

  2. 02

    Reversible changes

    Every device conversion deserves a verified path back.

  3. 03

    Protocol over ceremony

    Stable contracts and deterministic tooling beat hidden state.

  4. 04

    Own the full signal chain

    Hardware, kernel, transport, application, and UX are one system.

CURRENT MODE

Independent systems tinkerer

Cellular module interoperability

Investigating and adapting cellular modules across macOS, embedded Linux, USB networking, audio paths, AT protocols, and virtualized environments.

  • QDC507 / MDM9607 platform inspection
  • DJI 4G and Quectel module compatibility
  • SMS, call, UAC, ECM, ADB, and module runtime paths

Firmware and release automation

Maintaining repeatable build pipelines for router firmware, system images, self-extracting packages, and GitHub-hosted artifacts.

  • ImmortalWrt and iStoreOS image workflows
  • Cross-architecture packaging and artifact validation
  • Safe upstream synchronization without discarding local patches

macOS diagnostics and tooling

Building focused utilities for Apple-platform failures where system state, permissions, continuity services, signing, and hardware interfaces intersect.

  • Universal Clipboard / Handoff / Continuity Camera repair
  • Signed arm64 app bundles and privileged helpers
  • Observable failure modes and guided recovery

TOOLCHAIN

Languages and systems

Systems

C · Objective-C · Swift · Go

Automation

Shell · Python · GitHub Actions

Platforms

macOS · Embedded Linux · ESP32 · OpenWrt

Interfaces

USB · AT · ADB · ECM · UAC · QMI

SIGNAL STRENGTH

Core competencies

Hardware / software integration
Failure analysis and diagnostics
Build and release automation
macOS systems integration
continuity --repair
Objective-CmacOS

Universal Clipboard Repair

Focused diagnostics and recovery for Universal Clipboard, Handoff, and Continuity Camera.

View source
DJI_4G → EC254G
UTMCellular

DJI 4G VoHive for Mac

Virtualized Linux path that exposes a DJI 4G module as a Quectel EC25 and deploys the vohive platform.

View source
usb.attach(4G)USB
macOSNetworking

DJI 4G Connect

Open-source one-click macOS connector for the first-generation DJI 4G module.

View source
build --size 4GWRT
ShellCI

ImmortalWrt ImageBuilder

Cloud ImageBuilder workflow with selectable firmware size, optional Docker, and plugin integration.

View source
ipk → self.extractRUN
ShellPackaging

RunFilesBuilder

Builds self-extracting packages for iStoreOS and ImmortalWrt from the latest upstream IPK artifacts.

View source
arm64 / rk3588SoC
GitHub ActionsARM

iStoreOS Actions

Build support for Amlogic, Rockchip, and Allwinner boxes across a wide SoC matrix.

View source
img.install(target)IMG
Debian LiveInstaller

Image Installer

A Debian Live based installer for deploying Armbian and OpenWrt images from x86-64.

View source
handshake.sh
$ resolve 0xAAcodeislaw
 github.com/0xAAcodeislaw
$ handshake --protocol git
200 OK · identity verified · channel open

IDENTITY MODEL

0xAA|code is law
address identityprotocol-defined order
“The address begins the identity. The protocol decides the outcome.”
Handle copied