rea/docs/adr
N0zoM1z0 941d7101dd feat(session): add explicit provider registry and target binding
Introduce deterministic deep-provider discovery and immutable per-target routing while retaining disjoint artifact and native capability families.

Expose provider selection consistently through MCP, CLI, environment configuration, session status, prompt completion, typed diagnostics, and generated documentation. Preserve exact provider/profile provenance without request racing or transparent fallback.

Cover overlapping providers, ambiguity, rejection details, cancellation, restoration, package installation, and real Hopper target switching.
2026-07-15 22:13:48 +09:00
..
0001-provider-selection-and-analysis-profiles.md feat(session): add explicit provider registry and target binding 2026-07-15 22:13:48 +09:00
README.md docs(architecture): define provider selection and analysis profiles 2026-07-15 18:04:32 +08:00

README.md

Architecture decision records

Accepted decisions describe the architecture that implementation PRs must follow. Acceptance does not by itself mean the behavior is shipped; each record states its implementation status separately.

ADR Status Implementation
0001: Provider selection and analysis profiles Accepted Planned