During Phase I, ARGC operates through seven Nodes of five members each.
ARGC
└── 7 Nodes
└── 5 members each
Why Nodes Exist
Nodes exist for one reason: five people who know each other's work well enough to challenge each other, support each other, and keep each other honest.
That requires a unit small enough that everyone is visible. A group where contribution can be anonymous does not produce accountability, and accountability is the mechanism ARGC is actually built on.
How a Node Works
A Node works collectively. Members hold a shared engineering target — currently ft_transcendence — and raising each other's standard is part of the work, not a separate activity layered on top of it.
A Node is not a folder of individual projects that happen to share a name. Progress is measured at the Node level, and so is the standard.
Nodes and ft_transcendence
The Nodes are currently centered around ft_transcendence. That shared target is what gives the Phase I structure its purpose: one concrete engineering problem that every Node is accountable for, and that members can be evaluated on together.
See Transcendence for what the project represents, and Phase I for the phase as a whole.
Communication and Coordination
Communication and coordination between a Node and the wider ARGC structure are handled primarily through the Node Leader.
The Node Leader is a coordination point, not an authority over the members. Leadership within ARGC is based on responsibility and trust rather than status.
This Structure Is Temporary
The current Node structure was designed to serve Phase I. It is not the permanent organizational architecture of ARGC and should not be read as one.
When ft_transcendence is completed, the Nodes are dissolved and ARGC reorganizes around whatever model its next stage requires. See The ARGC Journey.