Learning

Why a PCOC is built the way it is. The briefs ask one question each. The rationale pages take the same subjects as arguments, then map them.

Briefs

Read in any order. The order below is the debt, if you want it.

• How do you make a digital thing scarce?Why a free key cannot be scarce, and how the cost can sit in the object.
• Issued, listed, or made?Why a cap and a list are the same office, and a made object has no office.
• What kind of cost refuses to divide?Why two objects cost twice, and why the work does not split across them.
• Why memory, and why a clock?Why the cost is memory held over time, and why that time is not inside the file.
• How do you prove when the work happened?Why effort has no date, and how a public block sequence supplies one.
• Can you check a stranger without asking anyone?Why the evidence a checker needs is already in the file.
• Why is the check always cheaper than the making?Why every depth of check costs the verifier less than the making cost the producer.
• What follows from two things?What the object already is, before anyone guesses a use for it.
• Why carry the cost forward?Why the finished file is a spent commitment the holder can put at risk.

Rationale

Why the construction is shaped this way. These pages do not amend the specification.

• Family contractThe abstract object. A match establishes relations. Admission is policy.
• How you make oneOne discharge. A small file, made by holding a room the file does not carry.
• Threat modelTwo holes. A seat-shaped file for less than the floor, or a floor nobody can afford to read.
• Cost and incidenceTwo bills. A skip counted twice is not a measurement.
• FoundationsThe map. How the object, the check, and the door hold together.