Runtime Binding Verification

Runtime Binding Verification

Mission

Close the gap between:

"an implementation exists"

and:

"this implementation is actually selected under these runtime conditions"

Start From

One high-impact abstraction, selector, factory, client, repository, handler, or mode whose active implementation matters.

Trace

Trace both directions where needed:

startup/bootstrap
→ registration / DI / provider / registry
→ selector/factory
→ config/runtime state
→ concrete implementation
→ real caller/use

and:

runtime caller
→ abstraction
→ creation/lookup
→ concrete instance
→ boundary

Search

Inspect as applicable:

• constructors and new
• dependency injection annotations/config
• service loaders/plugins
• factories/providers/builders
• registries/maps
• startup/main/application initialization
• reflection/class-name loading
• configuration mode switches
• test-only bindings vs production bindings
• legacy/inactive implementations
• fallback implementations

Counterexample Search

Search for every implementation and every creation/registration path of the abstraction.

Do not conclude from one call site.

Output

Create/update:

docs/reverse-engineering/runtime-binding/<scope>.md

Required table:

Verdict:

VERIFIED_ACTIVE
VERIFIED_ALTERNATE
INACTIVE_LEGACY
TEST_ONLY
UNRESOLVED

Promote only after counterexample search and scope check.