Runtime Discovery

Kind: mechanism

Layer: Extensibility Core

Aliases: Auto-Discovery, Registry/Discovery Mechanism

Record: architecture:runtime-discovery

Severity: contextual

Scope: runtime, plugin, module, service

Canonical: Ontology

A mechanism that finds the available handlers, plugins or services at startup by matching a naming convention, a file pattern or metadata, and registers each one it finds in place of a hand-written list.

Listed in Architecture principles, after Domain Service and before Service Discovery.

Requires

• Metadata
• Convention

Reinforces

• Runtime Extensibility

Enables

• Plugin Architecture
• Service Discovery
• Self-Registration

Conflicts with

• Compile-Time Binding
• Manual Registration

In tension with

• Predictability
• Static Analysis
• Startup Cost

Tensions

• Runtime Discovery / Predictability
• Runtime Discovery / Static Analysis
• Runtime Discovery / Startup Cost

Contracts

• Runtime Discovery

Violated by

• Manual Registration

Refactored by

• Registry Pattern
• Static Analysis
• Manifest-Based Design

Severity

• contextual

Category

• Runtime Discovery / Dynamic Binding

Enforced by

• rules/eslint/closure-barrel-must-be-glob.eslint.rule.ts

Reinforced by

• Self-Describing Architecture
• Metadata-Driven Design
• Capability Declaration
• Reflection

Linked from

• When rules collide
• The filesystem is the architecture
• Definitions own what, code owns how
• The direction axis
• The honest gaps
• Runtime Discovery / Dynamic Binding
• Correctness / Determinism / Verification
• Metadata / Self-Description / Declarative Systems
• Metaprogramming / Language-Oriented Architecture
• Plugin / Extensibility / IoC
• Core Vocabulary
• Runtime Discovery / Dynamic Binding
• Schema / Canonical Data / Semantics
• Architecture
• Severity levels
• The resolutions

in this codebase

• registerPage
• presentation/records
• presentation/records/records.barrel.ts