Architecture designs, current-state architecture, and decision records can now follow each adopter's own repository or external destinations. Explicit destinations, policy, established conventions, and optional configuration are resolved by semantic role; catalogue paths remain fallback offers.
Architect stays useful as an independent user pack. It can remain chat-only, save to an exactly confirmed personal workspace, consume Core's repository resolution when compatible, or produce a truthful repository handoff when Core is absent.