An applied research holding company at the frontier of consumer AI.

Two operating entities. Fifty-two applications. One operator. SH@W Labs operates in the lineage of the small, focused research lab — taking general-purpose AI capability accessed through open APIs and converting it into specific, defendable product expressions. The foundation model is commodity input. The mechanism is the asset.

Applications Deployed 52+ active
Sub-Platforms 6
Operating Entities 2consumer + commercial
Capability Domains 5
Patent Families 2in preparation
Operating Principal 1founder
01 / The Lab

A research structure, deliberately small.

The Lab is operated by a single principal engineer working with parallel AI augmentation. This is an architectural choice, not a constraint.

By compressing the loop between specification, implementation, and validation into a single operator, the Lab can advance multiple unrelated R&D threads in parallel — a structural advantage when the unit of work is the product hypothesis itself, rather than incremental feature delivery against a fixed roadmap.

The operating thesis: foundation models are a commodity. Open APIs — Claude, GPT-class systems, and their successors — provide raw capability at a marginal cost approaching zero. The competitive surface has moved upward, into expression — the specific mechanisms by which general capability is turned into a product worth using, defending, and shipping. The Lab's portfolio is constructed accordingly.

Field operations are conducted from a mobile platform, traversing the western United States. The Lab's working assumption is that the next decade of meaningful software is built closer to physical context, not farther from it.

02 / Portfolio Architecture

A consolidated portfolio shell, organized by domain.

Output is structured across two operating entities, six sub-platforms, and approximately fifty-two deployed applications.

The architecture reflects deliberate consolidation. Earlier work proliferated into discrete subsidiaries before being unified into a coherent portfolio shell — each application now inherits shared infrastructure (authentication, billing, deployment, telemetry) while preserving independent brand and product surfaces. The Lab ships variants, not duplicates.

Consumer
Operating Entity I

Applications addressing individual users at the intersection of AI capability and everyday product expression. Public-facing distribution.

Commercial
Operating Entity II

Applications addressing operators, enterprises, and regulated counterparties. The Lab's white-label and B2B work consolidates here.

Within these entities, six domain-specific sub-platforms organize the application portfolio: motion-driven interactive entertainment; skills-acquisition tooling; digital legacy and lifecycle systems; geospatial concierge networks; locative narrative platforms; and regulated entertainment frameworks.

This overview is intended for general distribution. Specific product surfaces, subsidiary brand identities, and deployment URLs are reserved for direct engagement.

03 / Capability Domains

Five technical families currently in active development.

Specific products and deployment surfaces are held in stealth pending patent disposition. The descriptions below characterize the underlying mechanisms.

001

Sensor-driven input methods

Browser-native input methods derived from device sensor data — accelerometer, magnetometer, gyroscope. The work includes empirical motion classification, handedness detection, compass tuning, and noise-floor characterization, with sensor-fusion methodology developed in-house for the consumer-device operating envelope.

Motion Capture Validation LabLIVE INSTRUMENT
002

AI-augmented developer tooling

Tooling for the practice of prompt-driven software development, including version-controlled prompt artifacts, build manifests, and multi-agent orchestration patterns. The Lab's working surface — itself an active R&D area — treats foundation-model API access as commodity input and the structured specification as the engineering artifact under version control.

003

Multi-tenant platform architecture

White-label compliance frameworks for regulated industries, including jurisdiction-aware feature gating and tenant isolation patterns. Built to ship the same core platform across jurisdictions with materially different regulatory surfaces.

004

On-device computer vision

Privacy-preserving image and video processing implemented without dependency on external inference APIs. The Lab maintains a position that for a meaningful class of consumer applications, the correct architecture is no network round-trip at all — and that purpose-built classical algorithms can match or exceed model-based approaches at narrow tasks. A deliberate counter-position to the rest of the portfolio: where AI capability is the right input, the Lab leans on it; where it is the wrong input, the Lab does not.

005

Multi-party marketplace systems

Dynamic pricing and revenue-distribution engines for marketplaces with three or more economic participants per transaction. The work includes settlement timing, payout topology, and incentive alignment across counterparties.

04 / Methodology

Four operating principles.

Validation precedes deployment.

No subsidiary ships customer-facing functionality without an explicit validation harness. The harness is the product; the application is one consumer of it.

Empirical calibration over published assumption.

Where physical sensors are involved, the Lab generates its own calibration data rather than relying on manufacturer specifications or third-party datasets. This produces tuning data that is, in practice, proprietary by construction.

Patent-aware architecture.

Capability domains are scoped such that the underlying mechanism is patentable independent of any single product expression. Products serve as reductions to practice; the mechanism is the asset.

Capability is rented; expression is owned.

Foundation-model access is procured at the boundary of the Lab and treated as commodity input. The Lab's investment is concentrated in the layer above — calibration data, classification models, interaction patterns, and architectural mechanisms — which constitutes the durable, defendable asset.

05 / Founder

Operating principal.

Aaron Shaw
Founder & Sole Operating Principal

Prior to founding the Lab, Shaw served in autonomous systems validation at Caterpillar Inc., contributing to MineStar Command for Hauling and the GRADE dozer-control product line. His work centered on hardware-in-the-loop test bench development, sensor-fusion validation, and the operationalization of autonomous behavior on safety-critical heavy equipment.

He holds a BS in Computer Engineering from Valparaiso University, where he contributed to the institution's CubeSat program. Prior to his engineering career, he spent twelve years as the operating principal of All American Contractors LLC, completing more than one hundred residential projects — work that informs the Lab's preference for finished, deployable artifacts over indefinite prototypes.

He is currently evaluating senior engineering roles in autonomous systems, validation engineering, and defense technology.

06 / Intellectual Property

Two patent families in preparation.

Specific subsidiary products serve as reductions to practice for the filings below. Detailed technical disclosure is held until provisional disposition is complete.

Family A

Sensor-driven browser input methods

A class of techniques for translating device sensor data into structured input events suitable for interactive applications, with particular attention to motion classification under noisy real-world conditions. Status: in attorney review.

Family B

Prompt-driven content generation systems

Architectural patterns for converting structured human intent into rendered, time-coordinated media output, including instrumentation for reduction to practice across deployed product surfaces. Status: in attorney review.

07 / Contact

Inquiries.

aaron@shaw-labs.com

The founder is currently evaluating senior engineering roles in autonomous systems, validation engineering, and defense technology — across the Las Vegas, Southern California, and San Francisco Bay Area markets through July 2026.

← Back to shaw-labs.com

Hold the phone, perform a motion, label what it means. Build a vocabulary of real sensor recordings that any motion-controlled game can read.

Works best on mobile over HTTPS. Desktop fallback: arrow keys / WASD for tilt, Space for shake.

Data Source
Phone · DeviceMotion
local browser sensors
— Hz
Reads DeviceMotion + DeviceOrientation from the phone running this page. Default mode.
Sensor Logger setup: install the Watch app from the Sensor Logger companion, open the gear icon on the Logger page, enable MQTT Publish, paste the same broker URL + topic. Public broker wss://broker.hivemq.com:8884/mqtt works with no auth — pick a unique topic so you don't collide with anyone else testing.
Your Wear OS app should send JSON frames in this shape:
{ "acc": [x, y, z], "rot": [alpha, beta, gamma], "t": ms }
Or batched: { "frames": [{...}, {...}] }. rot and t are optional; acc is in m/s² with gravity.
Live Sensors LAB
Acceleration (m/s²)
X
0.00
Y
0.00
Z
0.00
Linear Acceleration (gravity removed)
X
0.00
Y
0.00
Z
0.00
Orientation (degrees)
α (compass)
0
β (pitch)
0
γ (roll)
0
Force + Buffer
Total
0.0
Linear
0.0
Buffer
0/200
Detected
Linear Force0.0
Motion Path Visualizer

X/Y motion trace · fading trail · thickness = velocity intensity · crosshair = neutral

Recording IDLE
Duration
0.00s
Samples
0
Peak Force
0.00
Match Result TEST
Label This Motion SAVE
snake_case identifier the game engine will receive
🎥
Drop MP4 here or tap to choose
reference clip of the actual physical motion
Stored locally in IndexedDB. Travels with single-motion exports.
Motion Library 0 SAVED

Universal motion grammar recorder · localStorage persistence · iOS DeviceMotion permission supported