Figure 1.1, “SVK's Architecture” illustrates what one might call a “mile-high” view of SVK's design.
Because of the extremely flexible nature of SVK, it's very difficult to pin down one definitive way of describing its architecture; either in words or graphically. The way in which it all works depends largely on the source control model that you're currently using, and that gets even more complicated when you consider that you could be using more than one model with multiple projects in the same svk installation.
On one end is a Subversion repository that holds all of your versioned data. On the other end is your Subversion client program, which manages local reflections of portions of that versioned data (called “working copies”). Between these extremes are multiple routes through various Repository Access (RA) layers. Some of these routes go across computer networks and through network servers which then access the repository. Others bypass the network altogether and access the repository directly.