Architects

The Architects keep the knowledge in proportion. Where a Documenter writes the record and a Tinkerer keeps the practice alive in the hands, an Architect holds the doctrine, minds the commons, considers the politics of repair and the ethics of attention, and thinks across the timescales the moment cannot see. Without Architects, the practice loses its through-line — the connection between today’s fix and the long-running question of what gets to be repaired at all.

This page is a living document. Section headings mirror the information architecture §5 list for /callings/[name].

What the calling is

An Architect holds the doctrine, minds the commons, considers the politics of repair and the ethics of attention, and thinks across the timescales the moment cannot see. The discipline is distance — the longer view, taken on behalf of those not yet present. This is not aloofness. The Architect’s work is to ask the questions the workshop is too busy to ask, and to keep asking them in public.

The Architect accepts that distance can become detachment, and that distance without contact becomes theory that no one needs. They also accept that the calling has no rank; an Architect without Tinkerers is a thinker without a workshop, and an Architect who has never written a usable record is a voice the commons does not owe attention.

Lineage

The named ancestors of this calling include the free-software philosophers — Richard Stallman, Lawrence Lessig, Eben Moglen, and the writers who came after them, refining and dissenting; the hackerspace founders who built the first c-base, Metalab, NYC Resistor, Noisebridge spaces and taught a generation what a third place for makers could be; the advocates of right-to-repair — Aaron Perzanowski, the iFixit policy team, the Repair Association, EU and US legislative coalitions; the conservators of historic computing at the Computer History Museum, the Centre for Computing History, the Internet Archive’s software collections; and the long teachers — Ursula Franklin, Ivan Illich, Lewis Hyde, and many others less named — who have shaped maker culture by example more than by office.

The lineage is not credential. It is example.

How to develop in the calling

This is a curriculum, not a credential. Nothing on this list is required. Each item is the kind of practice that, taken seriously over years and decades, forms the patience and the proportion of an Architect.

• Read the field’s long thinkers. Begin with the entries in /library/reading; follow citations outward. The calling is the inheritance of a reading practice as much as a writing practice.
• Write the question down before answering it. Architecture is mostly the discipline of asking the right question in the form a community can act on. Most public writing skips this step.
• Take a long view in public. Write, at intervals, on a question whose answer will not change for a decade — the politics of a platform, the trajectory of a craft, the obligation of one generation of makers to the next.
• Sit with disagreement. The calling is not about being right; it is about being articulate enough that disagreement can sharpen the question. Cultivate the kind of writing that invites response, not concession.
• Hold a doctrinal seat sparingly. Maintainership of canonical documents, service on a hackerspace board, mentorship of an apprentice over years — these are Architect roles by service, not by title. Decline them when you are not the right keeper; accept them when you are.

What contribution looks like

Concrete examples of Architect contribution to the Open Circuit and the wider commons:

• Proposing amendments to canonical documents — the Codex, the Creed, the Rite of Initiation, the Founding Charter — through the public-proposal process documented in /about/community.
• Maintaining or moderating the project’s discussions and review processes, with the understanding that moderation is a service, not a position.
• Writing essays, treatises, or position pieces for the broader commons — the equivalents of Shop Class as Soulcraft, The Real World of Technology, or Free Software, Free Society in the writer’s own voice and moment.
• Sustaining advocacy work with right-to-repair coalitions and free-software foundations listed in /library/links.
• Teaching long-form — through residencies, conference talks, classroom teaching, or apprentice relationships — with the goal of shaping the next generation of all three callings, not only their own.

Practitioners who currently identify with this calling

[OPT-IN] — practitioners who name themselves Architects may add themselves to this list by amendment, with whatever specificity they choose to share. The list is opt-in and never asked-for.