<p>For historical reasons, the System Consortium remains loosely organized as a corporation with a president and board, though the actual ties to the way a corporation works soon devolved into it being essentially a group of per-federation organizations (e.g: the WF System Organization, The S-R Bloc System Organization, etc). Legacy terms were kept for bureaucracy reasons, then almost as a joke.</p>
<ul>
<li>President — The public face of the consortium, shakes babies and kisses hands, takes UN leadership out for dinner</li>
<li>The Board:<ul>
<li>CEO — Manages board meetings, the person the other CxOs interact with and trust to do the hard work of organization</li>
<li>CFO — Manages resource allocation within the System Consortium, working with UN-RAC</li>
<li>CTO — Manages the technical side of the venture; by far one of the biggest departments</li>
<li>COO — Manages the internal operations of the Consortium</li>
<li>CCO — Manages the intra- and extra-Consortium communications, including the nitties-gritty with the UN.</li>
</ul>
</li>
</ul>
<h3id="ceo">CEO</h3>
<p>Essentially CentComm. Manages the highest level of organization within the consortium. For gameplay, this means they manage gameplay events and large-scale stuff. There are no relevant jobs</p>
<h3id="cfo">CFO</h3>
<p>Manages <del>finances</del> post-scarcity resource allocation, working with the UN Resource Allocation Committee. Relevant jobs:</p>
<ul>
<li>Head of Personnel</li>
<li>Cargo</li>
</ul>
<h3id="cto">CTO</h3>
<p>The meat and potatoes, they manage the technical aspects of Lagrange Station, Lagrange System, the Ansible network, and the DSN. Relevant jobs:</p>
<ul>
<li>Engineer</li>
<li>Atmos</li>
</ul>
<h3id="coo">COO</h3>
<p>Services ahoy! But also many of the things that help the station run efficiently. Relevant jobs:</p>