On the Ceremony of Agreement
A short essay. It is not legal advice.
For most of recorded history, an agreement was an event. Two parties came together in a place, said words in front of witnesses, and made a mark that could not be made casually. The Romans had stipulatio: a spoken question and an immediate, matching answer, in person, in the same breath. Medieval contracts were closed with wax — warmed, pressed with a ring no one else owned, left to harden into something that could be seen and felt and broken only once. A notary did not merely record that a thing happened; the notary's presence was part of what made it happen. The mark was the meaning.
Somewhere in the move to scale, we lost the event and kept only the record. Signing became a transaction: a routed file, a server, a stored copy in a system neither party controls, a green checkmark. It is faster. It is also thinner. The modern signature proves that a click occurred. It rarely makes anyone feel that they have bound themselves to another person — and that feeling was never decoration. It was the point. Ceremony is how humans tell themselves that this moment is different from the thousand clicks around it.
Foolscap is built on a small, stubborn idea: that the document and the agreement should belong to the two people making it, and to no one in between. The contract is written in your browser and lives on your machine. When you are ready to sign with the other party, it goes directly to them — to the person you chose, and nowhere else. There is no server in the middle holding a copy it could read. This is not a privacy gimmick bolted onto a form tool. It is a return to the older shape of the thing: an agreement is between the parties, witnessed by the parties, kept by the parties.
The seal at the foot of a signed Foolscap document is deliberate. It records that each party affirmed, in their own words, that they intended to be bound; it timestamps the moment; it carries a cryptographic fingerprint of the exact text, so that the copy you hold and the copy they hold can be shown to be the same copy, unaltered between the two signings. It is engraved, framed, and stamped because a verification record should look like what it is — a mark of consequence — and not like a metadata appendix. People once framed their stock certificates and their commissions. A record worth keeping should be worth looking at.
We are careful about what this is and is not. Foolscap is not a law firm and does not give legal advice. The templates here are adapted, with attribution, from openly licensed standards written by people far more qualified than a piece of software; the signing certificate is a record of consent and integrity, not a pronouncement of enforceability. We would rather state the limit plainly than dress a convenience up as a guarantee. Honesty is itself part of the ceremony.
None of this is nostalgia for wax. It is an argument that the network finally lets us have both: the reach of the digital and the directness of the in-person. Two people, a document that passes straight between them, a mark that means something, and no intermediary required to make it real. That is not a disruption of the tradition of contracts. It is a continuation of it, by other means.
Draft something. Sign it with someone. Keep the seal.
Foolscap is made by Artivicolab. It provides general document templates for convenience only, is not a law firm, and does not provide legal advice. Have important agreements reviewed by a licensed attorney. · Back to app · Privacy