Portfolio brief · July 2026 · San Francisco

I build applied-AI products that survive contact with real workflows.

Robotics infrastructure, creative software, native iOS, healthcare, speech, growth systems, and operational tools—from product thesis and data model through deployment, QA, and measured proof.

Product definitionBuyer, wedge, workflow, authority, failure states, evidence, and next decision.
Applied AIAgents, document intelligence, computer vision, speech, media generation, evaluation, and fallbacks.
Native systemsSwiftUI, AVFoundation, StoreKit, Kotlin, background audio, virtual devices, and device diagnostics.
Data and infrastructurePostgres, Supabase, provenance, queues, workers, Cloudflare, Railway, Vercel, and provider integrations.
Proof and releaseReference qualification, CI, TestFlight, physical-device QA, production smoke tests, rollback, and receipts.
Flagship product dossiers

What each product does, who it is for, and what proves it.

Every stage label is deliberately narrow. “Built,” “deployed,” “TestFlight,” “reference-qualified,” and “production-proven” are not interchangeable claims.

01
Physical AI infrastructure

FastCrest Tether

Deployment confidence for vision-language-action robot policies: optimize a model for the target hardware, verify it still matches the reference policy, and produce evidence that it is safe to promote.

Current stageOpen source · shippingPublic repository

Buyer / user

Robotics and embodied-AI engineers moving VLA policies from PyTorch research code onto Jetson, RTX, Apple Silicon, AMD, ROS 2, and production serving infrastructure.

The hard problem

A policy can export successfully and still be wrong, slow, incompatible with the device, or operationally unsafe. Existing tools fragment export, runtime selection, parity checks, rollout evidence, and rollback.

Core operating loop

  1. 1Inspect hardware, Python, CUDA, TensorRT, providers, and model compatibility.
  2. 2Export monolithic ONNX graphs and choose the best available runtime path.
  3. 3Prove reference-vs-optimized parity with seeded inputs and numerical receipts.
  4. 4Benchmark latency, promote a proof packet, and retain rollback/reproduction evidence.

Evidence / shipped depth

  • 75 GitHub stars and 17 forks on the public repository.
  • End-to-end cosine parity +1.000000 on SmolVLA, π0, π0.5, and GR00T N1.6.
  • Measured 19.49 ms TensorRT vs 108.11 ms ORT-CUDA on SmolVLA/A10G: 5.55×.
  • Fast-kernel gate: 91.3% vs 85.3% native ORT across 600 LIBERO episodes.
  • PyPI distribution, clean-install bootstrap, ZMQ transport, ROS 2 starter adapters.
Technical surface
PythonCUDATensorRTONNX RuntimeTritonZMQROS 2Modal
Proof boundary

The public receipts establish measured export/runtime behavior. They do not claim every robot, checkpoint, or physical deployment is qualified.

02
Robotics data assay and release

FastCrest Cupel

Turn messy robot demonstrations into a target-specific, evidence-qualified dataset release—without destroying the raw evidence or pretending uncertainty is a pass.

Current stageRuntime-complete reference surface

Buyer / user

Robot-learning teams with LeRobot/TEL, egocentric, spatial, UMI, or multimodal demonstrations and a named policy, evaluator, task, and training budget.

The hard problem

Robot datasets often contain timing defects, missing evidence, leakage, rights constraints, inconsistent frames, and transformations whose downstream value is never measured.

Core operating loop

  1. 1Ingest and checksum immutable raw bytes; preserve lineage and rights state.
  2. 2Profile timing, media, missingness, conformance, uncertainty, and defect evidence.
  3. 3Replay raw vs derived episodes and preview reversible treatments.
  4. 4Compile a target-specific candidate and compare utility under a matched budget.
  5. 5Approve, release, verify, recall, and recommend the next bounded data action.

Evidence / shipped depth

  • Reference corpus: 11 pinned files, 91,340,741 bytes, 25,000 frames, 50 episodes.
  • Persistent rescue jobs retain inputs, attempts, failures, and results across restarts.
  • Executable cadence fault injection and reversible repair.
  • Fail-closed TEL, EGO, spatial-3D, and UMI conformance profiles.
  • Typed verdicts distinguish pass, fail, unknown, unsupported, inconclusive, blocked, and abstain.
  • Executable trace program targets 1,732 canonical product requirements.
Technical surface
PythonLeRobotPyArrowPostgresEvidence kernelDataset CIProvenance
Proof boundary

Reference/runtime completion is not pilot qualification. Physical-corpus, named-customer, and controlled-production evidence remain separate gates.

03
AI-native video creation

ReactCut

One video product with two synchronized ways of thinking: an AI node canvas for rapid creative experimentation and a precise CapCut-style timeline for finishing the edit.

Current stageWeb + native iOS · active shippingProduct site

Buyer / user

Creators, app teams, and marketers producing reaction videos, demos, ads, and short-form content that mix generated media with exact editorial control.

The hard problem

AI generation tools are fast but imprecise; traditional editors are precise but slow to explore. Moving assets between them creates export/re-import friction and breaks creative context.

Core operating loop

  1. 1Build image, video, audio, and transformation chains on a visual node canvas.
  2. 2Run edge-driven generation, inspect outputs inline, and star useful assets.
  3. 3Switch the same asset store into a multitrack timeline without re-importing.
  4. 4Trim, position, layer, synchronize, and export with native playback diagnostics.

Evidence / shipped depth

  • Next.js node editor built with Zustand and @xyflow/react.
  • Native SwiftUI editor with AVFoundation playback and timeline diagnostics.
  • Shared Rust/yrs document core designed for web WASM and iOS UniFFI.
  • Real chain execution, drag-edge-to-create, marquee selection, and in-node generation.
  • TestFlight distribution plus trace-backed QA for first-frame, drift, preroll, and memory.
Technical surface
SwiftUIAVFoundationTypeScriptNext.jsRustWASMUniFFICRDT
Proof boundary

A successful build or simulator trace is not treated as proof of a physical-device playback fix; generation pixels require live provider receipts.

04
Autonomous growth and creator intelligence

Meadow + Framefound

Run a per-brand growth loop that generates content, observes real outcomes, and changes the next action—while giving operators video-native evidence for creator and format decisions.

Current stageOperating product · active development

Buyer / user

DTC brands with product-market fit and inventory but an underperforming TikTok Shop, affiliate, or short-form organic motion.

The hard problem

Brands produce disconnected content, recruit affiliates who go dormant, and make creator decisions from profiles instead of the videos and outcomes that actually demonstrate fit.

Core operating loop

  1. 1Map live trends onto a brand-specific recipe, script, and five-beat shot sheet.
  2. 2Render vertical creative from real product references behind human approval gates.
  3. 3Log forecasts and ingest watch time, retention, sentiment, shares, saves, and GMV.
  4. 4Learn per account; change one creative lever at a time and preserve the outcome trail.
  5. 5In Framefound, research creators from video evidence, cluster patterns, shortlist, and compare.

Evidence / shipped depth

  • Early signed-brand operating motion; names, fees, and commission terms remain private.
  • Immutable, provider-tagged action/observation ledger with predictions tied to outcomes.
  • Specialist-agent pipelines, outline-before-action gates, trace replay, and durable artifacts.
  • Video evidence includes first frames, watched/transcript state, timestamps, and provenance.
  • Encrypted per-customer vault using AES-256-GCM and HKDF-SHA-256 workspace derivation.
Technical surface
Next.jsTypeScriptSupabaseAgentsBrowserbaseTikTokBufferVideo AI
Proof boundary

A queued scraper or generated schema is not counted as research proof until media, transcript/watch evidence, and a visible decision receipt exist.

05
Consumer AI · native iOS

Aether

A personalized visualization practice that is useful offline, becomes richer with cloud generation, and turns a user’s own intentions into repeatable audio, visual, and reflection rituals.

Current stageMVP+ · TestFlight track

Buyer / user

Consumers using guided visualization, affirmations, dream reflection, journaling, and intentional daily routines.

The hard problem

Most manifestation apps replay generic content, require a connection for the core loop, and treat personalization as a shallow prompt rather than a durable private context.

Core operating loop

  1. 1Capture desires, context, narrator, tone, soundscape, duration, and reminders.
  2. 2Generate title-first playlists; create a full present-tense story only when selected.
  3. 3Play narrated sessions with karaoke highlighting, ambient mixing, and lock-screen controls.
  4. 4Carry sessions into a searchable library, journal, vision board, and affirmation deck.

Evidence / shipped depth

  • Native SwiftUI application with offline-first deterministic composition.
  • Cloudflare proxy keeps model/provider keys out of the app and supports graceful fallback.
  • Cartesia-first narration, OpenAI fallback, then AVSpeechSynthesizer on-device fallback.
  • Procedural AVAudioEngine soundscapes; no bundled ambient audio assets.
  • StoreKit 2 monthly/annual paywall, background audio, reminders, library, journal, and vision board.
Technical surface
SwiftUIAVAudioEngineStoreKit 2Cloudflare WorkersOpenAICartesiaCloudKit
Proof boundary

TestFlight availability, provider configuration, entitlement restore, and physical-device audio are reported as distinct readiness receipts.

06
PBM evidence and action

RxBasis

The evidence and action layer between raw PBM documents and a defensible renewal decision for self-insured employers, brokers, and benefits consultants.

Current stageDeployed application · expanding

Buyer / user

Benefits leaders at self-insured employers, PBM consultants, and brokers managing contract terms, claims behavior, vendor responses, and renewals.

The hard problem

PBM contracts, claims, rebates, formularies, MAC lists, invoices, and renewal material arrive in different formats; potential leakage is difficult to trace back to the clause or record that supports it.

Core operating loop

  1. 1Upload evidence and extract facts, sources, confidence, and missing inputs.
  2. 2Map contract clauses to claims, spread, rebate, MAC, formulary, specialty, and NDC evidence.
  3. 3Flag potential leakage and evidence gaps without overstating legal conclusions.
  4. 4Draft data requests, challenge questions, follow-ups, response trackers, and renewal packets.

Evidence / shipped depth

  • Separate Uploads evidence hub from Analysis readiness and variance review.
  • Contract-to-claims audit, action center, verification, renewal, and data-rights modules.
  • Live CMS NADAC, NPPES, FDA Orange Book, and AHRQ MEPS data surfaces.
  • Next.js frontend, Python/FastAPI backend, controlled internal-Pro access, and regression gates.
  • Buyer language deliberately uses “potential leakage,” “flagged for review,” and “evidence-backed finding.”
Technical surface
Next.jsFastAPIPythonGPT-5 miniRechartsCMS/FDA dataDocument AI
Proof boundary

RxBasis organizes evidence and workflows; it does not replace fiduciary, legal, actuarial, or licensed professional judgment.

07
Funded-cohort operations

EcomLinked Tracker

A mobile-first operating system for funded ecommerce cohorts: submissions, review, meetings, fulfillment, learning, member visibility, and accountability in one role-aware workflow.

Current stageProduction · live-verified

Buyer / user

Program owners, cohort managers, reviewers, and funded ecommerce members who need auditable operating decisions rather than scattered forms, chats, and spreadsheets.

The hard problem

Cohort operations combine intake, voting, store sequencing, late joins, attendance, learning, fulfillment, integrity, and member communication—each with different visibility and authority rules.

Core operating loop

  1. 1Verify paid intake, assign a member to a group, and preserve assignment exceptions.
  2. 2Collect structured submissions and adaptive reviews; deterministically score and freeze human results.
  3. 3Run sealed Shadow AI, compare only after unsealing, inspect integrity, and stage learning reports.
  4. 4Approve, publish, expose the right outcome to each role, and preserve source-linked receipts.

Evidence / shipped depth

  • Deployed on Railway with production Supabase migrations applied.
  • Full v2 workflow live-verified: submission through publication and predictive-accuracy analysis.
  • Browserbase preview PNG storage verified with cleanup residue 0.
  • Role smoke covers owner, manager, reviewer, and member permissions.
  • Versioned fulfillment rules handle late joins, manager approval, and member-edit review reset.
Technical surface
Next.jsTypeScriptSupabaseRailwayStripeBrowserbaseResend
Proof boundary

Internal targets, voter identity, shortfalls, and cross-member fulfillment outcomes remain restricted to operational roles.

08
Real-time speech transformation

AccSync

A person-controlled real-time accent layer that reshapes pronunciation toward a chosen target while preserving speaker identity, intelligibility, and meeting-app compatibility.

Current stageResearch product · delivery path proven

Buyer / user

People who want more control over how their speech is perceived across calls and meetings without replacing their voice or identity.

The hard problem

Accent conversion is a multi-objective systems problem: pronunciation must move, identity and words must survive, latency must stay interactive, and classifier movement must correspond to audible target progress.

Core operating loop

  1. 1Capture normal speech and route transformed audio through a native virtual microphone.
  2. 2Predict target phoneme/PPG-duration behavior while preserving source-speaker characteristics.
  3. 3Evaluate identity, WER, accent movement, acoustic-reference progress, robustness, and latency.
  4. 4Refuse a product claim when a metric improves but listening/acoustic evidence disagrees.

Evidence / shipped depth

  • Cloud preview live; native virtual-microphone delivery proven end to end.
  • Held-out identity preservation reached SECS ≈0.94 in an early gate.
  • Robustness work measures MP3/low-pass degradation, WER, identity, and accent movement separately.
  • Hundreds of experiment milestones retain negative results instead of cherry-picking classifier wins.
  • Current honest state: delivery and evaluation are deep; the final real-time conversion engine is not solved.
Technical surface
PythonPyTorchAudio DSPASRECAPAPPGVirtual microphoneRailway
Proof boundary

Offline teacher or classifier movement is not labeled a product model unless same-speaker acoustic/listening and real-time gates also pass.

09
Clinical capture and follow-through

Santhica

An India-focused clinical capture system that turns prescription and patient evidence into structured, permissioned workflows with explicit audit and safety boundaries.

Current stageiOS + Android + backend

Buyer / user

Doctors, clinics, and patients handling prescriptions, credentials, patient records, documents, and follow-up across mobile devices.

The hard problem

Clinical information arrives through photos and documents, while identity, consent, organization boundaries, retention, and abnormal-result follow-through require much stronger controls than a generic consumer upload flow.

Core operating loop

  1. 1Authenticate providers, create organization identity, and verify credentials.
  2. 2Create patients and upload documents directly to signed storage locations.
  3. 3Trigger asynchronous vision extraction and write structured prescription evidence.
  4. 4Apply organization-aware access, rate limits, retention jobs, soft deletion, and PHI audit trails.

Evidence / shipped depth

  • Native iOS and Android clients plus Supabase/Postgres backend.
  • Versioned OpenAPI contract and production-only release branch discipline.
  • JWT-validated Edge Function API; mobile clients do not write directly to the database.
  • GPT-4o vision extraction pipeline with structured persistence.
  • RLS, signed uploads, PHI access logging, rate limiting, and retention migrations.
Technical surface
SwiftKotlinTypeScriptSupabasePostgresEdge FunctionsOpenAPIVision AI
Proof boundary

AI extraction is evidence capture, not diagnosis. Clinical authority and escalation remain human-owned.

Additional systems

The surrounding portfolio.

Adjacent infrastructure, research, studio, and community products that extend the main product work.

10Tether Studio

Local-first Policy Health IDE for finding contract mismatches across policy, dataset, runtime, timing, safety, and target; turns findings into evidence, repros, saved checks, and release gates.

11SimForge

Cloud robot simulation and reinforcement-learning training infrastructure built around on-demand Isaac Lab workflows.

12Fleet Release

Centralized rollout, rollback, desired-state, and release-evidence control plane for robot fleets.

13PairLaunch

Full-stack product studio and public operating surface for shipping focused software products.

14Contradiction Finder

Agent that scans Slack, Gmail, Notion, and Calendar context to identify conflicting claims and help reconcile them.

15BooKoo Apps

A portfolio of community and commerce products including Mailoo, Trackoo, Teamoo, Funneloo, Ticketoo, Pingoo, and live-community utilities.

Operating method

Depth without hand-waving.

The common thread is not an industry or framework. It is taking an ambiguous, high-friction workflow and building the product, evidence model, authority boundaries, and release path together.

01Find the sellable wedge.

Start with one buyer, painful input, decisive output, and a falsifiable reason to act.

02Model the whole workflow.

Define states, owners, permissions, retries, fallbacks, failure semantics, and what must remain unknown.

03Build the evidence loop.

Attach source, provenance, denominator, confidence, and a downstream outcome to every important claim.

04Ship across the boundary.

Separate compilation, simulator QA, TestFlight, real-device proof, production deploy, and customer qualification.

Current focus

Better evidence and interfaces for intelligent systems moving into the real world.