@nervur-org/dock 0.3.0

package/GETTING_STARTED.md

@@ -0,0 +1,128 @@
+# Getting started
+
+Quo lets an object ask another object and get an answer, without knowing
+whether that other object is in the same process, on the same device, or
+on another planet. Three words: a harbor boots wards, a ward keeps beings
+and judges its door, and a being is one ordinary object with one voice.
+This is the shortest road from nothing to each of the three, for a
+stranger with a terminal. `SPEC.md` is the truth behind every sentence
+here and assumes nothing; `quo-dock.md` is the dock, the part a box runs.
+
+Two packages, and you start with the one that fits what you have:
+
+- `@nervur-org/nervur`, the library. A harbor, a ward and a being in one
+  process, no wire, no files. For a program that wants Quo inside it.
+- `@nervur-org/dock`, the dock. A daemon and one command, `quo`, that
+  stand a box up: a person's world with a page, a model's side, an api, a
+  door on the wire. For a box that receives people and models.
+
+## A being, in one process
+
+```bash
+npm install @nervur-org/nervur
+```
+
+A being is a class with `asks`, the methods anyone may reach, each with
+the JSON schema of its input. Everything else on the class is hers alone.
+
+```js
+import { Being } from '@nervur-org/nervur';
+import { Ward } from '@nervur-org/nervur/ward';
+import { MemoryHarbor } from '@nervur-org/nervur/harbor';
+
+class Shop extends Being {
+  static asks = { price: { input: { type: 'object', properties: { item: { type: 'string' } } } } };
+  price({ item }) {
+    return { item, eur: 12 };
+  }
+}
+class Customer extends Being {
+  static asks = {};
+}
+
+const harbor = new MemoryHarbor();
+const ward = await harbor.boot('acme', Ward, { Shop, Customer });
+await ward.ask('boot', { key: 'shop', class: 'Shop' });
+await ward.ask('boot', { key: 'ana', class: 'Customer' });
+```
+
+The harbor booted a ward named `acme` with two classes it may make beings
+of, and the ward's owner, the process itself, booted one of each by key.
+The ward's own asks are seven, `boot`, `public`, `invite`, `knock`,
+`remove`, `unboot` and `ask`, and `ward.ask()` with no method is her
+describe: those asks and her `notes`, the ward's `pk` and her beings.
+
+Nobody reaches a being she has not invited. An invitation is minted on a
+being for one id, the shop's for `ana`, and the customer knocks with it;
+from then she holds a standing at the shop, under the name she took, and
+the shop holds her as an occupant.
+
+```js
+const invitation = await ward.ask('invite', { being: 'shop', id: 'ana' });
+const ana = harbor.objects.get(harbor.partitions.get('acme').beings.ana);
+await ana.knock(invitation);
+await ana.take('shop', invitation);
+console.log(await ana.standings.shop.ask('price', { item: 'bread' }));
+// { item: 'bread', eur: 12 }
+```
+
+That is the whole protocol: a standing on one side, an occupant on the
+other, an ask that rides the relation and an answer that rides it back.
+The two beings here share a process; the same lines hold when the shop is
+on a box across the sea, because a standing is an address and a key, and
+the harbor owns the wire. `harbor.objects` is the memory harbor's hand for
+a test and a first program; a being on a real box is reached through her
+ward, never held.
+
+## A box
+
+```bash
+npm install @nervur-org/dock
+npx quo init --dir ~/.quo --ward acme --user razvan --domain acme.com --default --show
+npx quo serve --dir ~/.quo --http 8787
+```
+
+`init` mints the ward `acme`, boots razvan's user being, her doorbell and
+the desk in it, marks it the default ward and shows it at the web route,
+and writes `routes.json`, the four routes of a box, `mcp.`, `web.`, `quo.`
+and `api.` under the domain, for a proxy to map onto the one loopback
+port. Without `--domain`, write it yourself; on a Mac the four are paths
+at one loopback address:
+
+```json
+{ "mcp": "http://127.0.0.1:8787/mcp", "web": "http://127.0.0.1:8787/web", "quo": "http://127.0.0.1:8787/quo", "api": "http://127.0.0.1:8787/api" }
+```
+
+`serve` is the daemon, the one process over that folder, and every other
+command is its client. From a second terminal, a phone:
+
+```bash
+npx quo invite --dir ~/.quo '{"being":"razvan","id":"phone"}'
+```
+
+The answer carries `link`, the ward's page with the invitation in its
+fragment. Opened on the phone, the tab boots a harbor of its own, joins as
+that device, and is in: no account, nothing typed. What a model gets is
+the same world as tools at `mcp.`, what a program gets is the same asks as
+JSON at `api.`, and what another box gets is the door at `quo.`; a being
+answers each the same, because each is an ask at her door.
+
+The box's own doings are rows on the faculties of its dock ward, placed by
+the root with `quo ask --ward dock`: a socket held to another box, an
+agent run for a ward, a schedule on the clock. A second box owns this one
+across the wire with an invitation on the ward's own pk, knocked with
+from there, and every owner command with `--via` from then on. Each of
+those, the edge, and what an estate stands beyond the init, is the
+"Getting started" chapter of `quo-dock.md`, proven cold on a Mac by
+somebody with nothing else to read.
+
+## Your own beings on a box
+
+A box holds the dock's classes and yours. `classes/index.ts` beside the
+wards exports each of yours by name, and `quo boot '{"key":"shop",
+"class":"Shop"}'` boots one; `quo init --class Shop` makes the ward's home
+being one of yours, an organisation's ward with the org as its being. A
+being's asks may name who may reach them, `for`, over the record of the
+occupant asking, and her `cells` are what she keeps between boots: the
+whole of what a being is, in `SPEC.md`, and the words above the spec, a
+world, a home, a membership, in `WORLDS.md` and `GLOSSARY.md`.

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Razvan Gherghina
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,6 @@
+Quo
+Copyright 2026 Razvan Gherghina
+
+This product includes software developed by Razvan Gherghina.
+
+Licensed under the Apache License, Version 2.0. See LICENSE for the terms.

package/README.md

@@ -0,0 +1,37 @@
+# The dock
+
+What every estate on Quo needs and nobody writes twice: a daemon and the
+`quo` command, the front desk, the user being and the avatar, harbors on
+disk, in a tab and on the edge, the model sides and the screen, the
+credential exchange. An estate is all of one owner's harbors, and it is
+built on the dock, on Quo.
+
+```bash
+npm install @nervur-org/dock
+npx quo estate my-estate --domain example.com
+npx quo init --dir my-estate/droplet
+npx quo serve --dir my-estate/droplet
+```
+
+`quo estate` writes an estate folder: one folder per harbor, the first a
+droplet's quo directory with its routes under your domain, its unit and
+its Caddyfile, and a package file that depends on the dock and nothing
+else. Add your beings to `droplet/classes/`, and your placement to the
+routes and agents files.
+
+`beings/quo-dock.md` is the truth of this package and the trunk of its
+documents; read it first. It knows nothing the spec of Quo does not say,
+and adds no word to harbor, ward or being. Beside it are the sides,
+`human/quo-human.md`, `mcp/quo-mcp.md`, `api/quo-api.md` and
+`harbor/quo-harbor.md`; `beings/WORLDS.md` is what home, presence and
+membership mean, and `beings/GLOSSARY.md` is every word above the spec.
+
+## Publishing
+
+Published from 0.1.0 with no compatibility promise before 1.0.0. The
+package ships an emitted `dist/` with its command, and the source beside it.
+
+## License
+
+Apache-2.0. Copyright 2026 Razvan Gherghina. See [LICENSE](LICENSE) and
+[NOTICE](NOTICE).

package/api/quo-api.md

@@ -0,0 +1,196 @@
+# The api route
+
+This is the fourth rendering of one describe. The screen speaks a being's
+describe as forms, the model side speaks it as tools, the CLI speaks it as
+lines, and this route speaks it as plain HTTP and JSON. It is one route of
+the daemon described in `papers/quo-dock.md`, which owns the routes, the
+grants, the avatar and the shared invariants; this document assumes all of
+that and adds only what the route does. `papers/WORLDS.md` decides what
+every route is held to: a route says the grammar a caller speaks and never
+who the caller is, and the same credential is honoured on every route.
+
+## What it is for
+
+A route hears every rung. A request carrying nothing is the stranger every
+route knows: an ask at the named ward's public being as `{}`, which is what
+every stranger is at every door, and what a browser fetch, a page
+rendering server side, a crawler and a tab on another origin are. A
+request carrying a bearer the box granted is an occupant: the identity's
+avatar in the world the grant names, asked through her one standing at the
+world's being. What a script sees with a bearer is what a model sees with
+the same bearer as tools and a tab sees as forms, because all three are
+one avatar's describe for one identity, and the gate is one decision for
+describe and for dispatch. The route judges nothing and names nobody: the
+public being answers a stranger by her own gate, the world's being answers
+an occupant by hers, and the route carries the answer.
+
+A grant is the box's and may die at any moment: a box wiped, an occupant
+removed at the world's being, thirty days without a refresh. Nothing of
+the world dies with it, since the avatar and her standing are the ward's;
+only the box's memory of which token names her is gone, and the holder
+trades again on a fresh invitation and lands on the same avatar. So a
+bearer is held by something with a human near it: a model client whose
+human clicks the allow page again, a script whose root mints again, a
+SaaS whose operator signs up again as at any vendor. A program of the
+org's that must run without a human is not a caller of this route. It is
+a harbor of the org with a ward and a standing, or an agent the daemon
+boots on the box, and either speaks Quo on keys that do not expire.
+
+A world is a ward, so the route names one. Every ward `init` made holds a
+desk, who is public for the first hello and answers a stranger nothing
+else, so a world's public reads live in a ward of their own, and the route is what
+makes a second ward reachable by name from outside: the corpus of a court
+watcher, a catalogue, a board. An occupant's world is the one her
+invitation named, and a bearer on any other world is refused.
+
+## The mapping
+
+`packages/dock/api/route.ts` is the route, `Request` in and `Response` out
+and naming no terrain: the daemon mounts it under `/api` and the proxy maps
+it from the api. hostname, and the worker at the edge mounts the same file
+under its harbor's prefix. It asks its harbor for the wards it holds and for
+which of them a caller who names none is at, and for nothing else.
+
+| request                              | Quo                                                                  |
+| ------------------------------------ | -------------------------------------------------------------------- |
+| `POST /api` `{identity, invitation}` | the trade: her avatar knocks with it, and a grant is issued          |
+| `POST /api` `{refresh}`              | the next grant; the old refresh token dies                           |
+| `GET /api`                           | the describe of the default ward, as `GET /api/<that ward>`          |
+| `GET /api/<ward>`                    | the describe: the public being for nobody, the avatar under a bearer |
+| `GET /api/<ward>/<ask>?k=v`          | that ask, the query as args, every value a string                    |
+| `POST /api/<ward>/<ask>` JSON body   | that ask, the object as args                                         |
+| `POST /api/<ward>/<being>/deliver`   | a vendor's delivery, the raw body and the headers to that envoy      |
+| `GET /api/<ward>/<being>/deliver`    | the same with an empty body: a redirect lands here, query in headers |
+| `OPTIONS`                            | the preflight, any origin, `authorization` allowed                   |
+
+What a caller leaves unsaid follows `papers/WORLDS.md`, and none of it is
+a default the route picks. A credential names an identity in a world, so an
+occupant's ward is her grant's and a bearer on any other ward is refused.
+A stranger carries nothing that names a world, so a stranger who names no
+ward is at the ward the terrain says it is at, the one the box hosts or the
+one it marks, and `GET /api` is what a tab at the web
+route's root sees and a model's first tool list. A being is never named,
+because a caller
+does not choose who answers: naming a ward is naming a door, and behind it
+the ward decides, the public being as nobody for a stranger and the
+identity's avatar for an occupant. The one path that names a being is the
+delivery, and there it is not a choice either: the envoy claimed that path
+at her birth, and a delivery with no envoy named has nowhere to land and
+is 404, never the public being.
+
+The trade is the allow page of the model side without the page. Nobody at
+a page vouches for a program, so a trade is a knock that spends: the
+invitation is the one the root minted for that identity on the world's
+being with `quo invite`, sent as a line, and the avatar knocks with it
+inside the trade. An identity already in is refused with `already in` and
+refreshes instead, or is removed at the world's being and invited again,
+and never re-enters on a spent invitation. What comes back is the box's
+grant, `dock/grants.ts`: an access token for an hour, a refresh token for
+thirty days, the same grant the OAuth dance issues, honoured on the model
+route too.
+
+What she says crosses as the model side crosses it:
+
+| she answered                   | the client gets                                        |
+| ------------------------------ | ------------------------------------------------------ |
+| an object                      | 200 with that JSON                                     |
+| `{ error }`                    | 400 with that JSON                                     |
+| silence, a throw, a wait spent | 503 `{ error: 'silence' }`: the work may have happened |
+| an ask not hers for this asker | 400 `{ error: 'unknown ask' }`, her own answer         |
+
+For a stranger, a ward with nobody at the door is 503 beside them, and
+not a 404 of its own: on the wire a stranger who asks a ward that has no
+public being hears one silence, and a device speaking for strangers says
+what the door would. A stranger learns which world exists here and nothing
+else about it. For an occupant the ward's words cross by name, `unreached`
+as 503 `{ error: 'unreached' }`, and `removed` is 401 `{ error: 'removed'
+}` with the grant forgotten at the box, so a script the world's being
+removed starts over with a fresh invitation, exactly as a model client
+does.
+
+And what the route says on its own: 404 for a ward not here and for a path
+that is not one of the shapes, 400 for a body that is not a JSON object,
+400 `{ error: 'already in' }` for a trade on an identity that holds a live
+standing, 401 `{ error: 'unauthorized' }` for a bearer nobody issued or one
+that died, 403 `{ error: 'not your world' }` for a bearer on a world the
+grant does not name, 413 for a body past a megabyte, 405 for any other
+method. Every answer is JSON and open to any origin: the route carries
+nothing a stranger can use that she did not choose to say, and a bearer is
+the caller's to keep.
+
+The route holds none of the judgement. For a stranger it asks the ward the
+owner's `ask` with no being named, which is the public being asked as
+nobody, and the ward bounds the wait, names the three choices and saves
+before the pointer returns: a public being may write while answering, a
+tally, a board, and what she wrote is hers to keep. For an occupant it
+asks her avatar, `tools` for the describe and `call` for an ask, the two
+things every side asks of her, and saves the ward after.
+
+## The delivery
+
+A vendor's webhook is not a stranger's ask and does not land as `{}`, and
+it is not an occupant's ask either: it is the owner asking the envoy
+`deliver`, as `papers/quo-dock.md` says of envoys, and the route carries
+the bytes and nothing of the judgement. `POST /api/<ward>/<being>/deliver`
+is its own row and not an ask: the body is read as a string and never
+parsed here, since the vendor signed the bytes and a reparsed body fails
+her check, and the rule that a body is a JSON object does not apply. The
+route asks the ward's owner pointer for that being's `deliver` with `{
+body, headers }`, and answers what she answers: `{ ok }` as 200, her error
+object as 400, silence as 503. No bearer is read on this path, because the
+rung is not the caller's to prove: the signature is hers to check, and
+what fails it is refused by her and never by the route.
+
+A `GET` on the same path is the same ask with an empty body, and is where
+an OAuth redirect lands when an envoy begins an account, the code in the
+query. The query crosses inside the headers object under the name
+`:query`, which no header on the wire can carry, so her one ask in stays
+one and an author writes no second door for redirects. What she answers
+crosses as JSON like any delivery.
+
+**And a browser gets a page.** This is a road for programs with exactly one
+human arrival, and it is somebody who has just paid for something: a vendor
+returns her by opening this URL in her tab, so without a page she ends a
+payment reading what an envoy says to a machine. A `GET` whose `accept`
+names HTML is answered with the human side's landing page, saying which of
+the two happened and offering the world's own page, since a tab a vendor
+opened has no history to go back through. What the envoy answered is never
+on it. Everything else is unchanged: a vendor asking for JSON is answered
+in JSON, a `GET` that says nothing about what it wants is answered in JSON,
+and the page carries no cross-origin header, since a page is for the
+browser that was sent here and never for a script somewhere else.
+
+On its own the route says 404 for a ward not here, for a being not hers
+and for a third segment that is not `deliver`, 413 past a megabyte and 405
+for any method but `POST` and `GET`. A vendor that retries on anything but a quick
+200 lands once, because she keeps the delivery id and answers `{ ok }` for
+one she has seen before she wakes anyone.
+
+## What is not here
+
+A ward's delivery reaching more than one envoy, and a vendor that cannot
+sign what it sends. Both stand when a first user does.
+
+## The proof
+
+`packages/dock/test/api.test.ts`, over a real daemon on loopback. A
+stranger: a world with a public board described and asked by anyone, args
+by query and by body, what she wrote kept across a reboot, no ward named
+being the device's own, and every refusal. An occupant: an invitation
+traded for a grant, the describe under the bearer being the avatar's own
+with no ward named and with hers, an ask through her, another world
+refused, refresh rotating, removal at the world's being ending the grant,
+and the identity let in again on a fresh invitation. One identity, two
+grammars: a bearer the OAuth dance issued honoured here and its refresh
+rotating at the trade, a bearer the trade issued opening an MCP session,
+and the tool list being this route's describe with her look and page
+left out. The delivery: signed bytes landing on an envoy's `deliver` as
+the owner, a good signature kept and woken once, a retry landing once, a
+bad one her refusal as 400, no bearer read, what she kept outliving the
+daemon, and the route's own 404, 405 and 413.
+
+The same route on a second terrain is
+`packages/dock/test/terrain/edge.test.ts`, behind `npm run deep:dock`: the
+trade at a worker's `/api`, the ask through her avatar, and the answer
+compared against a Node daemon doing the same thing, because a rendering of
+one describe must not differ by terrain.