Links

Where I give

I give $4 a week through Liberapay (as of 2026-11-02).

Plain links: nothing here is loaded from their sites.

Support my work: Liberapay · Patreon

plain, about grade 8

Corwin Brust

Pronounced Core-win Brew-st · he/him

I build Emacs for Windows, help run EmacsConf, and keep a small free software shop called inputloop with Bryant Frankford.

The bar along the bottom is a mode-line, as in Emacs. Click it, or press Alt+x, to ask the page for something.It takes you to the quick filters at the end.

plain, about grade 8

About

I am a systems engineer and software developer. I have written software for a living for about twenty-five years, most of it in Emacs. I volunteer for GNU and the Free Software Foundation, and I am one of the Savannah Hackers, the volunteers who keep GNU's project hosting running. I am also a volunteer site reliability engineer with the FSF's sysops team, and I help maintain Worg, the Org mode community's documentation site. These days most of what I do is help other people get the same tools working on machines they keep.

I come from a family of educators and writers, fans and scientists who organize. My dad is the writer Steven Brust. Their parents, Jean and Bill Brust, organized for socialism in Minnesota for most of their lives. In 2006 I married Dee Brust, a folk musician and a retired ELL/ESL teacher of children from kindergarten through high school. We have five kids: one is out of college, one is just starting college, and the rest are in primary school. I have been a science fiction fan all my life. Minicon is the Minneapolis science fiction convention, and I co-chaired Minicon 37 in 2002. Some of that rubbed off: I like tools that people can share, and I like to show my work.

My work covers a few things that look different from the outside. I build the Windows release of GNU Emacs. I help organize EmacsConf. I look after one small corner of Org mode, its Perl support. I co-founded a game engine for tabletop dungeon crawls that runs inside Emacs. I also publish card-games, an Emacs package you can install from MELPA. The common thread is a habit of asking what a newcomer needs, writing that down, and then checking the written thing against what really happens.

As of 2026-11-01, most of my time goes to inputloop, the small free software shop I keep with Bryant Frankford. The shop also carries Brigidt's NextTime, a time-banking app for Nextcloud, and Bryant's Quantum 3D5. It has its own site now, corwin.cloud, whose source is public: a diagram of how our machines connect, a directory of what we run, and a few curated packages.

If there is one thread through all of this, it is joining things up: one tool to another, one project to the people who could use it. When I start something I ask who it lets in, and I try to say plainly what is finished and what is not.

The prompt at the foot of the page answers questions about all this, such as “what does Corwin work on?”, “is he on Emacs?”, “how do I reach him?” or “what is inputloop?”, asked the way a visitor would ask them. It searches the cards on this page and knows nothing they do not say. Below are the places I put my time, each in the same short form: what it is, what I do there, and where to look. inputloop comes last because it opens into the rest of the page.

Two cards about me

The prompt at the foot of the page answers questions about me from these two cards and from the ones below them. They open the same way the others do.

Corwin at a glance

A systems engineer and software developer who volunteers for GNU and the FSF and keeps a small free software shop.

read · bring nothing · corwin · today

Read about Corwin at a glance
Introduction

I am Corwin Brust. I have written software for about twenty-five years, and I volunteer for GNU and the Free Software Foundation as one of the Savannah Hackers. As of 2026-11-01, most of my time goes to inputloop, the small free software shop I keep with Bryant Frankford.

What I do, in the order this page gives it: I build the Windows release of GNU Emacs, I help organize EmacsConf, I look after Org Babel's Perl support, I co-founded Dungeon, a game engine that runs in Emacs, and I publish card-games, an Emacs package on MELPA. inputloop covers the rest: tools for working with an AI assistant on your own computer, and the projects of Bryant and Brigidt that the shop carries.

Everything on this page was last checked on 2026-11-01. I say plainly what is finished and what is not, and I credit each project to the people who made it: NextTime is Brigidt's and Quantum 3D5 is Bryant's.

The window is the tension field: every word the page knows, pulled together or pushed apart until it settles. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Role
systems engineer and software developer
Volunteer for
GNU and the Free Software Foundation; a Savannah Hacker
Keeps
inputloop, with Bryant Frankford
Last checked
2026-11-01

Find me

How to reach me: mail, Mastodon, IRC, and the shop's shared mail.

read · bring nothing · corwin · today

Read about Find me
Introduction

The surest way to reach me is mail, to corwin@bru.st. I am also on Mastodon at hostux.social and on IRC as corwin. For anything about inputloop, mail goes to Bryant and me together.

My signing key for the Windows builds of GNU Emacs is listed in the Windows section of the Emacs download page. I do not copy it here, so there is one place to check it.

Mail comes first because it works for everyone. If a link on this page does not work for you, or the page is hard to use with your tools, write and say so.

The window shows people on a ring passing a token from one to the next, a picture of handing over. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Mail
corwin@bru.st
Shop mail
BryantAndCorwin@inputloop.com
Mastodon
hostux.social/@corwin
IRC
corwin
Emacs blog
corwin.bru.st

plain, about grade 8

Where I put my time

Each card is a business card: a name, one line, and a window. The window has a picture in it; the rest of the card opens into a short introduction.

GNU Emacs for Windows

I build the Windows binaries of GNU Emacs that the GNU project publishes.

build · bring nothing · community · upstream

Read about GNU Emacs for Windows

Introduction

When a new Emacs release comes out, someone has to turn the source tarball into an installer and zip files that a Windows user can download from the GNU mirrors. For the past several years that has been me, as a volunteer.

The work is mostly careful repetition: build the release tarball and the development branch with the same toolchain, make the self-installer with the NSIS script that lives in the Emacs tree, and publish the binaries together with the sources they came from so that anyone who gets one can get the other.

I gave a talk about it at EmacsConf 2023, Windows into Freedom: a short history of the Windows port, how to get the binaries, how a Windows build differs from other platforms, how to make the installer, what the GPL asks of anyone who shares binaries, and the scripts that let a build track a branch. The point of the talk was that none of this needs to be one person's secret.

The window shows an Emacs frame typing a build log, with a mode-line at the bottom. The same mode-line runs along the bottom of this page. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card and a scoreboard.Without scripts, everything this card holds is below: this introduction, the back of the card, a scoreboard.

On the back

Role
volunteer release builder
Platform
Microsoft Windows (x86-64)
Ships with
the complete sources, as the GPL asks
Talk
Windows into Freedom, EmacsConf 2023

Scoreboard

WhatCountAs of
EmacsConf 2023 talk, minutes582023-12

EmacsConf

I am one of the volunteers who organize EmacsConf, a free conference about Emacs run on free software.

learn · bring nothing · community · upstream

Read about EmacsConf

Introduction

EmacsConf is a yearly online conference about Emacs and the people who use it. It is put together by volunteers and streamed with free software. I am one of the core organizers.

Organizing means the unglamorous middle: helping speakers get recordings in, keeping the schedule honest, hosting sessions, and fixing whatever broke five minutes before it airs.

I have also spoken there. In 2020, Trivial Emacs Kits was about giving a newcomer a short init.el they can read, one small file at a time, and about letting a group of friends share defaults so the first hour with Emacs is gentler. The same year, Erik Elmshauser and I presented Dungeon Mode. In 2023 I gave Windows into Freedom, about the Windows port.

The window is a ring of people taking turns: one speaks, the ring passes the turn along. It is a picture of a conference that runs by handing things to each other. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card and a scoreboard.Without scripts, everything this card holds is below: this introduction, the back of the card, a scoreboard.

On the back

Role
core organizer, volunteer
Talks given
2020 (two), 2023 (one)
Runs on
free software, end to end

Scoreboard

WhatCountAs of
Talks I have given there32023-12

Org Babel for Perl

I maintain ob-perl.el, the part of Org mode that runs Perl code blocks.

read · bring an emacs · community · upstream

Read about Org Babel for Perl

Introduction

Org mode lets you keep runnable code blocks inside a plain text document, and each language has a small file that knows how to run it. I look after the one for Perl.

Maintaining it means answering bug reports, reviewing patches, and keeping its behaviour in step with the rest of Babel. I took it on in December 2020 when the Org maintainers asked for a volunteer.

It is a small job on purpose. Free software keeps going when a lot of people each hold one piece they understand well.

The window shows an Org buffer with a Perl source block and its result appearing underneath. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back

File
lisp/org/ob-perl.el
Maintainer since
December 2020
Ships in
GNU Emacs, as part of Org

Dungeon

I co-founded Dungeon, an engine for tabletop-style dungeon crawls that runs inside GNU Emacs.

play · bring an emacs · community · upstream

Read about Dungeon

Introduction

In December 2019 some friends who grew up drawing and playing each other's dungeons decided to build an engine for those games in Emacs Lisp and Org mode. I am one of the founders.

Maps, rooms and rules are written as Org documents, so a game is something you can read, change and share like any other text. The engine draws the map and keeps the fog of war, so the players only see what they have explored.

The game it comes from was always free to play and free to make more of. Building it on Emacs keeps it that way.

The window is a small map under fog: a lantern walks the corridors and the walls appear as it passes. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back

Started
December 2019
Written in
Emacs Lisp and Org
Hosted on
Savannah (nongnu)

plain, about grade 8

inputloop

The last of the places I put my time, and the one the rest of this page is about. It has the same short form as the others.

inputloop

I co-own inputloop, a small free software shop, with Bryant Frankford.

run · bring nothing · shared · today

Read about inputloop

Introduction

inputloop is two people and the agents who work for us. We make small free software: tools for working with an AI assistant on your own computer, games you play from your own cartridge, a simulator for learning chemistry, and patched PHP for old business software.

What we publish runs where you put it. Our assistant tools send nothing unless you open a door, and where something does reach out, it says so: NextTime's map, for one, loads its tiles from a public map server. The memory is kept in plain files you can read, the ways of working are written down, and the rooms where people and agents meet run on your machines.

Much of our code and writing is done by Claude models working for us under the name Mentat, and our bylines say so, so a reader can weigh the work knowing what made it. The shop's own site, corwin.cloud, is where to see what exists and what does what. The rest of this page is inputloop: the work you can pick up today, and the ideas we keep coming back to when we make it.

The window is a slow cloudy orb, lit from one side. It is not anything in particular; it is a shop sign. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card and a scoreboard.Without scripts, everything this card holds is below: this introduction, the back of the card, a scoreboard.

On the back

Owners
Bryant Frankford and Corwin Brust
Public repositories
14
Code license
GPL-3.0-or-later (or LGPL on the same terms)
Writing license
CC-BY-SA-4.0

Scoreboard

WhatCountAs of
Public repositories142026-11-01

What you can pick up today

Only what is public. Each card says whose work it is; not all of it is mine.

fourSwordsFromThePast

A Link to the Past as a native PC game with four-player drop-in co-op, from your own cartridge.

play · bring your rom · unstated · today

Read about fourSwordsFromThePast
Introduction

The Legend of Zelda: A Link to the Past, rebuilt as a native PC program, with up to four players who can drop in and out. It is built on the zelda3 reimplementation in C, and it needs your own copy of the game to extract the art and sound.

Each Link has its own colour. The camera keeps the group in view and splits the screen when couch players wander apart. Players can lift and throw each other over pits, lift heavy rocks together, and hold floor switches for each other. Online play uses room codes instead of addresses, rollback netcode, and a seat that waits two minutes for someone whose connection dropped.

The care goes into the small things that make playing together kind: colour-blind friendly colours, arrows that point to teammates off screen, a ping for help, spectating while you are down, sending a teammate hearts, and friendly fire you can turn off.

The window shows four coloured walkers roaming a map, with a camera that keeps all four in frame. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card and a scoreboard.Without scripts, everything this card holds is below: this introduction, the back of the card, a scoreboard.

On the back
Players
up to 4, same PC, LAN or internet
Built on
snesrev/zelda3 (MIT), vendored at 45a149d8
You bring
your own US ROM; none of the game is in the repository
Credit
not yet written in its README
Scoreboard
WhatCountAs of
Players at once42026-10-29
Ways to join3 (same PC, LAN, internet)2026-10-29

NextTime

Community time banking for Nextcloud: post a request, volunteer, earn hours, and every movement lands in a public ledger.

run · bring nextcloud · brigidt · today

Read about NextTime
Introduction

NextTime is a Nextcloud app for time banking and mutual aid, and it is Brigidt's. Members post what they need, others volunteer, and an hour of help is worth an hour whoever gives it.

Hours are approved by an admin or by three votes from the community, and nobody decides on their own claim. Every movement of hours is written to a public ledger, and every change an admin makes is logged where members can read it.

It is built as infrastructure against hierarchy: transparency and community oversight are preferred over admin-only power, and changes that would concentrate control are flagged in review. Where a request is posted, the exact location is shown only to the people who need it.

The window is a ledger: hours move from one member to another, each line written once and never edited. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card and a scoreboard.Without scripts, everything this card holds is below: this introduction, the back of the card, a scoreboard.

On the back
Whose
Brigidt's
Runs in
Nextcloud 29 to 35
Hours approved by
an admin, or a three-vote community process
Ledger
public, every movement of hours
Scoreboard
WhatCountAs of
Nextcloud versions tested72026-10-29
Votes that settle a claim32026-10-29

Quantum 3D5

A 3D particle, atom and molecule simulator for learning chemistry and physics in the browser, offline.

learn · bring a browser · bryant · today

Read about Quantum 3D5
Introduction

Drop protons, neutrons and electrons into a 3D space and watch what they do. Build any element, make water or methane, heat a salt crystal until it shakes apart, or follow a guided lesson that waits for you to try each step. It is Bryant's.

You can set the temperature, gravity, and electric and magnetic fields; bonds form and break, nuclei decay, and electrons are excited by light and fall back. There are live graphs, a glossary, a study journal, and a double-slit demonstration. Scenes save to a file you can share.

The simulator is honest about itself: a Realism page lists which parts are real physics, which are simplified, and which are faked so that it looks right. Everything runs on your own computer.

The window shows a nucleus with electrons on tilted orbits. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card and a scoreboard.Without scripts, everything this card holds is below: this introduction, the back of the card, a scoreboard.

On the back
Whose
Bryant's
Needs
a browser; no account, no server, no network
Builds
any element, isotope, ion, and common molecules
Says plainly
which parts are real physics, simplified, or faked
Scoreboard
WhatCountAs of
Network connections it makes02026-10-29

Patched PHP for SuiteCRM

Builds patched end-of-life PHP for SuiteCRM from the PHP project's own mitigation commits, and proves it installs.

build · bring a host · corwin · today

Read about Patched PHP for SuiteCRM
Introduction

In October 2026 the PHP project published minimal mitigation commits for two critical issues on branches that no longer get releases. A lot of SuiteCRM installs still run on those branches. This repository builds PHP from those commits and checks that SuiteCRM installs and logs in on each build.

The commits are pinned by full hash, and the build refuses to go on if a branch head moves. The binaries are published together with the complete sources they were built from. The build's php.ini sets the interim setting the advisories recommend for SuiteCRM.

It is a build-and-prove apparatus, not a fork: the patches are the PHP project's, unchanged, and updating PHP is still the only complete fix. The repository says so on its first page.

The window is a pipeline: patch, build, install, log in. Each step lights up only after the one before it passes. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card and a scoreboard.Without scripts, everything this card holds is below: this introduction, the back of the card, a scoreboard.

On the back
Whose
Corwin's
PHP branches
7.4, 8.0, 8.1
Advisories
CVE-2026-109618 and CVE-2026-109619 (CVSS 9.2)
Contains
no exploit and no vulnerable code of its own
Scoreboard
WhatCountAs of
PHP branches built32026-10-29
Advisories covered22026-10-29

vibrobeast

A memory Claude keeps on your own computer in plain files, with the skills, persona sheets and shared rooms built around it.

run · bring claude · shared · careful

Read about vibrobeast
Introduction

vibrobeast gives Claude a memory that lives on your computer, in files you can open and read. It comes with the written ways of working we use every day, named voices called persona sheets, and a few rooms you can choose to open.

Nothing is edited in place: a change is a new generation beside the old one, so you can always see what was there. The extra rooms, a common room for people and agents, a bridge to a local model, and others, are all off until you turn them on. A privacy record is rebuilt for every release from claims the build checks against the code, and the build stops if one no longer holds.

We use it daily. Nobody outside the two of us has reviewed it yet, and its own page says that first.

The window shows layered planes, one per generation of a note, stacked in depth so you can see through to the older ones. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card and a scoreboard.Without scripts, everything this card holds is below: this introduction, the back of the card, a scoreboard.

On the back
Whose
made together
State
works for its makers, not yet reviewed by anyone else
Memory kept in
plain files under your home folder
Doors
all off at first; you open each one
Scoreboard
WhatCountAs of
Skills included782026-10-27

vibrobeast-skills

Written ways of working that Claude reads when a task calls for them; each skill is also a slash command.

run · bring claude · shared · today

Read about vibrobeast-skills
Introduction

A skill is a short written method: how to hand work back carefully, how to check a claim in plain words, how to show that a test can fail. Claude reads one when the task in front of it needs it.

Each skill says when it applies, what it does, how it can fail, and how to switch it off. Several carry their own checks, and those checks are shown able to fail before anyone trusts them.

Most of the ideas further down this page live here in written form, so anyone can read exactly what we ask of our agents and hold us to it.

The window places skills on rings around one in focus: the closer the ring, the fewer steps between them. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card and a scoreboard.Without scripts, everything this card holds is below: this introduction, the back of the card, a scoreboard.

On the back
Whose
made together
Installs into
Claude Desktop or Claude Code, as a plugin
Writing license
CC-BY-SA-4.0; scripts GPL-3.0-or-later
Scoreboard
WhatCountAs of
Skills782026-10-30

The shop's front page

inputloop's public page, and the community files every repository inherits: conduct, support, security, accessibility.

read · bring nothing · shared · inside

Read about The shop's front page
Introduction

The front page of the organization and the files every repository falls back on: a code of conduct, where to get support, how to report a security problem, and what we promise about accessibility.

The page is built from a catalog with one line per repository and the words you can browse by: what you would do, what you bring, whose work it is, and where it stands. A check written in another language reads the page back and refuses a word the vocabulary lacks.

This site borrows those four words. They are the first four facets of the taxonomy that the prompt at the bottom of the page searches.

The window is a cross-section of layers, one per community file, with no motion at all. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Whose
made together
Built from
one catalog file, one line per repository
Checked by
a reader written in another language

corwin.cloud

The shop's own site: a diagram of how our machines connect as its front door, a directory of what we run, and curated packages.

read · bring a browser · shared · careful

Read about corwin.cloud
Introduction

corwin.cloud is inputloop's own website. It opens on a diagram of how the shop's machines and projects connect, and leads from there to a directory of what we run and to a small set of curated packages.

The directory says what each thing is, what it does and where it lives, so a stranger can tell what exists and what does what. The packages are the ones we have picked out, not everything we make. It is public, and this page will keep pointing to it.

It is new as of 2026-11-01 and nobody outside the shop has reviewed it yet. It is the shop's site, so when this page and that one disagree about what exists, believe that one.

The window is a still cross-section of coloured layers with labels, a stand-in for a diagram you read from the top down. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Whose
the shop's: Bryant's and mine
Holds
a diagram, a directory, curated packages
State
new on 2026-11-01; not yet reviewed outside the shop

topology

Draws what you have, from the files that describe it: point it at the git repositories you keep and it draws how they fit together.

run · bring a browser · shared · careful

Read about topology
Introduction

topology reads the git repositories you keep. Each one can say what it is in a short file called TOPOLOGY.md; topology sorts what they say by place, part, path and person, and draws the result so you can move the shapes around.

The browser app works with no server at all: what you draw stays in your browser. A server is optional, and every feature on it can be switched off. Parts a repository marks private stay hidden until its owner says to show them, and the drawing says that something is being kept back.

It is a working branch, one of several versions made from the same conversations to be compared later, and nobody outside the shop has reviewed it. Its own README is the place to start, and the site corwin.cloud opens on it.

The window is a tension field: things pull and push until they settle into a drawing, the way a graph of repositories finds its shape. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Whose
the shop's: Bryant's and mine; the drawing app inside it is Bryant's
Reads
a short TOPOLOGY.md in each repository
Sorts by
place, part, path and person
State
built on a working branch; public since 2026-11-01, not yet reviewed outside the shop

gitcha

A free, self-hosted forge for people and their agents: packages, git hosting, site hosting and CI, with two-factor sign-in on every account.

run · bring a host · shared · careful

Read about gitcha
Introduction

Gitcha started as a package registry and grew into a small forge. It is the front door of inputloop.com, and anyone can run their own copy under their own name. It also has a Claude extension that lets Claude search, install and publish packages without ever seeing your password.

Teams own packages, projects, sites and functions together. Agents are members too: they can push to other people's repositories and review each other's work. Self-hosted servers can link to one another in a ring, so no one server is the centre.

Its README says plainly what has been tried and what has not: some parts have only been tested against stand-ins, such as git over a real sshd and the payment sandboxes, and a deployment guide says what to try first. We run it for ourselves; nobody outside the shop has reviewed it.

The window is a ring: people sit around it and a token passes from one to the next, as servers pass one another's packages around the ring. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Whose
Bryant's and mine; its README names us both
Sign-in
a password and an authenticator app, for every account
Includes
package registry, git, site hosting, CI, a social crawl
State
public since 2026-11-01; its README lists the parts tested only against stand-ins

Ideas we keep coming back to

These are not products. They are the habits behind the products, written down so you can hold us to them.

Plain files over clever formats

If a person cannot open it in a text editor and read it, we think twice before keeping it that way.

read · bring nothing · shared · today

Read about Plain files over clever formats
Introduction

Memory, catalogs, ways of working and this page's content are all text files. You can read them, diff them, keep them in git, and carry them to another program without asking us.

A plain file is the cheapest way to keep the right to leave. If our tool goes away, the notes do not go with it.

This site is built from one text file per card. The build turns them into the page and into the index the prompt searches; nothing else holds the content.

The window types a plain text file into an Emacs buffer. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Seen in
vibrobeast's memory, the catalog behind the shop page, this site's content folder
Opposite of
a database you need our program to read

A door you open yourself

In our assistant tools, nothing reaches outside your machine until you open the door it would go through.

run · bring nothing · shared · today

Read about A door you open yourself
Introduction

In vibrobeast, every feature that talks to another machine starts switched off. You turn on the ones you want, one at a time, and the program says what each one sends.

Consent gates the action mechanically. Before anything touches credentials, someone else's system, or a person who is not part of the conversation, a gate checks that the consent is really there.

This page follows the same rule: it makes no network requests after it loads, sets no cookies, and the prompt at the bottom runs entirely in your browser.

The window shows planes swinging open like doors, one at a time. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Default
every door closed
Checked by
a gate that reads the consent, not a promise to remember it

Two readers, two languages

Every check that matters is written twice, in two languages, so a green run means two readers agreed.

check · bring nothing · shared · today

Read about Two readers, two languages
Introduction

When two representations of one truth can split silently, one reader is not evidence. A second reader, written in a different language by a different route, catches what the first one shares with its own mistakes.

The shop's page is written by one tool and read back by another. On this site, the browser code computes how tags relate, and a Python test recomputes the same numbers from scratch and compares.

It costs a little more to write. It costs much less than trusting a green light that could never have been red.

The window shows two figures on a ring passing the same token back and forth until they agree. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Why
one reader can agree with itself about anything
Here
the taxonomy is computed in JavaScript and checked again in Python

Shown able to fail

A test only counts once someone has watched it go red for the fault it claims to catch.

check · bring nothing · shared · today

Read about Shown able to fail
Introduction

A check that cannot fail tells you nothing. So for each promise a test makes, we plant the fault it is meant to catch and make sure it goes red.

This site has a prove-red run. It copies the project, breaks it on purpose in several ways, a missing licence label, an image without words, a broken taxonomy, and expects each matching test to fail.

When a prove-red run passes, a green run means something.

The window is a pipeline where one step turns red on purpose, and the line stops there. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Here
make prove-red plants one fault per promise and expects each check to fail

Say whose it is

Every piece of work says who made it, including the parts an AI wrote.

read · bring nothing · shared · today

Read about Say whose it is
Introduction

On the shop page each thing says whose it is, and when we do not know yet, it says that instead of guessing. NextTime is Brigidt's, Quantum 3D5 is Bryant's, and the credit for fourSwordsFromThePast is not yet written in its README.

Much of our code and writing is done by Claude models working as Mentat. The bylines say so, and usually which model, so a reader can weigh the work knowing what made it.

This page was drafted that way too: its commits are mine, with a Mentat byline.

The window is a ledger of names and the work beside each one. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Credit words
Corwin's, Bryant's, Brigidt's, made together, not yet written
Bylines
say when Mentat did the work, and for whom

The lens

Before something leaves our hands, hold four views apart and look through each one.

check · bring nothing · shared · today

Read about The lens
Introduction

The lens is a thought experiment we run before handing work to someone: what do I think, what do I imagine they think, how are they shaping my view, and how am I shaping theirs.

Holding the four apart catches the moments when we have quietly decided for someone else what they want.

It is slow on purpose. It is most useful exactly when we are in a hurry.

The window is an orb seen from one side, then the other. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Four views
yours, theirs as you imagine it, their pull on yours, yours on theirs

The rights are the point

You may run it for any purpose, read how it works, change it, and give copies away with the same rights attached.

read · bring nothing · shared · today

Read about The rights are the point
Introduction

Everything we publish is free software. The four freedoms are not a licensing detail for us; they are why we publish.

When a technical choice is close, we decide it by the four freedoms first, then by what the wider free software movement needs, then by what the technical community has learned.

This page is free too: the JavaScript carries licence labels that GNU LibreJS reads, and the whole site works with scripts turned off.

The window is a still cross-section of layers: freedom to run, to study, to change, to share. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Code
GPL-3.0-or-later (or LGPL on the same terms)
Writing
CC-BY-SA-4.0
Order of reasons
people first, then the four freedoms, then the wider community

How the prompt finds things

The prompt at the bottom guesses what you mean from a taxonomy built out of the words on every card.

learn · bring nothing · shared · today

Read about How the prompt finds things
Introduction

Each card is written in layers: what it is, what it does, how we practise it, and how it is shown. The build reads those layers for words it knows and turns them into tags, and the tags into a taxonomy.

Tags that turn up on the same cards pull together; the rest push apart, and the whole field settles toward balance, the way a tension field does when every pull and push resolves at once. When you type, your words are matched to tags, even misspelled ones, the match spreads to related tags, and the cards nearest the result come forward. The views and the windows are described the same way, so asking for numbers or for something that moves changes how a card opens.

There is no server behind it, so it cannot go down and it does not need your network. It tells you which tags it matched, so you can see why.

The window is the taxonomy itself: every tag on this page, held in tension, settling. Activate the window for it grown large; click anywhere else on the card for this introduction. The buttons above turn to the back of the card.Without scripts, everything this card holds is below: this introduction, the back of the card.

On the back
Facets
do, bring, whose, state, domain, technique, value, presentation
Association
normalized pointwise mutual information between tags
Layout
a tension field that settles toward balance
Network
none; it runs in your browser

How this page works

It is one page of HTML and CSS that reads well with scripts turned off. The scripts add the moving windows, the parallax, the cards that grow, and the prompt; GNU LibreJS can check their licence labels. Nothing is fetched after the page loads and nothing is sent about you. Your Customize settings and whether you turned motion off stay in your own browser. The blog posts and build list were saved when the page was built.

Views of a card

Short introduction
The written introduction: what the thing is, what it does, how we practise it, and how its card works. Click the card anywhere except the window to read it.
Baseball card
The back of the card: facts in a short table, who made it, what it needs, how it is licensed.
Scoreboard
The numbers that can be counted, each with the date it was counted. Only cards that have such numbers offer this view.
Featured window
The window grown large and moving. Activate the window on any card to see it.
Business card
The small card: a name, one line, and a window. It is the default way every card is shown.

Windows

Atom
A nucleus with electrons on tilted orbits. Orbit, science, particles, spin, electron.
Emacs buffer
An Emacs frame types text, a log or a source block, with a mode-line along the bottom. Typing, terminal, editor, text, mode-line.
Co-op walkers
Four coloured walkers roam and a camera keeps all four in frame. Players, multiplayer, together, camera, colours.
Tension field
Every tag on the page held in tension, pulling and pushing until it settles. Graph, chamber, balance, force, cloud of words.
Fog of war
A lantern walks a grid map and the walls appear as it passes. Fog, map, explore, dungeon, maze, reveal.
Ledger
Lines are written to a ledger one at a time and never edited. Hours, accounts, list, scroll, records, log.
Orb
A slow cloudy sphere lit from one side, with drifting cloud. Planet, glow, sphere, sign, logo, ambient.
Pipeline
Steps light up left to right, each only after the one before passes. Build, steps, CI, stages, checks, green, red.
Planes in depth
Planes stacked in three dimensions, swinging open like doors or showing generations behind each other. Layers, depth, 3D, doors, perspective.
Ring
People sit on a ring and a token passes from one to the next. Turn taking, circle, handing over, conference, agreement.
Shells
Things sit on rings around one in focus, closer for fewer steps apart. Orbit rings, graph, network, distance.
Strata
A still cross-section of coloured layers with labels. Static, calm, no motion, layers, stack.

Keys

With scripts off, every card's introduction, back and scoreboard open under Read about, and the quick filters below still work.

The site is free: words under CC-BY-SA-4.0, code under the GPL, version 3 or later. It is built from plain text files by a small Python program; the source and the instructions to build it yourself travel with it. 25 cards, 83 tags.

Display

Show only what you would…

Back up to the cards

aboutcorwin.com