Each project below is a real, running build. Where there's public code, documentation, or a live instance, it's linked. Where something is early-stage, that's named too — not hidden behind polish.
NESI takes the raw material of an ordinary day and turns it into something that can be recognized, kept, and eventually shared. Kevin decides what crosses; nothing else does.
It runs on one governing rule: a recognition mechanic never does the recognizing. No worth-score, value-rating, or skill-rank is ever emitted — the system's only job is to surface and hold tension, never to judge it. That's not a design note. It's cited live inside the running code as NESI's single operative law.
A working practice for turning ordinary days into something that holds — built first for Kevin's own use, and applicable anywhere a number would distort the thing it's measuring: education, care work, community platforms.
A running 2D build, with its own instrument suite — conservation checks, threshold sweeps, and a cold-walk verification run by someone who didn't build it. Twelve automated instruments, plus stranger-tested sessions. Not a design doc.
A working manuscript — Architecture of Coherence — and the pattern library behind it, reduced from 176 archival design patterns to the subset with confirmed live use: patterns cited by name inside running code, a governing document, or an active build. Not just an old log entry.
A citable, load-bearing account of the design principles underneath the rest of this work — useful to anyone building systems where a stated principle needs to actually hold under running code, not just read well.
A full manuscript and a 23-pattern cross-section, each entry sourced to the exact file and line that cites it live. Not a claim — a citation.
This is a working paper, not a finished doctrine. If you want to talk through where it applies to your own system, book a call.
A Field Kit takes an unresolved structural mess — a housing dispute, a surveillance proposal, a datacenter siting fight, a defective-product matter, a school-closure decision — and produces a crystallized set of apparatus a practitioner-ally can use the same day: a structural audit, a one-pager, a recognition diagram, sample letters, and templates, bundled into a single distributable document.
Tenant unions, opposition groups, oversight bodies, and consumer-side authors who need apparatus, not just analysis.
A structural audit, a distributable one-pager, a recognition diagram, and ready-to-send templates — built to hand to someone the same day.
Nothing goes out without a deliberate go-ahead. See Library for what's currently available to read or request.
A separate, ongoing project exploring what a public gift economy looks like when it's run as a structural ledger instead of a marketing page — nodes naming real capacity and real need, with debt left structurally unrepresentable.
It runs in a different register from this page on purpose: this page is the funder-facing front door; the ledger is the gift circle itself, running behind it.
Every project above started as a smaller, uglier working version. If you have a system that needs the same discipline applied to it —