@quo-systems/quo 0.2.17 → 0.2.19

package/README.md

@@ -13,9 +13,10 @@ Nothing else is Quo.
   beings and judges its door.
 - **Being.** One ordinary object, one voice.
 
-[`SPEC.md`](SPEC.md) is the truth. It is the protocol alone: what any ward in
-any language must do for its bytes to be Quo. It is self-contained and
-assumes nothing from any other document, this README included. Read it first.
+[`protocol/SPEC.md`](protocol/SPEC.md) is the truth. It is the protocol
+alone: what any ward in any language must do for its bytes to be Quo. It is
+self-contained and assumes nothing from any other document, this README
+included. Read it first.
 [`quo-kit.md`](quo-kit.md) is this kit: what one TypeScript
 implementation chose and another kit may refuse. It assumes the spec, and
 where the two disagree the spec wins.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quo-systems/quo",
-  "version": "0.2.17",
+  "version": "0.2.19",
   "description": "Quo: an object asks another object and gets an answer, without knowing where it is. Being, Ward, Harbor.",
   "keywords": [
     "quo",

package/quo-kit.md

@@ -542,8 +542,9 @@ passes the same suite. Those tests are the checklist, not the mock.
   number on every terrain and does not move because another lane of the gate
   is running; a regression in it is somebody deriving again what the ward
   already holds. Beside it, that the kept keys stay under their bound however
-  long a ward talks, and one wall clock set an order of magnitude wide, which
-  is a smoke alarm and not a measurement.
+  long a ward talks, and one wall clock that prints what an ask took and
+  asserts nothing, because the gate runs every file at once and a clock there
+  measures the machine.
 - `test/package.test.ts`: the package as a stranger meets it. The tarball
   is packed, installed into an empty folder with nothing but Node, and
   every entry point the exports map names is imported. Every other suite