Holmes LabAgentic Software Engineering Architect

SELECTED WORK / DECISIONS & EVIDENCE

Products, platforms.
The decisions behind them.

A professional foundation in medical software. A personal practice in agentic engineering. Different contexts, connected by the work of building reliable systems.

Architecture you can inspect

Follow the connections, then inspect the actual tool captures.

PROFESSIONAL EXPERIENCE

The engineering behind the products

I moved from imaging control and hardware interfaces to shaping software strategy across ultrasound product families. From H60/PT60A system architecture, I went on to lead SPLE platform development, One Branch and UX unification across the HS60 and V8 families and Z20/R20, connecting development projects and teams to commercial delivery.

Explore the technical decisions and roles ↗

Holmes-Kit, Jarvis and Holmes Lab are personal projects. They do not represent my employer’s products or official position.

ENGINEERING HARNESS

From requirements to code impact, connected by evidence.

The problem — Faster code generation does not remove the need to explain a change or keep it within scope. Longer tasks increase the distance between initial intent and implementation.

My direction — I am building toward an Agentic Software Engineering Harness that combines precise requirements–design–code–test traceability with Code Property Graph (CPG) analysis. Specification links explain why a change exists; code structure and flow analysis inform change impact; test execution evidence records what was verified.

Three questions for every change — What requirement does it satisfy? What does it affect? What evidence verifies it? I aim for bidirectional traceability: follow a requirement to code and tests, then trace a code change back to affected requirements and verification gaps. A CPG alone does not establish requirement links. Their accuracy and freshness, and unresolved analysis relationships, matter too.

People and agents — People decide the problem, authority and acceptance criteria. Agents carry out tests and implementation tied to specifications. Automated checks and human review serve different purposes.

My practice here — I connect Holmes Lab’s requirements, design, implementation and test specifications, and record tests around changes. Tool binding, hook configuration and observed execution are treated as separate evidence.

Evidence & limits: My ambition is world-class traceability and change impact analysis. Progress must be evaluated through missed impacts, false positives, link accuracy and freshness, and verification results from actual agent work. Independent benchmarks and current execution transcripts are not published here. This introduction does not guarantee that all errors are blocked or that enforcement is active in every environment.

PERSONAL & FAMILY AI

Useful everyday AI — and the conditions for trusting it.

The problem — A personal and family assistant needs more than good answers. What it remembers, which actions it may take and how outcomes are verified are part of the product.

My decision — I keep the personal/family assistant separate from the public portfolio and retain the local Mac Studio operating direction. Family conversations, memory and tools are not shared with the public website.

What I verify — I distinguish understanding a request, calling a tool and achieving an outcome. Questions raised by operation feed back into permission boundaries and verification criteria.

What I share — I explain the purpose and architectural decisions behind the project. Family conversations and operational logs are not demonstration material. Project conversations continue on LinkedIn.

JARVIS / REAL-TIME VOICE & CHARACTER

Jarvis: real-time voice and character demo

Ask about AI coding. Watch Jarvis listen, think and speak through its animated character.

Conversation topic: Holmes-Kit. The recording demonstrates Jarvis’s voice conversation and character responses.

Prepared with public Holmes-Kit references. Questions use synthetic speech; answers are actual Jarvis real-time responses. Waiting intervals were shortened and volume balanced. This is a recording, not a live connection to the personal assistant.

Specifications and test evidence reduce risk; they do not guarantee error-free software or require human approval for every edit.

About the conversation topic: Holmes-Kit ↗
Actual recorded character and voice responses · English
Read the conversation

Question
When I ask AI to write code, I worry it might change things I never asked for. How can Holmes Kit help? Answer in English in two short sentences, without personal names or memories.

Jarvis
It keeps development within approved specifications, which reduces the chance of unrelated changes. It also links requirements to test evidence, making modifications easier to review and verify.

Question
If AI says the tests passed, should I just trust it? Why do actual execution results and evidence linked to requirements matter?

Jarvis
No. “Tests passed” alone isn’t enough to trust the system. Evidence linked to requirements and real execution results shows it behaves as intended and supports confident validation.

Evidence & limits: This page is not an evaluation of every assistant capability. Public-web notification integration, latency and reliability measurements are not claimed as complete in this case.

THIS SITE · IN DEVELOPMENT

A place to understand the work and start a thoughtful conversation.

The problem I want to solve — A list of roles and projects rarely explains the decisions I have made. Visitors need context, evidence and limits before a natural path to conversation.

My approach — I use bilingual static content to share my engineering journey, product platforms and personal projects. Contact continues on LinkedIn.

What I focus on — Clear writing, visual explanations and inspectable evidence. Accessibility, mobile readability and consistent color and typography are part of the product.

What I verify — I check bilingual builds, content and responsive views in a real browser. Local verification and public service operation are different levels of evidence.

Evidence & limits: I build, publish and continue to develop this site. I record local checks and deployment verification separately, and assess accessibility and performance in the public environment.

Below: explanatory architecture diagrams and static tool captures. Use the interactive explorer above to inspect persisted GraphDB relationships.

Discuss an engineering question ↗