Resolved-identity model is in-memory only

LIMIT-RESOLUTION-001

Resolved identities exist only in memory; nothing persists them across processes.

Lifecycle

accepted

Owner

metel-frontend

Scope

architecture/spec/resolution.md#resolution

Origin

ADR-0054 (2026-09-10 amendment)

Review

revisit once an incremental-compilation or persistent-server design is actually proposed

Affects · linked records

arch.resolution.requirement-1architecture requirement

arch.resolution.requirement-2architecture requirement

ResolutionMap metel-frontend/src/identity/mod.rscode

limitationKnown limitations ↗

Limitation

The resolved-identity model (ResolutionMap, the interned identity tables) is in-memory only for this delivery. On-disk persistence and cross-process interner stability are explicitly out of scope — stated directly in ADR-0054's own 2026-09-10 amendment, not inferred.

Impact

An incremental-compilation or persistent-LSP-server design that wants identities to survive a process restart cannot rely on this model directly today; every process re-derives identities from scratch on load.

Affects

• arch.resolution.requirement-1
• arch.resolution.requirement-2

• metel-frontend/src/identity/mod.rs::ResolutionMap

Resolution

None yet. ADR-0054 frames this as a deliberate, cheap-now/expensive-later sequencing choice, not an oversight — revisit once a concrete incremental or persistent-server consumer exists.