Enterprises don't build every architecture from scratch — they reuse. But reuse only works if you can classify assets ('is this generic enough to reuse here?') and find them. The Enterprise Continuum is the classification scheme; the Architecture Repository is where the assets live.

Exam-wise this topic is about two things you must not muddle: the Continuum (a way of classifying) and the Repository (a place for storing).

The Enterprise Continuum classifies architecture and solution artefacts by how generic or specific they are, and has two halves that run in parallel:

The Architecture Continuum — the descriptions: Foundation → Common Systems → Industry → Organization-Specific. The Solutions Continuum — the realisations of those descriptions: generic products → systems solutions → industry solutions → organisation-specific solutions.

Movement is bidirectional: you specialise generic assets down the continuum for reuse, and you generalise good organisation-specific work up it so others can reuse it.

A payments platform: a generic 'secure messaging' pattern is a Foundation architecture; a reusable 'event-driven microservices' blueprint is Common Systems; an 'ISO 20022 payments' reference model is Industry; and your bank's specific payments architecture is Organization-Specific. On the Solutions side, the org-specific solution might realise it with a named message bus and your own services.

The Architecture Repository is the store that holds the outputs and governance of architecture work. Its top-level parts are: the Architecture Metamodel, the Architecture Capability, the Architecture Landscape (assets in use/planned at points in time — Strategic/Segment/Capability levels), the Standards Information Base (SIB), the Reference Library, the Governance Log, the Architecture Requirements Repository, and the Solutions Landscape.

The Continuum classifies; the Repository stores. The Reference Library, for instance, is organised using the Enterprise Continuum.

ADM outputs (TGF‑C2) are filed here and reused on the next cycle. The building blocks you'll meet in TGF‑C4 are classified along the continuum (an ABB may be a Common Systems asset; an SBB an org-specific one). Governance decisions land in the Governance Log.