My code is not yet CPAN ready, (nor production ready really) however I do have a forum system running on it which seems fast enough on a small $20 a month server. I would probably have real problems if a few hundred users tried to browse it at the same time on the current implementation lol.

As for code correctness, there is a very simple set of rules for tags and the rest is left upto the developer. There will be a very small number of built in tag names to access some standard primitives but after that the code would be application specific.

For instance 

<use><qd>action</></>   

would use 2 built in primitives (use&qd) to process the action named i
+n the query

where

<shop::cart::contents></>
[download]

would use &contents from a shop::cart package which deals with the DBI or your choice of ORM etc. The versions out there already don't support this but I have made a lot of progress since then in many directions and I'm hoping to start pulling it all together into a coherant form quite soon... it just depends how long this compiler takes to get going.

If you really apply Separation of concerns there should be at some point in the development, a moment in which you can extract some stable part of your code and begin to build the rest upon it. But my competence limit is reached. Best wishes anyway!