So in trying to come up with a working set of rules for lispdown, I downloaded some lisp code from an acquaintance's github account, and tried to convert it into lispdown. Here's a sample: This code...
<>
.. becomes this lispdown code...
<>
<
.. becomes this lispdown code...
<
Note that that Lispdown-to-Lisp process is automatable, but the reverse is a non-deterministic process designed for human use. I guess I could come up with some rules(or conventions) for known forms, but that would take away the flexibility that comes from Lisp just being itself :). Even with my brief contact with the language I can see that the lack of syntax actually frees up the ability to visually/spatially arrange code in ways that makes local sense, eg "the conditional here should be aligned under the cond keyword, but in this other place it should actually be offset because of the huge conditional expression"