Holmes LabAgentic Software Engineering Architect

Evidence for change. Explicit collaboration.

Holmes-Kit connects the reason for code changes. Agent Bridge connects explicitly enrolled CLI sessions. Choose the tool that fits your work.

Documentation reviewed 2026-11-05

Start with a problem: engineering notes ↗

Start independently; combine when useful

Kit connects what changes, why and how it is verified. Bridge tracks explicit peer delivery and acknowledgement. Kit is not required by Bridge; a peer message is not a Kit approval or human authorization.

Explanatory flow — not a live session or recorded execution
  1. Human intent and permission
  2. Kit specifications and checks
  3. Explicit Bridge delivery
  4. Observe actual outcome

Read a problem, then try a tool

What should an AI check before changing code?

Add whitespace handling and a default name to one greeting function. Follow the same three tests from failure to success, connecting requirements, design decisions and execution evidence.

Continue from here