The membership leaf · Unions

The membership leaf · Unions

The trace a union keeps.

Two files hold a building's union in good standing: membership.json records the ticket numbers that have been taken, and invites.json records the numbers that have been un-invited. The leaf shows the numbers — the people stay in the pockets that did the joining.

Loading the leaf…

Settled

Ticket numbers that have been taken to a seat. The receipt (with this number) goes to the union's mailbox, and the keeper folds it in.

    Un-invited

    Ticket numbers that have been revoked. When the leaf ships, the gate closes on those numbers everywhere the book is read.

      The honest parts of a leaf

      • A leaf proves numbers, never people. "Token 0f1…ab2 is settled" is true or false; "this face is a neighbor" is a pocket's claim, not a file's.
      • A leaf is live: it is read online when the book asks, and it changes when the building ships a new copy — never between reads.
      • Copies must agree. The pocket mints the seat on the phone, the leaf is folded in by the keeper, and a revoked number closes the gate on every phone that reads it fresh.