Essays, the Eidos specification, and the projects behind them.

On the Name Eidos

Eidos is Plato's word for Form, though the architecture it names owes nearly as much to Aristotle, who used the same word, and its craftsman is the one the Gnostics described.

The Limits of a Gate

An architecture that rests on mechanical enforcement owes an account of where enforcement stops: which rules deserve a gate, who guards the gates, and what a passing gate proves.

Hexy

A hex map maker for tabletop RPGs, with a live player-facing second screen.

Eidos: An Architecture for Cheap Code

For fifty years, software architecture has argued about where the boundaries should go, on the shared premise that the code is written by a person whose attention is the scarce resource. That premise no longer holds.

Portfolio Site

This site: one repository serving the treatise and everything written under /writing.

Eidos Architecture

The canonical specification: Forms and implementations, the three commitments, the vocabulary, and the conformance levels that measure a repository against them.

Adopting Eidos

The playbook for existing projects: assessment, a first gate, forming the load-bearing modules, regenerability drills, and the anti-patterns that undo all four.

Form Template & Gate Registry

The canonical templates for a Form document and the gate registry, plus the parity check that makes the registry impossible to quietly falsify.

Eidos for Infrastructure

Where declarative tooling already separates Form from implementation, drift is the enemy, and six fitness functions buy an E2 estate in a weekend.