Builder of operating systems, recovery tools, creative platforms, and story worlds.
I build software under Bobby’s Workshop and Blue Phoenix Studios, with one rule running through the entire portfolio:
Evidence before adjectives. A product earns words like secure, reliable, compatible, polished, and production-ready through working code, retained tests, and honest limitations.
A from-scratch x86_64 operating-system program built around the Phoenix Prime Kernel, protected userspace, verifiable recovery, and owner-controlled computing.
Current verified baseline: long-mode kernel boot, content-addressed initramfs validation, and a separate ELF64 process executing at CPL3 under QEMU. ARCWYRE remains active systems research, not a public production release.
Device intelligence, diagnostics, repair planning, evidence orchestration, and cross-device coordination for the Bobby’s Workshop ecosystem.
Rust-powered USB discovery and the safe desktop foundation for signed boot and recovery media. Read-only detection and explicit safety boundaries come first.
The human-facing repair and recovery workspace that brings diagnostics, guided workflows, case records, evidence, and approved device actions into one professional interface.
A personal insight platform combining astrology, numerology, Human Design, compatibility, daily guidance, web, and mobile delivery.
A mythic platform-fighter and story universe centered on memory, identity, transformation, and original beast-hybrid heroes.
A production and canon platform for characters, factions, timelines, scenes, storyboards, lore rules, and franchise-scale creative workflows.
An AI-assisted writing, OCR, research, editing, and publishing studio with unit, end-to-end, performance, and desktop workflow foundations.
A story-generation platform for turning ideas into structured children’s-book drafts and creative production assets.
- Atlas Verify — case-based verification and research tooling
- REFORGE OS — repair and restoration experience research
- Super Bobby’s World of Secret Rooms — interactive game and world experimentation
- Velocity Systems — performance and systems experiments
- Put Together — early product exploration
Private laboratories include Sonic Codex, Universal Cart, Dad’s Million Miles, patient-care product research, and additional workshop experiments.
Blue Phoenix Studios
└── Bobby’s Workshop
├── ARCWYRE Native from-scratch operating system
├── PhoenixCore diagnostics and recovery intelligence
├── Phoenix Key safe boot and recovery media experience
├── BootForge reusable USB and boot primitives
├── Soul Codex personal insight platform
├── Phoenix Creator Studio creative production and canon platform
├── Ghost Writer writing and publishing studio
└── Original worlds Kai-Jax, Rainstorms, and future franchises
Each flagship remains a separate product and repository. Shared low-level components use versioned contracts instead of being silently copied into whichever repository last declared itself the center of the universe.
Every flagship is being developed toward the same long-term standard:
- a memorable identity and unmistakable purpose
- a fast, accessible, delightful first-run experience
- stable builds and reproducible release evidence
- strong onboarding, screenshots, demos, and documentation
- tests for happy paths, failures, recovery, and data safety
- consistent design language without making every product look identical
- community-ready issue templates, contribution paths, changelogs, and roadmaps
- honest status labels and no fictional completion percentages
See the Fan-Favorite Product Standard for the portfolio-wide quality gates.
- ARCWYRE R12 protected userspace and fault containment
- PhoenixCore and Phoenix Key contract cleanup and hardware-proof lanes
- Soul Codex mobile release quality
- Kai-Jax movement, combat feel, continuity, and playable vertical slices
- Phoenix Creator Studio production-readiness and creator delight
- Portfolio-wide README, CI, security, release, accessibility, and visual polish
Build tools that empower people.
Make complexity understandable.
Design recovery before failure arrives.
Treat polish as engineering, not decoration.
Let the code, tests, users, and evidence decide when something is ready.