Specs are intentionally narrower than architecture/domain docs. They capture focused investigations, audits, or temporary design planning where the main value is concentrated detail, not broad onboarding context.
When a spec becomes stable, move its lasting guidance into
architecture/, domains/, interfaces/, or operations/ and keep the spec
as historical context (or remove it if it no longer adds value).