hey if you have got the system working try this :

It needs editing to work on a different filesystem, too many hardcoded paths

It has no documentation, or anything ( o plain ASCII diagram or flowchart ) explaining either how it works, or how its unique, or how its different, or how its better

After reviewing the actual code, which is you say not the priniciple itself but only proof of principle , I don't see how its unique or how its different from HTML::Mason or TT2...

• You can define variables in template (both Mason/TT2)
• You can define templates within a template (definitely TT2)
• You can embed perl (both Mason/TT2)
• There is a default template (both Mason/TT2)
• database plugin, among others (both Mason/TT2)
• templates in folder actions are accessible directly via url
• session handling (both Mason/TT2, via plugins)
• ...

Perlmonks is implemented in a similar way; Some modules, some templates on disk, some default templates, some templates stored in database, data in database, url mapping, actions ... custom template format, embedded perl... session handling ...

I know I must be missing the point

update: so i went and checked some more of your nodes and i found in I will be vindicated you clarify your idea is , as chromatic says, basically scheme :)

Its a great idea , perl is built on it,

It would work great as a backend for a GUI Builder or for a a node based visual programming environment like PNI, but not something i'd want to write by hand anymore than XML :) and you can't beat typing for speed :)