Guest signal · Read-only access
Each product starts with a human problem, then earns its complexity through useful decisions, thoughtful safeguards, and an interface people can actually live with.
Selected systems
Guest mode shows only deliberately public context. Detailed work notes and approved collaborations live behind account access.
Operations
Applicant intake, structured review, training, collaboration, and deployment readiness in one accountable flow.
Operations
Role-aware property operations for work orders, assignments, messaging, and map-led maintenance.
Personal systems
A private medical workspace for records, medications, appointments, files, and care context.
Community
An independent social platform for accounts, posts, groups, and internal conversations across devices.
Personal systems
Phone-first scheduling, tasks, rewards, pets, and games for households and teams.
Explorations
A local virtual office for agents, work orders, approvals, memory, and supervised processes.
Explorations
A browser-based science-fiction roguelike built around wave defense, turrets, rooms, and the Spire.
How the work moves
I treat software as an operating environment, not a pile of screens. The useful question is always what the person needs to understand, decide, and do next.
Map the people, constraints, privacy boundary, and definition of done before the interface grows.
Identity, data, permissions, and core workflows arrive early enough to shape the product honestly.
Motion, hierarchy, and feedback clarify what changed and why—without turning the interface into noise.
Client visibility is opt-in
Client work can appear in the authenticated portfolio when the client explicitly wants it shared. Names, details, and outcomes stay hidden otherwise.
Unlock the workspace