Quo Gives Software Its Own Authority

Field notes

Quo’s central exchange uses two messages: an invitation names the permitted reach, then a second message commits to a previously unknown key and makes the request. The homepage gives the mechanism a concrete test case, reporting two reachable classes and an AX-100 stock count of 42. It also exposes failure and lifecycle behavior: the warehouse limits invitations to six per minute per address, keeps standing in memory, and forgets the browser-generated keys when the tab closes.