Product Engineer · Systems Builder · Execution Infrastructure
Building durable software products across AI, media, and infrastructure.
I design and build execution-first product systems at the intersection of software, AI, and media.
Chief builder @ Justyn Clark Network (JCN) - a development studio focused on systems that value clear intent, determinism, product judgment, and durability over hype and abstraction.
The leverage in senior software work is shifting from just knowing how to build to knowing what should be built, what should not be built, and how to shape products people actually want to use.
My work typically centers on:
- product engineering from ambiguous intent to shipped systems
- execution models that survive interruptions
- schema-first platforms that scale cleanly
- AI systems with real constraints
- audio, video, and media pipelines
- developer tooling that does real work
These are active, evolving systems - not experiments or shelfware.
🛠️ SMALL Protocol - A shared language for making work traceable, resumable, and verifiable. Think "source control for execution state."
🎧 JustBeatz Music - A full-stack music platform focused on audio playback, media storage, and metadata management.
🔗 wakeplane - Durable scheduling and automated execution engine for long-running systems.
🔗 devports - A lightweight CLI for managing development ports, services, and local network URLs.
🧵 tbe - Thread Based Engineering. A deterministic, policy-gated execution kernel with replayable evidence.
🔄 loopexec - A CLI for running bounded execution loops without losing context or progress. Designed to keep work moving forward, even when everything else stops. (in progress)
🏛️ Boardroom - A Pi-based executive deliberation pack from Justin Clark Network for running structured CEO and board workflows from decision briefs.
三 musketeer - A command-line companion for running coordinated work across multiple agents and tools. Built for alignment, guardrails, and keeping execution pointed in the same direction. (in progress)
- Product engineering judgment: what to build, what not to build, and why
- Deterministic agent execution and safety
- CI-grade invariant enforcement
- Local-first tooling and CLI systems
- Execution lineage and reproducibility
- Audio + media systems built like software, not toys
- The Operator Is Not the Bottleneck
- The Operator Stack: Running a Distributed Studio From Apple Silicon
- SMALL Protocol v1.0.0 Release Notes
- Why Execution Needs a Contract
Most work happens in active product repositories and private systems. Public code reflects ideas that survived contact with reality.