- Perhaps you need Related Work sections that compare/contrast yours to the others.

? The second and third paragraphs of section 2 seems to me to make a little too
  many assertions without really backing them up. Also, having an example 3rd
  party app for explanation would help.

x Is there some paper on ASDF that you can reference?

x Maybe add a reference for how URLs are structured?

x In "further work" you talk about invalidating classes. To what extent is that
  already solved by the class invalidation and redefinition support in CLOS?

x I think 3.1 might be subdivided into more sections.

x I'd add a section with a list of radiance applications, high level overviews,
  their challenged and how radiance solved them

x Is the mention of a lack of a special package, after the implementation of
  the cache interface, really necessary? ("Particularly, the above...")

x It might need to be made more clear that the code in the routing section is
  on the administrator's side.

x The Clip thing might need a tiny example.

x Please add a definition of an App: Is it supposed to run as a process
  (as usual web applications do)?

x What's a macro-framework? (I understand, but I feel like it needs either a
  better name or more explanation. In particular because macros are a rather
  important thing in CL.)

x What is the advantage of the different URL namespaces over Symfony's
  approach?

x Add some more personal motivation.

x "It also allows us to expose any kind of definition, ...". Perhaps add
  "almost"? (I don't know, just being cautious.)