From the first paragraph of the README
A Clojure implementation on Scheme. Jolt reads Clojure source, analyzes it to a host-neutral IR, emits Scheme, and runs it — on Chez by default, or on Gambit compiled to JavaScript for the browser. The compiler is self-hosted: it is written in Clojure (jolt-core/) and compiles itself. It ships a Clojure-compatible standard library.
Compare it to the intro for Ironpython 3 [0]
IronPython is an open-source implementation of the Python programming language that is tightly integrated with .NET. IronPython can use .NET and Python libraries, and other .NET languages can use Python code just as easily.
IronPython 3 targets Python 3, including the re-organized standard library, Unicode strings, and all of the other new features.
While I'm not a technical writer (and not even a native English speaker), if I had a go following that example (not sure if I grasped your original intent).
Jolt is a Clojure implementation on top of scheme and primarily supports Chez. It can also be run with Gambit to run inside a browser environment. It aims to be fully compatible with Clojure and its standard library and the core compiler is also written in standard Clojure.
Then the whole "This is not the JVM" is just noise. Just replacing it with
While we do not interop with the JVM, we provide shims for some basic features to interact with existing Clojure libraries.
Also some sentences like
Differences from Clojure — what actually diverges
Scripts — a file, a shebang line, *command-line-args*
A file runs too — jolt script.clj, or an executable #!/usr/bin/env jolt script: see Scripts.
The java.* shims are not the JVM. A shimmed class implements its JVM counterpart's API on Scheme, so it can look convincing while the surrounding runtime is not the JVM.
No JVM, no Java interop. No reflection, no gen-class/proxy. Interop syntax (Class., Class/static, .method) resolves only against a shimmed subset of the java.* standard library;
.jolt extension. A namespace's source can be foo.jolt as well as foo.clj or foo.cljc, and the three are the same language: the reader, analyzer, and emitter never look at the extension. .jolt is a marker for readers and tooling, saying the file uses jolt-specific interop and is not portable Clojure.
jolt completions tasks is worth knowing on its own: one line per listable task, name<TAB>doc, which is the machine-readable form of what jolt tasks prints for a person.
That is not how you write for a person, IMO. You can look at the ironpython repo to see how you structure things for human consumption.
[3] https://github.com/IronLanguages/ironpython3
ADDENDUM
Your comments here are way more readable than what's in the README and the web site. From the latter, I'm strongly skeptical of the quality of the code as what matter there are clarity, simplicity, and directness. If the docs are noisy (verbiage instead of clear explanations), I shudder to think what the code looks like.