Triumvirate

0. Consists of The Mechanic, The Controller, The Observer.
1. The Mechanic is elected by the general public. Anyone who certifies as a technician is eligible. The term is 60 days.
2. Resolve the budget every 15 days. If two of them do not approve, the cabinet has to make a new budget proposal.
3. It can request hearings on various subjects, e.g. new cabinet members. They do not have authority over hiring of cabinet members, but the hearing is public and will affect the public opinion on the cabinet.
4. It can fire cabinet members if two of them agree. This way mechanic can have some control over the cabinet.
5. The observer rarely exercises her power as a member of the triumvirate.

The cabinet

0. Consists of leaders of divisions.
1. Division leaders are elected within each division.
2. Propose the budget every 15 days.
3. Propose large infrastructure projects and allocates budgets for it.

Divisions

0. Each location is managed by a division.
1. Division leader allocates resources and workers of all locations under the division.
2. Leaders are elected by a popular vote among the corresponding division members and have indefinite terms.
3. Election happens if the leader resigns, be elected to the mechanic, is fired, or cannot function anymore.
4. Directors gather daily at division headquarters. Usually, the leader give the work orders, and the member reports back.
5. Directors can be fired by the division leader immediately.

Workplace managers

0. Workplace managers, or directors, are direct reports of the division leader, and manage individual workplaces.
1. They have the full authority over the place they manage. They allocate resources, set work hours and manage workers.
2. Employees of the workplace is hired and fired by the director.

Salary

0. Ideally, salaries must be distributed at the start of the quarter immediately.
1. Sometimes, there is not enough resource to pay salary, which is why salary action exists as a separate action.
2. Salary action moves resources from the party home to the party members, excluding the party leader.
3. Cabinet, division, workplace parties pay their own members salary. Due to the limit in the implementation, a single salary action must distribute the same amount of resource to every recipant. This means that division leaders in particular have to pay salary twice, once to the directors and once to their workplace employees, i.e. headquarters employees.

Salary is paid with ration + phosphorite. Higher level managers generally receive more as phosphorite. It should be noted that salary is only given with circulating resources which are necessarily consumed.

Laborers are not paid through salary action. They are paid hourly and their wages are included in apparatus operation cost.

• Laborer pay: 0.1 kg ration + 0.1 kg water/hour, nominal 12 kg ration + 12 kg water/quarter(15 days)
• Lv1 manager : 15 kg ration + 15 kg water + 10g phosphorite/quarter, egP = 40
• Director: 30 kg ration + 30 kg water + 30g phosphorite/quarter, egP = 90
• Division Leader: 50 kg ration + 50 kg water + 100g phosphorite/quarter, egP = 200

Salary negotiation

To be implemented......

Firing.

0. Fired people are jobless, NPCs will wander in public spaces. They can be rehired.

Budget

1. Once the stationwide budget is resolved, it is distributed to division headquarters. 1.1 There is no "cache" for stationwide budget. Once stationwide budget is resolved, resources will be taken from specific places. Foods will be taken from farm, components from the workshop, and water from the reservoir.
2. Each division propose and resolve its budget separately, only after the stationwide budget is resolved. Then the budget is distributed from the division headquarters to invididual workplaces.

Requests & Delegations

1. A director issued OfficialTransferResource to me. He does not care where I get the resource from. But he cares about time, destination, and amount.

2. My boss issued Examine to me. He cares that I report the information back. So, in principle, I can delegate it to someone who would report to me.

3. Division leader told me to hire a particular manager. It is important that I do it myself, into my workplace. I cannot delegate this to anyone else. The action must be the same instance.

4. My employee requested Salary to me. It is important that I do it myself, into my workplace. I cannot delegate this to anyone else. The action must be the same instance.

5. A director requested Repair to me. I can delegate it to whoever available to execute the action.

6. I was requested to arrest someone. It is important that I do it myself. The action must be the same instance.

Initial approach: An action has resultingInfo(). If any resultingInfo of an action has positive compatibility with resultingInfo of the original action, then this information serves as proof of work of the original action.

But this is a bad idea. compatibility must have to be implemented with isProofOfWork, not the other way around.

New Implementation:

1. The delegated action information IsProofOfWork of the original action. Therefore, it has positive compatibility with the original action information.
2. The delegated action information is still IsProofOfWork of the original action, but this is not what the player wants. The resulting information is also IsProofOfWork of the original action. Therefore, it has positive compatibility with the original action information. An Alibi information must have negative compability with the original action information.
3. Any delegated action information is not IsProofOfWork of the original action.