Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

The repositories

One repository per module, all under https://github.com/ikigai-rs. This map is derived from the organization’s repository list (gh repo list ikigai-rs) on 2026-09-26, grouped the way the maintainers group them; a few private repositories (the site, the release tooling, a secrets module and a set of Lisp programs) are omitted. If a name here does not resolve on GitHub, the list moved before this page did — the organization is the truth.

The kernel and the host

  • ikigai-core — the kernel workspace: ikigai-core (kernel, Description/ArgSpec, capabilities, golden threads, clocks), ikigai-vocab (the vocabulary and the Turtle renderer). Those two are the whole workspace — every module crate that once lived here has moved to its own repository. Everything else depends on it.
  • ikigai-cli — the main host and a workspace of its own: the ikigai binary, the embedded host, the engine (the REPL grammar), resolve/wire/scheduler, the IPC and QUIC transports, the MCP projection, and the inbound-HTTP transport library.
  • ikigai-module — the loadable-module format: ModuleSpace, the transports, host-callback resolution. Part II.

Compute and data

  • ikigai-fn — the function library this book chains onto, and the smallest complete module crate: read it first if you are writing one.
  • ikigai-fs — the file workspace, urn:file:*, natively and on a browser’s storage.
  • ikigai-http — the outbound HTTP client as resources.
  • ikigai-text — Unix-like text endpoints, urn:text:*, pure pipeline citizens.
  • ikigai-linkeddata — ikigai-rdf (transreption between RDF syntaxes), ikigai-sparql (the graph face), ikigai-sniff.
  • ikigai-store — the persistent RDF store: a dataset opened from a path that survives a restart, owned by one process so that reads can be cached. ikigai-sparql above queries a graph it is handed; this is where the bytes live.
  • ikigai-jsonld — JSON-LD expand/compact/flatten, lazy-loadable as wasm.
  • ikigai-compress — gzip and zlib as resources, urn:compress:* and urn:decompress:*, registered as transreptors too.
  • ikigai-markdown — Markdown as a graph: one structural lift, every dialect a mapping resource.
  • ikigai-ledger — the work ledger: items, comments, labels and links as resources, and next as a resource with a swappable ranking policy.
  • ikigai-xslt and ikigai-xslt-module — XSLT as a resource, linked or loadable.
  • ikigai-shacl — SHACL validation, native and in the browser. Checking a resource mounts it.
  • ikigai-toolbox — the RDF Toolbox (turtle-lsp in the browser) served as resources: a page that checks any resource’s Turtle face, and its shapes, as the viewer. Checking a resource reads through it.
  • ikigai-sexpr — s-expressions to SPARQL and Turtle, no Lisp engine.
  • ikigai-lisp — the Lisp engine (urn:lisp:eval), whose builtins are the five verbs.
  • ikigai-script — scripts as resources in any host: urn:script:{name} with content-addressed versions, run as a read or for its effects, under the least of what it declares, what its publisher held and the host’s ceiling. Scripts are resources mounts it.
  • ikigai-nl — natural language to a DRAFT script, with the model as a drafter and never an actor. A sentence becomes a draft mounts it.

Personal and platform

  • ikigai-personal — calendar and contacts (macOS EventKit).
  • ikigai-org — the org-mode agenda as the same event graph.
  • ikigai-meeting — meeting scheduling over provider backends.
  • ikigai-llm — urn:llm:ask, one facade over pluggable inference backends.

Polyglot faces

  • ikigai-python — a pure-stdlib Python client and servable peer for the wire protocol.
  • ikigai-deno — the same in zero-dependency TypeScript.

Trust and governance

  • ikigai-sign and ikigai-encrypt — signatures as RDF graphs, and their dual.
  • ikigai-throttle — rate limit, retry, circuit breaker, failover and timeout as space overlays; Failover is what a prefer-mount is made of.
  • ikigai-a11y — layered accessibility configuration and the WCAG contrast floor this book’s gate measures with.
  • ikigai-log — the log’s line grammar and its provenance vocabulary.

Developer tooling and faces

  • ikigai-repo — git, gh and cargo as capability-gated resources.
  • ikigai-browse — repository browsing as resources, with text, HTML and Turtle faces.
  • ikigai-gonk — the work-ledger and repository-browser host: the ledger (items, comments, links and a next-item ranking), the browse family over every repository it is given and SPARQL over its store, through a socket, HTTP and QUIC. The gonk Book teaches it.
  • ikigai-dev-server — retired. The standalone IPC server that served the browse family before gonk did, whose Cargo.toml was its manifest; its repository stays readable for that history.
  • ikigai-web — the standalone HTTP and SPARQL face (published as ikigai-web-server).
  • ikigai-runbook — guided, runnable demos as resources.
  • ikigai-conformance — what “done” means for a module, as one test over a kernel: it walks every endpoint and reports every violation of the recipe this book teaches at once.
  • ikigai-name — persistent-identifier resolution, urn:name:*.
  • ikigai-emacs — the editor as a client, its commands generated from the manifold.
  • ikigai-web-demo — the kernel in the browser, a page assembled by resolution.
  • ikigai-tutorial — this book, and the crates it teaches.

The semantic CMS