System kernel
A computational artifact. Every surface, seam and cavity maps to a software concept — nothing here is decoration.
Outer shell → product boundaryI design products at the intersection of business, architecture and engineering.
A computational artifact. Every surface, seam and cavity maps to a software concept — nothing here is decoration.
Outer shell → product boundaryThe product is what the world touches. Underneath it, structure: a chassis of contracts holding the capabilities in place.
Chassis → contractsSeventeen modules, each owning one decision and its data. The core executes; the modules decide.
Modules → domains · core → executionRequests, data and events move between capabilities through explicit paths — never through a shared shortcut.
Pathways → requests · data · eventsGovernance and security sit above the capabilities. Infrastructure runs beneath them, and neither leaks into the other.
Control layer → governance · base → infrastructureAt VIA this shape runs a marketplace: six applications, seventeen services, real-time workflows and geospatial dispatch — shown here as principle, not topology.
Packets → real-time workflowsSignals rise from every module to one monitoring surface. If you cannot see it, it is not in production yet.
Telemetry → observabilityAI agents run bounded parallel work beside the kernel. Nothing enters without passing the human gate.
Rails → AI agents · gate → human approvalA specification enters the kernel. Bounded workstreams split out, each produces a change artifact, and every artifact passes architecture, test and security gates before a human approves the release. Scroll to run the sequence.
Business problem to product model to production, and back through telemetry and feedback. Scrolling moves you around the loop.
Business problemThe operating system for a marketplace: six applications on a seventeen-service platform with real-time workflows, geospatial dispatch, shared identity and gated releases.
Product engineering and digital experience for a premium furniture brand.
Commercial real-estate digital experience and marketing platform.
A simulated RFID-enabled campus: attendance, movement and transaction events feeding decision-tree and random-forest models. No hardware was deployed — the value was in the modelling.
Admissions, wards, laboratory and discharge in one operational system. Patient journeys are modelled as workflows, so clinicians see the next step and administrators see the whole floor.
Reservations, rooms, front desk and housekeeping on one timeline. Availability is a single source of truth from the moment a booking arrives until the room is turned over.
Declarative environments, provisioning pipelines and health signals. Infrastructure is described, then reconciled — provisioned, balanced and scaled without being hand-built.
Tools for teams that work together: shared boards, tasks and conversations built around how work actually moves between people.
A health-tech concept for a national network: one patient record, shared securely between clinics, laboratories and hospitals, so care continues wherever the patient goes.
I turn operational complexity into systems people can actually use.