I'm building an 8-bit computer out of 400+ relays, along with the software to program it: a simulator, an assembler, an IDE and a VS Code language server. The machine is up and running, and it's Turing complete.
Project blog · Build videos · Featured on Hackaday · Board designs
| Project | What it is | Try it |
|---|---|---|
| relay-computer | Interactive front panel and animated schematics, in Angular + SVG | Simulator |
| relay-computer-model | A wire-by-wire simulation of the hardware: cards, backplanes and buses, switching like the real relays | |
| rcasm | Assembler for the relay computer's assembly language | |
| relay-computer-ide | In-browser editor for writing and assembling programs | Editor |
| rcasm-lsp | Language server: diagnostics, hover, completion, go-to-definition and more, in VS Code and in the editor | |
| relay-computer-pi | Code from the YouTube series on calculating π on the relay computer | |
| relay-computer-blog | Source for the build blog (Hugo) | Blog |
knowledge-as-code keeps engineering knowledge in git, where people and AI coding sessions can both find it. Standards, decisions, runbooks and known fixes each become a typed Markdown record, reviewed by pull request like any other change.
kac, a .NET command-line tool, checks every record against the schema its type declares, fails CI on a broken cross-reference, and writes the indexes nobody should keep by hand.- The same records are packaged as a Claude Code plugin, so an agent can look up the standard that applies, and cite the rule it followed, before it writes code.
- People read the corpus as a wiki; agents read the plugin built from the same files, so nothing has to be kept true twice.
Docs · How it compares · NuGet · dotnet tool install --global KnowledgeAsCode.Tool
Both are also experiments in agent-first development: every line is written by Claude via Claude Code, designed through conversation rather than typed by hand.