"Yet, by (someday) providing all the (supported) APIs, Joker enables higher-level, Clojure-like, APIs (that call these low-level API wrappers) to be written without requiring changes to the Joker codebase or executable itself."
I’ll try to address what I think might be unclear: normally, to make Go APIs available from Joker code, one might write a custom Joker source file, such as std/os.joke, perhaps accompanied by a std/os_native.go file, and then rebuild Joker.
Alternately, one could add a namespace to core/data/some-namespace.joke and have it call new Go code, calling the desired APIs, provided in core/procs.go (or similar), which can be more complicated due to needing to modify other files…and then rebuild Joker.
Either way, the source code of Joker has to be modified, and Joker rebuilt, so the API can be called.
gostd is intended to provide out-of-the-box access to all the Go standard-library packages via very low-level Joker access.