# Projects

The projects are a workshop, not a single product. They share questions and habits—how to represent structure, how to measure uncertainty, and how to make systems observable—but most are independent repositories with their own runtime and release cycle.

# The public center

attobop.net is the publishing surface: the landing page is an interactive Rust/WebAssembly cellular-automata instrument, while the essays explain algorithms, probability, sensing, and representation. The figures and reproduction bundles make the essays checkable; the site does not need the other projects to run.

The coin-sampling and unseen-species essays are representative of the recurring pattern: start with a precise question, expose the assumptions, then connect the result to executable experiments. The colophon documents the publication machinery.

# Research and mathematical tools

• subsume studies subsumption and ontology reasoning with geometric and embedding-based representations. It is the software counterpart to the region embeddings essay.
• fingerprints explores finite-sample entropy and unseen-species estimation. It connects to the unseen species essay and its Good–Turing/Chao-style questions.
• flowmatch experiments with flow matching on curved spaces such as the torus, sphere, and SO(3). It is a continuation of the representation question: what changes when the space itself has geometry?

These projects supply ideas and experiments for the writing; they are not dependencies of the public site.

# Developer and systems tools

• metallix is a local inference engine for Apple Silicon, built around Rust and Metal.
• vicinity works on approximate nearest-neighbor search.
• anno handles text annotation and entity extraction.
• muxer studies multi-objective bandit routing with drift detection.
• netbraid keeps network observations separate while testing how they relate; it is the network evidence/replay edge of the systems work.
• proofyloops provides CLI and MCP tooling for debuggable Lean 4 proof workflows.
• hypha coordinates local sensor and compute nodes with power-aware scheduling.
• piku is an experimental local coding-agent workspace.

The common thread here is operational rather than architectural: make a hard system inspectable, keep evidence close to the operation, and preserve clear boundaries between components.

# How the pieces fit

questions and observations
          │
          ├── essays and figures ──► attobop.net
          │                              │
          │                              └── reproducible explanations
          │
          ├── geometry, inference, sampling ──► research projects
          │                                      (subsume, fingerprints, flowmatch)
          │
          └── local systems and evidence ─────► developer tools
                                                 (metallix, netbraid, hypha, ...)

The arrows describe shared direction and feedback, not import dependencies. The projects can be built, tested, and used independently.