As I said, the newly discovered difficult formal work of putting this article together compared to my previous usual informal use of markdown strongly implies to me that this article is more accessible... in some way. That work must be ending up somewhere.

Hopefully this smallweb article has something in it of value to Aral, hints to drop to me about useage or otherwise. I feel a bit coy about having radically avoided javascript components / javascript / html in favour of xml-looking kitten markdown fragments and the json data fragment, which is not coding in javascript per se either. I think the fact that kitten is *not like* javascript and html but is a basically xml construction that already maps onto them is very powerful.

I was going to talk about Sandewall's Madman here, which I guess will be the view from my common lisp Leonardo System Knowledge Representation Framework of these kitten constructions, but this is a fairly minor detail from the kitten's perspective: Kitten being a robust xml thing, it is easy to map some similarly formal s-expressions previously aimed at html onto.

In terms of useage of data, I would hope that I can open my markdown fragments, maybe entire kitten into a modern successor to Kent Pitman's Cross Referenced Editing Facility (you watch the show, right) where trajectories through dense and rambling free-ranging technical explanations were discovered for answering questions / generating code in that experts space from their dialogue. This being interesting in the modern situation because the trajectories through expert dialog are explainable in the way that deep learning's numeric weights by definition can never be.

Alright, it is bed time for me. Good night! I hope you discovered [kitten](https://kitten.small-web.org).