What is being
made now
Small by design. Each project here is active for a reason.
Every tool here is built and tested on local models: Ollama, vLLM. All running on-premise.
Pencil Sync
Tool · design-sync · 2026–
Bidirectional sync between pencil.dev designs and frontend code. Edit a component in the canvas, the code updates. Change the code, the design follows.
Vidistiller
Tool · extraction · 2026–
Self-hosted video intelligence platform. Transcribes, detects slides, summarizes with LLMs, and exports to Obsidian-ready Markdown.
Token Diet
Tool · optimization · 2026–
Unified installer and dashboard for RTK, tilth, Serena, and ICM. Slashes AI session token costs by 40–90% without changing how you work.
Superharness
Protocol · multi-agent · 2026–
Multi-agent task coordination for Claude Code, Codex CLI, Gemini CLI, and OpenCode. A shared contract layer that keeps AI coding assistants from stepping on each other.
Obsidian Semantic MCP
Tool · memory · 2025–
Turns an Obsidian vault into a queryable brain for Claude. Semantic search across every note using local embeddings, no cloud services required.
Tessera MCP
Tool · memory · 2026–
Local MCP server for semantic search over non-markdown Obsidian attachments. Covers PDFs, images, audio, CSV, and code: everything markdown cannot see. Sibling to Obsidian Semantic MCP.
Morpheme
Tool · observability · 2026–
A live, in-browser dashboard for AI agent session state. One dashboard, multiple data sources. Connects to Superharness natively.
Synod
Protocol · multi-agent · 2026–
A coordination protocol for clusters of AI agents that deliberate, decide, and learn together.
What is being
learned
Essays, field notes, failures, and the occasional longer argument.
Written from direct practice. Local models, local memory, local infrastructure. No cloud-first assumptions.
Operator note Artifice Machine
Maxime Roy builds Artifice Machine. The work is published here.
One developer. A suite of AI instruments. Not a product studio.
How the work
is approached
Operating principles
These principles were not designed. They are not rules. They came from the failures.
- Build the harness, not just the model
- Sign the work
- Small enough to understand, useful enough to ship
- Record the failures. They are part of the work.
- Tools should outlast the moment that produced them
- The interface is part of the instrument
- Run local. Models, memory, and tools stay on the machine