Completion Check: Verify Infrastructure Is Wired

Overview

Infrastructure is not done when the code is written — it's done when it's wired into the system and actively used. Dead code is wasted effort.

The Checklist

Before declaring infrastructure complete:

• • Traced execution path from entry point to new code
• • Verified registration — handlers registered, interfaces satisfied, hooks configured
• • Confirmed correct backend — using intended database/service/config
• • Ran end-to-end test showing new code is actually invoked
• • Searched for dead code — no orphaned or parallel implementations

Verification Steps

1. Trace the Execution Path

Follow from user intent to actual code execution:

# Go: Verify handler is registered
rg "HandleFunc.*myEndpoint" cmd/ internal/
rg "mux.Handle" cmd/

# Python: Verify function is called
rg "my_function\(" src/

2. Check Registration

// Go: Is the interface satisfied?
var _ MyInterface = (*MyStruct)(nil)

// Is the handler registered in the router?
router.HandleFunc("/api/resource", handler.Create).Methods("POST")

# Python: Is the entry point wired?
# Check __init__.py exports, CLI registrations, etc.

3. Test End-to-End

Run the feature and verify new code is invoked:

# Go
go test ./... -run TestIntegration -v

# Python
uv run pytest tests/ -k "integration" -v

4. Search for Orphans

# Find functions defined but never called
rg "func \w+" --type go | # all function definitions
  # cross-reference with call sites

Common Traps

Red Flags

• •Marking "complete" without running the feature
• •Assuming code is wired because it exists
• •Building parallel implementations (old + new both present)
• •Skipping end-to-end verification