Product Systems Designer
System-level thinking
for AI-native software.
Not UI design. Platform architecture.
I study how AI-native products are structured at the system level — runtime layers, governance models, multi-product navigation, and the design decisions that scale across platform boundaries.
Invariant Framework
Invariant Framework
Structure enforced.
Not documented.
The Invariant Design Language is a formal specification for design systems that must hold under automated execution. It defines three layers: doctrine, grammar, and runtime — each with explicit constraints and enforcement boundaries.
Specification carries enforcement. Documentation does not. The framework exists because AI-generated interfaces require a structural contract, not a style guide.
View the Framework →Architecture
Three Layers. One Platform.
Each layer depends only on layers beneath it. Cross-layer dependencies are a specification violation.
Case Study — Zoho
Runtime Continuity as
Platform Primitive.
Zoho operates 55+ products across a federated platform without a unified runtime contract. This case study examines the structural consequences: navigation fragmentation, context loss across product boundaries, and the absence of a shared session layer.
Read the Full Analysis →Runtime Continuity Model
Case Studies
Platform-level analyses.
Research
Runtime Continuity
as Platform Primitive.
A formal examination of how design systems maintain structural coherence when interface output is partially or fully generated by automated systems. Covers schema contracts, prompt primitives, and the role of the runtime layer as a validation boundary.
View Research Publications →Research Index
Work With Me
Structured engagements.
System-level scope.
I work with product teams who need architectural clarity — not more screens. If you are building a platform and need someone who can map the system before designing the surface, let's talk.