A building program is a list of rooms, square footages, and functional relationships. That list doesn't become architecture until you translate it into a spatial layout that respects which spaces need to sit next to each other, which ones can be nearby but separated by distance, and which ones must be kept apart entirely.

This translation process is where programming meets design. You're working with three relationship types: adjacency (spaces that share a wall or direct connection), proximity (spaces within a short walking distance), and separation (spaces deliberately kept apart for security, noise, contamination, or operational reasons). Every building type has its own version of these rules. A courthouse demands three distinct circulation paths so judges never cross paths with defendants in custody. A hospital needs sterile processing adjacent to surgical suites but separated from public corridors. A school needs classrooms clustered by grade but music rooms isolated from testing areas.

The tools for this work are familiar: adjacency matrices that score every space-to-space relationship, bubble diagrams that explore possible arrangements, and stacking diagrams that assign departments to floors. But choosing between competing adjacency demands, especially when they conflict with each other or with site constraints, is where the evaluative judgment comes in. The ARE tests your ability to make those judgment calls.