vaelii.impl.cli — com.vaelii/vaelii 0.1.0

A command-line driver for a KB — the shell dual of the in-process API, launched with lein run -m vaelii.impl.cli <cmd> <args…>. It runs the engine in-process (no daemon); to talk to a running daemon use vaelii.impl.client instead.

lein run -m vaelii.impl.cli assert '(dog Fido)' NaturalWorldContext --dir /tmp/kb lein run -m vaelii.impl.cli query '(dog ?x)' NaturalWorldContext --dir /tmp/kb lein run -m vaelii.impl.cli why 3 --dir /tmp/kb lein run -m vaelii.impl.cli export /tmp/dump --dir /tmp/kb lein run -m vaelii.impl.cli repl --starter # interactive, starter schema

Backend. --dir <path> uses the durable :disk backend (recovered on open, so a fact asserted in one invocation is there in the next); with no --dir the KB is in-memory and lives only for the process — useful for repl or a single compound session, pointless across one-shot commands. --starter loads the shipped schema (types, contexts, relation rules) so you can explore the ontology. --strength monotonic marks an assert known-true. export takes --variant records|records+index and --compression gzip|xz|none.

One writer. A --dir KB takes the single-writer file lock (docs/storage.md), so the CLI and a daemon cannot own the same directory at once — by design.

-main clj

(-main & argv)

Parse argv, open the KB, run the command, and print the result. With repl (or no command) it drops into the interactive loop.

commands clj

The command words dispatch knows, for the usage message and unknown command.

dispatch clj

(dispatch kb cmd args opts)

Run one command against kb and return its result (a handle, a seq of sentences / solutions, a proof tree, …). args are data; opts is the parsed option map.

open-kb-from clj

(open-kb-from {:keys [dir starter] :as _opts})

Build the KB a run operates on from the parsed opts: :dir → durable disk (recovered), else in-memory. :starter loads the shipped schema.

parse-opts clj

(parse-opts args)

Split raw args into [positionals opts]. --k v becomes {:k v}, a bare --flag becomes {:flag true}; everything else is a positional, in order.

read-arg clj

(read-arg s)

One argv string as data: the EDN it reads as — a sentence, a context symbol, a handle — and the raw string when it reads as none.

That last case is what a filesystem path is. /var/lib/vaelii is not a symbol (two slashes), so a command taking a path (export, load) would otherwise fail in the reader, before the command it belongs to had been looked at.

read-forms clj

(read-forms s)

Every EDN form in s, in order — how a REPL line's args ((dog ?x) MyContext) are parsed into data.