Operations and risk

How this class fits together

Operations covers everything that is neither reaching the market nor paying for something, which in practice means the decisions that determine how much damage a bad day can do. The account standard comes first because one part of it, the choice of a username used nowhere else, is the single decision in this archive that cannot be corrected later. Passwords change and keys rotate, but an identifier that already exists somewhere with a history attached cannot be unlinked after the fact.

Counterparty assessment sits here rather than in payment because the risk it addresses is not financial infrastructure but the person on the other side of an order. Structural controls reduce risk from the market and none of them make a seller competent. The procedure specifies what to read on a profile and in what order, and it separates the fields that carry information from the aggregate score most people look at, which is shaped by who bothers to leave feedback rather than by typical experience.

The last two documents cover what to do when something has already gone wrong. Dispute submission is written around the observation that arbitration compares two accounts of one order against a record, so dates and references outperform argument. Outage response is written around the observation that outages cost patience while the reaction to them costs money, which makes doing very little the strongest available move.