⏺ There it is — the full picture, and it's genuinely spicier than the recursion alone:
I'm not `ds4-agent`. I'm `operandi` — a pure Common Lisp agent (SBCL 2.5.6, from Homebrew), running in a Lisp image with ~20 OPERANDI.* packages: OPERANDI.LLM, OPERANDI.ACTOR, OPERANDI.TOOLS, OPERANDI.SUBAGENT, OPERANDI.SESSION, OPERANDI.STORE, OPERANDI.TUI, OPERANDI.HTTP, OPERANDI.MCP, OPERANDI.PAYMENTS, OPERANDI.CRON, OPERANDI.SEARCH, OPERANDI.MAPLE, OPERANDI.PPQ, OPERANDI.ENGINE... It's a whole sovereign agent platform written in Lisp — not a C inference binary.
And the backend is configured to talk to DwarfStar itself:
• *LLM-BACKEND* = LLAMA
• *LLM-URL* = http://localhost:9931/v1/chat/completions — the DwarfStar ds4.c server
• *LLM-MODEL* = deepseek-v4-flash
So the stack is: operandi (a Lisp agent) → DwarfStar's `ds4.c` engine (C) → DeepSeek V4 Flash weights (GGUF) → M4 Pro Metal kernels. Three layers of "AI building the thing that runs AI," and I'm the top layer, reading the bottom layer's source.
The interesting part isn't just "I'm a laptop" — it's that the whole thing is a self-hosted, self-referential stack: a Lisp agent whose brain is served by the very C engine it's inspecting, on the very hardware the project targets. The README's thesis ("AI agents build the engine that runs AI agents") is literally the architecture of this conversation.
Want me to dig into how operandi talks to the server — the LLM-CHAT / POST-CHAT plumbing, or the tool-calling format it uses?
18 iter · 0.000¢, 315875 prompt (293683 cached)/2299 completion tok, 18 calls
