jolt-lang.net valid

Jolt

Jolt is a Clojure implementation on Scheme. It reads Clojure source, analyzes

For agents: Jolt: a Clojure implementation on Scheme that reads and analyzes Clojure source; the llms.txt summary is truncated, so details are unclear.

clojureschemeprogramming-language

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T05:52:26.064Z. Cached copy · Source on jolt-lang.net

# Jolt

> Jolt is a Clojure implementation on Scheme. It 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,
> written in Clojure and compiling itself, and ships a Clojure-compatible
> standard library. Programs compile to single self-contained native binaries
> with no JVM and no runtime install.

Important: there is no JVM underneath Jolt, so JVM reasoning does not carry
over. Most portable Clojure runs unchanged (persistent collections, the numeric
tower (including `BigDecimal`), lazy seqs, transducers, protocols/records,
multimethods, metadata, atoms, refs/STM, `future`/`promise`/`agent`/`pmap`,
`core.async`, runtime `eval`, and the full reader). What differs: there is no Java
interop (no reflection, no `gen-class`/`proxy`; `Class.`/`Class/static`/`.method`
resolve only against a shimmed subset of `java.*` written in Scheme, and a class
token is a name, not a loaded class); those shims implement their JVM
counterparts' API but not the JVM's runtime, so classloaders, JVM GC behaviour,
and JVM thread-lifetime rules do not apply; strings are codepoint-indexed rather
than UTF-16, so `(count "😀")` is 1; regexes compile through irregex, not
`java.util.regex`; and `clojure.core` coverage is broad but not total. C
libraries are reached through the `jolt.ffi` foreign-function interface.
Read the Differences page before assuming a JVM behaviour holds.

## Start here

- [Getting Started](https://jolt-lang.github.io/docs/getting-started.html): install, evaluate, run a project, dependency requirements per platform.
- [Differences from Clojure](https://jolt-lang.github.io/docs/differences.html): the divergences from JVM Clojure. Read this first when porting code.
- [Rationale](https://jolt-lang.github.io/docs/rationale.html): why a Clojure on Scheme, and what it is for.
- [Source repository](https://github.com/jolt-lang/jolt): the compiler, runtime, and standard library.

## Guides

- [Building & Running](https://jolt-lang.github.io/docs/building-and-deps.html): `deps.edn` projects, AOT compilation to a native binary, typed arithmetic and inference.
- [REPL-Driven Development](https://jolt-lang.github.io/docs/repl-driven-development.html): the nREPL server and editor setup (CIDER, Calva, Cursive).
- [Writing Libraries](https://jolt-lang.github.io/docs/writing-libraries.html): publishing a jolt library, the `.jolt`/`.cljc` extension rules.
- [Testing](https://jolt-lang.github.io/docs/testing.html): `clojure.test` on jolt and how the conformance corpus works.
- [Host Interop](https://jolt-lang.github.io/docs/host-interop.html): which `java.*` classes are shimmed, and how to register your own host classes.
- [Native Interop (FFI)](https://jolt-lang.github.io/docs/native-interop.html): binding C shared libraries with `jolt.ffi`, and exporting jolt code behind a C ABI.
- [Cljc Interop](https://jolt-lang.github.io/docs/cljc-in
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=jolt-lang.net · GET /v1/domain/jolt-lang.net · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for jolt-lang.net:
1. POST https://agentwebmap.com/v1/sites/jolt-lang.net/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://jolt-lang.net/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/jolt-lang.net/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/jolt-lang.net).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.