Systems
Six systems, the libraries underneath them, and what’s on the drawing board: seventeen public repositories and one private tool with a public track record. Order within a group is each page’s own weight — reorderable at zero design cost.
SYSTEMS 7 · LIBRARIES 6 · WEB 2 · IN DESIGN 3
Systems
The flagship layer — an OS, an agent runtime, a standards engine, a media platform, an RF toolkit, a GPU inference stack, a mesh client.
-
A bare-metal Rust phone OS for the AGM M7 — no Linux underneath. The kernel boots end-to-end under QEMU, and CI proves it on every push.
-
Self-hosted AI agents with persistent memory. One binary, no containers, no external databases — a knowledge graph that carries forward across sessions.
-
The standards engine that gates every other repo on this site: a lint/gate CLI, code intelligence, and PR/issue orchestration, private by choice.
-
A unified self-hosted media platform: one Rust server across 21 crates, replacing a stack of separate *arr-pattern services with one coherent media lifecycle manager.
-
An RF signals toolkit in Rust: a clean-room Meshtastic mesh stack running live, CHIRP radio workflows, an encrypted credential vault, and a 17-domain signal model labeled by what actually ships.
-
A GPU inference stack for transformer embedding models, built from the device upward in Rust and HIP for AMD hardware. CPU correctness proven; GPU cutover waits on hardware access.
-
A clean-room Rust implementation of a Tailscale-compatible mesh networking stack. Pre-alpha, actively implementing the peer client against a real reference control plane.
Libraries
Shared substrate the systems above are built on: search primitives, sealing, subprocess handling, common scaffolding.
-
theatron
θέατρον — the seeing-place
Desktop UI primitives for the fleet: Dioxus/Blitz components, design tokens, markdown rendering, HTTP/SSE, OS integration.
-
heurema
εὕρημα — a thing found
Contracts for vector search, full-text search, persistence, and rank fusion. Reciprocal-rank fusion is implemented; HNSW and BM25 land by extraction from their in-app implementations.
-
sphragis
σφραγίς — a seal
Post-quantum hybrid sealing: an X-Wing KEM (X25519 + ML-KEM-768) with a ChaCha20-Poly1305 envelope, behind an explicit feature flag.
-
koinon
κοινόν — that which is shared
Fleet-common Rust scaffolding: tracing init, typed errors, config loading, a CLI prelude.
-
epitelesis
ἐπιτέλεσις — executing-to-completion
A typed subprocess wrapper over std and tokio: timeouts as contract, captured output, structured errors. Every fleet subprocess call goes through it.
-
zetesis
ζήτησις — systematic inquiry
Budget, cost, citation, and query contracts for agent research pipelines, with a fixture-driven deep-research loop.
Web
Web-facing infrastructure: this site's own theme, and a self-hosted newsletter service.
-
typikon
τυπικόν — the book of order
The Zola theme, frontmatter schemas, and CI gate bundle this site itself runs on: CSP enforcement, link checking, accessibility, smoke tests.
-
epistole
ἐπιστολή — a letter
Subscriber lifecycle and archive flows over an embedded store; SMTP delivery is the next phase.
In design
Specification before code — locked design decisions, no shipped implementation yet.
-
πίναξ — the tablet, the register
A relational storage engine designed from scratch in Rust: multi-writer MVCC, per-page encryption, a causal changelog as a storage primitive. Design documents only; implementation not started.
-
μνήμη — memory as faculty
A Datalog engine for facts, rules, and inference: content-addressed facts, supersede-based retraction, incrementally maintained views. Design documents only; implementation not started.
-
δίοπτρον — the instrument through which one sees
A specification for a web runtime where operator and agents share one capability surface: browsing, ingesting, querying, acting. Design documents only; implementation not started.
FLEET CI WORKFLOWS: FORKWRIGHT/.GITHUB →
Systems built in employment are employer property, described under professional experience →