Architects

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

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

What the calling is

An Architect holds the doctrine, minds the commons, weighs the politics of repair and the ethics of attention, and takes the long view on behalf of people not yet present. The discipline is distance. Distance 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 the calling’s own dangers: that distance can curdle into detachment, and that distance without contact produces theory nobody needs. They also accept that the calling carries 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 owes no attention.

Lineage

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

The lineage is not a credential. It is an example.

How to develop in the calling

This is a curriculum, not a credential. Nothing on it is required. Each item is the kind of practice that, kept up 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 and follow the 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 a form a community can act on. Most public writing skips this step.
• Take a long view in public. At intervals, write on a question whose answer will not change for a decade: the politics of a platform, the trajectory of a craft, what one generation of makers owes 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 rather than concession.
• Hold a doctrinal seat sparingly. Maintainership of canonical documents, a seat on a hackerspace board, the 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 ways an Architect serves the Open Circuit and the wider commons:

• Proposing amendments to the canonical documents — the Codex, the Creed, the Rite of Initiation, the Founding Charter — through the public-proposal process described at /about/community.
• Maintaining or moderating the project’s discussions and review processes, holding moderation as a service rather than a position.
• Writing essays, treatises, or position pieces for the broader commons: the next Shop Class as Soulcraft, The Real World of Technology, or Free Software, Free Society, in the writer’s own voice and moment.
• Sustaining advocacy alongside the right-to-repair coalitions and free-software foundations listed in /library/links.
• Teaching in the long form — residencies, conference talks, classrooms, apprenticeships held over years — with the aim of shaping the next generation of all three callings, not just 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 detail they choose to share. The list is opt-in, and no one is ever asked to join it.